ParseServerOptions

The account lockout policy for failed login attempts.

Enable (or disable) client class creation, defaults to true

Enable (or disable) custom objectId

Add headers to Access-Control-Allow-Headers

Sets the origin to Access-Control-Allow-Origin

Adapter module for the analytics

Your Parse Application ID

Sets the app name

Configuration for your authentication providers, as stringified JSON. See http://docs.parseplatform.org/parse-server/guide/#oauth-and-3rd-party-authentication

Adapter module for the cache

Sets the maximum size for the in memory cache, defaults to 10000

Sets the TTL for the in memory cache (in ms), defaults to 5000 (5 seconds)

Key for iOS, MacOS, tvOS clients

Full path to your cloud code main.js

Run with cluster, optionally set the number of processes default to os.cpus().length

A collection prefix for the classes

custom pages for password validation and reset

Adapter module for the database

Options to pass to the database client

The full URI to your database. Supported databases are mongodb or postgres.

Set to true if Parse requests within the same Node.js environment as Parse Server should be routed to Parse Server directly instead of via the HTTP interface. Default is false.

If set to false then Parse requests within the same Node.js environment as Parse Server are executed as HTTP requests sent to Parse Server via the serverURL. For example, a Parse.Query in Cloud Code is calling Parse Server via a HTTP request. The server is essentially making a HTTP request to itself, unnecessarily using network resources such as network ports.

⚠️ In environments where multiple Parse Server instances run behind a load balancer and Parse requests within the current Node.js environment should be routed via the load balancer and distributed as HTTP requests among all instances via the serverURL, this should be set to false.

Key for Unity and .Net SDK

Adapter module for email sending

Set to true if a email verification token should be reused in case another token is requested but there is a token that is still valid, i.e. has not expired. This avoids the often observed issue that a user requests multiple emails and does not know which link contains a valid token because each newly generated token would invalidate the previous token.

Default is false.
Requires option verifyUserEmails: true.

Set the validity duration of the email verification token in seconds after which the token expires. The token is used in the link that is set in the email. After the token expires, the link becomes invalid and a new link has to be sent. If the option is not set or set to undefined, then the token never expires.

For example, to expire the token after 2 hours, set a value of 7200 seconds (= 60 seconds * 60 minutes * 2 hours).

Default is undefined.
Requires option verifyUserEmails: true.

Enable (or disable) anonymous users, defaults to true

Enables the default express error handler for all errors

Key for encrypting your files

Set to true if new users should be created without public read and write access.

Sets whether we should expire the inactive sessions, defaults to true. If false, all new sessions are created with no expiration date.

Key for your files

Adapter module for the files sub-system

Options for file uploads

Mount path for the GraphQL endpoint, defaults to /graphql

Full path to your GraphQL custom schema.graphql file

The host to serve ParseServer on, defaults to 0.0.0.0

Options for request idempotency to deduplicate identical requests that may be caused by network issues. Caution, this is an experimental feature that may not be appropriate for production.

Key for the Javascript SDK

Log as structured JSON objects

parse-server's LiveQuery configuration object

Live query server configuration options (will start the liveQuery server)

Adapter module for the logging sub-system

Sets the level for logs

Folder for the logs (defaults to './logs'); set to null to disable file based logging

Your Parse Master Key

Restrict masterKey to be used by only these ips, defaults to [] (allow all ips)

Max value for limit option on queries, defaults to unlimited

Maximum number of logs to keep. If not set, no logs will be removed. This can be a number of files or number of days. If using days, add 'd' as the suffix. (default: null)

Max file size for uploads, defaults to 20mb

middleware for express server, can be string or function

Mounts the GraphQL endpoint

Mount path for the server, defaults to /parse

Mounts the GraphQL Playground - never use this option in production

Sets the number of characters in generated object id's, default 10

The options for pages such as password reset and email verification. Caution, this is an experimental feature that may not be appropriate for production.

The password policy for enforcing password related rules.

Mount path for the GraphQL Playground, defaults to /playground

The port to run the ParseServer, defaults to 1337.

Enable (or disable) the addition of a unique hash to the file names

Set to true to prevent a user from logging in if the email has not yet been verified and email verification is required.

Default is false.
Requires option verifyUserEmails: true.

Protected fields that should be treated with extra security when fetching details.

Public URL to your parse server with http:// or https://.

Configuration for push, as stringified JSON. See http://docs.parseplatform.org/parse-server/guide/#push-notifications

Read-only key, which has the same capabilities as MasterKey without writes

An array of keys and values that are prohibited in database read and write requests to prevent potential security vulnerabilities. It is possible to specify only a key ({"key":"..."}), only a value ({"value":"..."}) or a key-value pair ({"key":"...","value":"..."}). The specification can use the following types: boolean, numeric or string, where string will be interpreted as a regex notation. Request data is deep-scanned for matching definitions to detect also any nested occurrences. Defaults are patterns that are likely to be used in malicious requests. Setting this option will override the default patterns.

Key for REST calls

When a user changes their password, either through the reset password email or while logged in, all sessions are revoked if this is true. Set to false if you don't want to revoke sessions.

Configuration for push scheduling, defaults to false.

Rest representation on Parse.Schema https://docs.parseplatform.org/rest/guide/#adding-a-schema

The security options to identify and report weak security settings.

Callback when server has closed

Callback when server has started

URL to your parse server with http:// or https://.

Session duration, in seconds, defaults to 1 year

Disables console output

Starts the liveQuery server

Personally identifiable information fields in the user table the should be removed for non-authorized users. Deprecated @see protectedFields

Set the logging to verbose

Set to true to require users to verify their email address to complete the sign-up process.

Default is false.

Key sent with outgoing webhook calls