We’re changing how new developers on-board to Context.IO starting now.
All new developer API keys are subject to a 90-day trial period.
This means all new API keys to Context.IO are provisional accounts and will expire after 90 days.
You may have noticed the developer console shows the following message:
“Your account will expire on <DATE>. Read this FAQ for details on how to extend your access.”
The date on the message is when your API key is set to expire. Below, you will find more information about our new developer provisional accounts, and what to do to remove the provisional status of your account.
What is a provisional account / trial period account?
A provisional account is a Context.IO developer account that is only active for 90 days by default. After 90 days, the provisional account will be deleted unless you follow the instructions below to remove the provisional status.
We believe 90 days will be enough for developers to review the API and determine whether it will be a good fit for their needs.
What are the limits of a provisional account?
During your provisional period, you can only have up to 25 users, and make 500 calls to the API per hour.
This should be enough for developers reviewing the API. A provisional account is not meant for active development on a production-level application.
Can you increase my call limit during the trial period?
No, the call limit during the trial period cannot be lifted. If you feel 500 calls per hour are not enough for your app, we highly recommend you heavily use webhooks for consuming data, as opposed to making calls against the API repeatedly. Our API is meant to be used primarily via webhooks.
How do I remove the provisional status of my developer account to extend use beyond 90 days?
In order to remove the provisional status of your account and extend your usage period beyond the initial 90 days, Context.IO must review your API usage.
Context.IO will perform a call analysis of your account to ensure you are following development best practices (below are the best practices we look for).
When you are ready for us to review your usage of the API, you can reach out to us via email.
What are the best practices I must follow in order to lift the provisional status of my account?
Context.IO is meant to be primarily used via webhooks. Best practices we recommend are:
1. DO: Consume data primarily via webhooks. Set-up webhooks to be notified of new messages arriving in a mailbox instead of constantly polling the API for new messages.
2. DO: Use historical webhooks for message backscans. If your application requires historical data (i.e. messages dating back to the beginning of a mailbox history), you will need to setup your webhooks to receive historical messages.
3. DO: Store account IDs / user IDs on your end. You should store the Context.IO unique account / user ID on your end, so you are able to retrieve data for your end-users without having to poll Context.IO for a user ID.
4. DO: Store message IDs on your end. You should also store message IDs of messages you care about, in case you would need to retrieve it later. (We highly recommend you do store the messages you care about on your end.)
5. DON’T: use Context.IO to populate a live feed. You should not make calls to Context.IO to populate your application’s live feed / display of messages. You should populate your applications’ feed from information from your database, and you should populate your database from webhooks you consume via Context.IO. Why? Each call to Context.IO that requests messages is a call against IMAP, and IMAP can be unpredictable. This is why we recommend you use the API asynchronously via webhooks, so we can maintain the IMAP connection for you and proactively send you the data you need. Otherwise, we cannot ensure calls to retrieve messages straight from IMAP will be performant.
How much does Context.IO cost during the trial period?
There is no cost to you during the trial period.
How much will I pay after my trial period?
You can use Context.IO for free after your trial period has ended in exchange for anonymous, aggregated data sharing. If you want to learn more about how we use data sharing, you can read our privacy FAQ.
If you wish to fully opt-out of data sharing altogether for your entire user base, you can review our pricing options on our pricing page.
If Context.IO is not for me, what happens to my account after 90 days?
After the 90-day period is over, you developer account will be deleted, along with any users and webhooks under your developer key.
In other words, if Context.IO is not for you, you can simply stop using Context.IO, and we will remove all information associated with your account after 90 days — you won’t even have to contact us to delete your account.