Anytime you make a network call to Parse on behalf of your app using one of the Parse SDKs or REST API, it counts as an API request. This does include things like queries, saves, logins, amongst other kinds of requests. It also includes requests to send push notifications, although this is seen as a single request regardless of how many recipients are targeted. Serving Parse files counts as an API request, including static assets served from Parse Hosting. Analytics requests do have a special exemption. You can send us your analytics events any time without being limited by your app's request limit.
The request limit is calculated on a per-minute basis. For example, if an app is set to 30 requests/second, your app will hit its request limit once it makes more than 1,800 requests over a 60 second period. If your app hits its request limit, your extra requests will begin to fail with error code 155 (RequestLimitExceeded). To prevent the requests from failing you should adjust the request limit slider for the relevant app on the Account Overview page. Please note that you can see your actual requests/second on the Performance Analytics tab.
You can increase/decrease your request/limit as frequently as you would like within a given month. We will prorate your charges on an hourly basis.
When you increase your request limit, you're provisioning additional capacity ahead of time. Your account will be billed according to the request limit that has been set, regardless of how many requests your app made.
No. We do not adjust your app's request limit automatically.
Every app is different and the answer will depend on how efficient the app is in terms of request usage as well as your user's behavior patterns. We estimate that the average app's active user will issue 10 requests. Thus, if this app's traffic was evenly spread throughout the day, it would be able to handle around 250,000 daily active users under the free tier. If this same app had a million users on a particular day (or 10,000,000 total API requests), it would benefit from bumping the request limit to 120 requests/second. Every app is different, so we strongly encourage you to measure how many requests your users send on average.
By using the various Analytics graphs in your dashboard. You can find the number of daily active users under the Audience graph. The number of requests your app is consuming per second can be found under Performance. These two figures should help you arrive at an estimate of how many requests per second the average user will send your way. While it is possible to get an estimate with a small number of users, we recommend setting up a beta program with a few dozen users prior to launching your app publicly. This will help you get a better estimate of how your app performs with a wider variety of users, and in turn it will help you plan ahead for your big marketing launch.
If you schedule more concurrent jobs than your app is provisioned for, the scheduling API will return an error indicating that you are out of capacity. You can control the number of concurrent jobs for each of your apps by adjusting the request limit slider on the Account Overview page. In general, if you need more concurrent jobs, you are likely to also need more requests per second capacity.
Database storage refers to data stored as Parse Objects, which are limited to 128KB in size. File storage refers to static assets that are stored using the Parse File APIs, typically images, documents, and other types of binary data.
You will find everything you need in the Performance view within the Analytics section of your Parse Dashboard. The amount of File Storage, Database Storage, and Data Transfer currently used by an app will be displayed below the graph, under Billing data.
The overage rate for database size is $10/GB but we only allow increases in increments of 20GB. When you you exceed 20GB of database size we will increase your soft limit to 40GB and begin charging you an incremental $200/month. When you hit your soft limit of 40GB we will increase your soft limit to 60GB... and so on up to a hard limit of 100GB.
We do not provide custom plans for apps that require more than 600 requests per second.
'Unique recipients' is the number of distinct devices a push notification is sent to in a given month. If a particular device receives multiple push notifications in a month, that only counts as one 'unique recipient'. If a particular user owns multiple devices, and a push notification is sent to each of these devices, that will count as multiple 'unique recipients'.
Apps register for push notifications by creating an installation object, which counts as a network request. Subsequent app launches associated with this installation will count as additional requests if the installation object is modified and saved. Note that the installation object may be modified automatically by the Parse SDK, such as when the device time zone or app version has changed.
A request to send a push does use an API request, and does count towards your request limit. However, that request could be to send a push to a single device, or a million devices, and it still uses just one request. One thing to keep in mind is that sending a push notification will likely drive people to use your app, which itself might result in an increase in API request usage. We recommend that you increase your app's request limit prior to a big marketing push, or consider spreading out your campaign over a longer period of time.
Our QuickStart Guide for Parse Push provides the minimal steps required to set up push notifications in your app. Using Core and Analytics to target and track your push campaign metrics is optional.
It is expected that a percentage of your audience will opt out of push notifications or uninstall your app over time. Your Installation data is not deleted in these cases, which may account for the discrepancy between the estimated recipient size and the actual number of valid subscribers.
Please refer to the Troubleshooting guide for your platform.
No. We count Analytics requests separately from other API requests, and we don't count Analytics requests against your request limit. Parse Analytics requests are completely free!
You can create as many apps as you like.
Most of our services (bandwidth, file storage, data transfer, background jobs, and push notifications) don't require you to specify limits ahead of time — we simply charge you automatically if you incur overages. You'll get charged for overages according to the rates listed on the pricing page. Your app will continue to function normally. The one exception is the request per second limit, which you set yourself for each app in your Account Overview page.
You may share access to one app with one or more collaborators. Each collaborator should sign up for a Parse account individually if they don't have one yet. You can then invite them to collaborate on your app from the Collaborators panel in your app's Settings. You as the app owner will remain responsible for any charges your app may incur. Collaborators will share the same level of access that an app owner has, but they will not be able to delete the app or add more collaborators.
You may transfer any app you own to a collaborator in the Collaborators panel in your app's Settings.
Your credit card will be charged automatically on a monthly basis and a copy of the payment receipt will be sent to the account owner via email for your records. You can find a list of past account statements in your Billing Overview page. You can view individual statements and print them for your records from that page.
No. We only accept credit card payments on a monthly basis.
No, but that doesn't mean we aren't going to work our hardest to take care of you. We will always do our best to keep our servers running and to keep them running as smoothly as possible. If a problem occurs, we will use every resource at our disposable to resolve it as soon as possible. We'll also do our best to let you know if there are any issues at status.parse.com.
Your app is hosted in our datacenter located on the East Coast of the United States.
We backup all data across all customers regularly for our own disaster recovery purposes. Customers are responsible for backing up their own data. We are unable to assist individual customers with recovery when the data was deleted by the customer via our API.
Yes. You can inititate a data export from your app's Settings page.
In general, additional background jobs will require an increase to your request/limit. We do not offer custom plans.
You can reset your password . A link will be sent to your email address with further instructions.
Parse staff does not access or interact with customer data or applications as part of normal operations. There may be cases where Parse is requested to interact with customer data or applications at the request of the customer for support purposes or where required by law. Parse may also inspect customer data to debug and troubleshoot platform issues.
Your app will not suddenly stop working if we're unable to charge your credit card once. You will get an email reminder if a charge fails to go through. Please update your credit card information as soon as possible, as we will try to charge your account again in 24 hours. If your account fails to submit payment within 30 days, we reserve the right to disable your account.
Parse offers tools to help users running applications on the Parse Platform. These include Bug Reporting Tools, Billing Inquiries, and Community Channels, and are listed in our Help page for your convenience. Please refer to our Support Policy for more details.
Please note that Parse is designed to be a self-service platform and we provide a lot of information on our site. You may refer to our documentation, see our full list of products and services, or visit the Help center for more information on using Parse. Our Developer forums are a great place to reach out to other Parse developers with any questions that may not be answered directly by our documentation. If something is not working as expected, please file a bug report with detailed information.