SapanCalDeveloper Docs

Development and production

What development and production applications can do, the free connection limit, and test calendars.

Every application is either development or production. Build and test in development for free, then switch to production when real users connect.

DevelopmentProduction
PlanAny, including FreePro or Enterprise
CostFreeBilled per connected account each month
ConnectionsUp to 10 per company, across all development applicationsNo limit
New API keysStart bc_test_Start bc_live_
Redirect URIs and webhook URLhttps, plus http://localhost and http://127.0.0.1 for local testinghttps only

The API behaves the same in both: same endpoints, same responses, same webhooks.

The development limit

A company can have 10 connections in total across all its development applications, in every region. Every connection that isn't revoked counts, including ones that need relinking. Test calendars (below) don't count.

When the limit is reached, creating a connect session for a new connection fails with 403 connection_limit_reached:

Development applications are limited to 10 connected accounts per company. Switch an application to production to connect more.

If the limit is reached while a user is on the connect page, the session ends with status: error and error_code: connection_limit_reached. Relinking a connection that isn't revoked is always allowed; bringing back a revoked one counts as a new connection.

Go to production

  1. Upgrade the company to the Pro plan under Billing.
  2. Open the application, go to Settings → General and set Environment to Production. Only owners can change the environment, because production connections are billed.
  3. Make sure every redirect URI and the webhook URL use https. The switch is refused while any of them is a localhost http URL.
  4. Create a new API key (it starts bc_live_), deploy it and revoke the bc_test_ key. Existing keys keep working after the switch, but the prefix helps you tell environments apart.

A connection is billed once per month if it was active at any point in a production application. See pricing.

You can also create a separate production application and keep the development one for testing.

Test calendars

The Testing tab lets owners and admins connect their own calendars to an application and try every endpoint from the console, without writing code:

  • Up to 5 test calendars per application.
  • Free: they don't count towards the development limit or billing.
  • They never send webhooks, and API keys can't see them. They only show up in the console.
  • Try the API runs requests as the application against your test user. They show up in Logs, marked Console, and don't count towards usage.

Test users are named bentocal-test:{your member id}. The bentocal-test: prefix is reserved, so the API rejects user ids that start with it.