Environments - Bindbee Docs

Separate data, shared configuration

	Development	Production
Connectors	Separate, unlimited	Separate, as per plan
API keys	Separate	Separate
Webhook deliveries	Separate	Separate
Automatic sync	Initial sync only	Every 24 hours
Logs	Shared	Shared
Scope configuration	Shared	Shared
Custom field definitions	Shared	Shared

A key only unlocks its own environment. A development key can’t read, write, or create a Production connector, and a Production key can’t touch a Development one - either way, that’s a 401.

Regenerate the key and the old one stops working immediately, everywhere at once.

Move a connector between environments

A connector can still be moved between the two. It keeps its authorization and every ID you have stored, so nobody reconnects. Switch your calls to the target environment’s API key. This can’t be done from the dashboard. Email support@bindbee.dev to have the connector moved.

Choosing one

Use Development when	Use Production when
Testing an integration before go-live	A paying customer’s live connection
A sandbox or demo tenant of an HRIS	Data feeds anything customer-facing
Internal test accounts, however realiztic	You need syncs to run unattended
Validating field mappings

Core concepts - where environments sit in the hierarchy
Authentication - how keys are supplied
Syncing - why Development needs a manual trigger
Embedded SDK - how the key you sign with picks the connector’s environment