Current direction
The platform favors stable domain services internally, bounded public reads, signed provider callbacks, and narrowly scoped interfaces over exposing unfinished operations.
Build on stable boundaries
An API is useful only when the workflow behind it is reliable.
Batch Scale is preparing secure, tenant-scoped integration surfaces deliberately. Public catalog reads are the documented exception while broader API and webhook capabilities remain controlled.
code
check_circleTenant-aware boundaries
check_circleExplicit authorization
check_circleIdempotent writes before broad access
Security expectations
Do not copy session cookies into external tools, scrape private screens, or share provider credentials. Supported developer access will use explicit scopes, revocation, audit evidence, and safe retries.
What comes next
Tenant API keys, signed outbound webhooks, documented schemas, rate limits, idempotency contracts, and sandbox examples will be published only as each surface is supported.
A practical path
Move from question to useful next step.
- 1Describe the integration and records involved
- 2Identify read, write, event, and security requirements
- 3Use only documented interfaces and rollout status
Build the next step around real work.
Start with the part of the business that needs clarity now and preserve a path to everything it affects.