Use Jaxia with App9 Post

What this means in practice

Jaxia receives the current brand, page, selection, timezone, and user role, then performs social operations only through delegated App9 Post MCP tools. Draft creation can execute directly, while scheduling, publishing, approvals, and inbox replies require explicit confirmation unless the brand policy is already satisfied.

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

1. Issue a short-lived delegated token limited to the current user, brand, and allowed tools.

2. Pass only the context needed for the current turn.

3. Show suggested actions and tool activity before asking for confirmation.

4. Recheck role, scope, capability, approval, and billing rules when the tool executes.

5. Keep the manual scheduler fully available when Jaxia is unavailable.

Example request

This example uses a server-side API key and an explicit brand selection. Replace placeholder values and keep credentials out of browser bundles, client logs, and source control.

curl --request POST \
  --url 'https://postapi.app9.co/mcp' \
  --header 'Authorization: Bearer APP9_POST_API_KEY' \
  --header 'X-App9-Post-Brand: BRAND_ID'

Open the complete API reference

Operational details

Common mistakes to avoid