Documentation
SDKs & Tools
The current documentation surface is centered on the API and product workflow. Treat SDK planning as an integration design exercise until official tooling is documented here.
Documentation
Recommended starting point
Begin with the API reference and a thin internal client in your stack.
Begin with the API reference and a thin internal client in your stack.
Model authentication, retries, and payload validation before wrapping calls in shared abstractions.
Keep integration code close to the workflow that uses it until the contract is stable.
01
Recommended starting point
- Begin with the API reference and a thin internal client in your stack.
- Model authentication, retries, and payload validation before wrapping calls in shared abstractions.
- Keep integration code close to the workflow that uses it until the contract is stable.
02
What to avoid
- Do not assume a full language-specific SDK exists for every team workflow.
- Do not hide rate-limit and auth behavior behind overly magical wrappers.
- Do not skip staging validation before connecting production automation.