SDKs and Client Libraries
This page lists the client libraries your developers can use to call the platform API from their own applications, along with what each one covers. Use it to pick the right integration path for your stack before you write any code.
The API is a standard HTTPS/JSON service, so you can always call it directly with any HTTP client. SDKs are optional conveniences that handle authentication, request signing, retries, and response parsing for you. Availability and package names are account- and version-specific — (confirm the exact package names, versions, and download locations in your account or developer portal).
Reference
| Language / Platform | Package (placeholder) | Typical use | Auth handled |
|---|---|---|---|
| Direct HTTPS / JSON | n/a | Any language, full control | You supply the API key/token header |
| JavaScript / Node.js | @your-org/api-client | Server-side sends, automation scripts | Yes |
| Python | your-org-api | Batch jobs, data/reporting pulls | Yes |
| C# / .NET | YourOrg.Api.Client | Enterprise/back-office integrations | Yes |
| Java | your-org-api-client | JVM services | Yes |
| PHP | your-org/api-client | CMS and web-app plugins | Yes |
| CLI tool | your-org-cli | Ad-hoc testing, CI/CD steps | Yes |
Rows above are representative. Treat package names as placeholders until you verify them against the official downloads for your account.
Notes
- No SDK for your language? Every SDK is a thin wrapper over the same REST endpoints. Call the API directly with
curlor your preferred HTTP library — you lose nothing but the convenience helpers. - Authentication. SDKs read your API key or token from configuration and attach it to each request. Never hard-code secrets in client-side code or commit them to source control; use environment variables or a secrets manager.
- Versioning. Pin a specific SDK version in your dependency manifest so upgrades are deliberate, and review release notes before bumping.
- Rate limits and retries. SDKs typically retry transient failures with backoff. If you call the API directly, implement your own retry logic and respect any rate-limit responses.
- Support scope. Community or example libraries may not be officially supported. Confirm the support status of each library before relying on it in production.
Related
Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.