Use the App9 Post TypeScript SDK
Call the public contract with typed resources, brand selection, idempotency, and problem errors.
Create App9PostClient with apiKey, brandId, and an optional baseUrl. The SDK adds bearer and brand headers, generates idempotency keys for supported mutations, returns contract types, and raises App9PostApiError with the original problem details.
What this means in practice
Create App9PostClient with apiKey, brandId, and an optional baseUrl. The SDK adds bearer and brand headers, generates idempotency keys for supported mutations, returns contract types, and raises App9PostApiError with the original problem details.
Use the documented brand and account boundaries consistently across the scheduler, REST API, SDK, MCP tools, SSE consumers, and webhooks. That makes the same social operation explainable to an operator and reproducible by an integration.
Implementation checklist
Install @app9/post-sdk in a server-side TypeScript project.
Construct one client per environment and brand credential context.
Use typed create, preview, action, analytics, and inbox methods.
Catch App9PostApiError and preserve problem.request_id.
Regenerate or upgrade the SDK alongside published OpenAPI contract changes.
Operational details
The SDK is a convenience layer over the same REST resources documented here.
Custom fetch injection supports testing and controlled runtime behavior.
Browser use still requires a safe BFF or session because raw service keys must stay private.
Common mistakes to avoid
- Do not bypass the SDK's brand requirement with a fabricated header.
- Do not discard structured problem data and keep only an error string.
- Do not bundle a production API key into frontend code.