CLI, SDKs, and developer sandboxes
Caraer’s developer tools support the steps between an integration idea and a working app. The interactive API reference exposes the released contract, the CLI manages app projects, and JavaScript and Python clients provide generated API types. Developer sandbox endpoints support a separate company context for development.
Why integrate
Section titled “Why integrate”Your team can inspect the contract before building, validate an app locally, and test it against a known company schema. The same toolchain supports app source, functions, webhooks, and CMS modules, so related parts of an integration can live in one project.
What you could build
Section titled “What you could build”Start with a read-only request in the API reference, scaffold a private app with the CLI, implement one function, and validate its saved result in a sandbox. Add deployment and runtime inspection once that workflow is proven.
Start integrating
Section titled “Start integrating”Use the CLI reference, build an app, and test API endpoints with OAuth. Inspect developer-sandbox operations and your chosen client version against the API reference.
Generated clients are versioned contracts; upgrading can change how response data is represented. Follow relevant release notes. Sandbox requests still operate on real sandbox data, and a successful build or ready runtime should be followed by a check of the actual user workflow and saved result.