Skip to main content

Quick start

What CFO provides privately​

  1. A client_id and client_secret over an approved private channel.
  2. A grant manifest naming the zone, organization, destinations, and capabilities.
  3. Credential validity dates and the escalation owner for discovery drift.

Keep the secret in the ERP secret store. Never place it in source, tickets, chat, screenshots, or URLs.

ERP runtime
  -> POST /integrations/oauth/token
  -> GET  /integrations/me
  -> GET  /integrations/destinations
  -> GET  /integrations/catalog/activity-codes

Verify that /integrations/me matches the manifest. Use only the facility/retention pairs returned by destinations; never build a Cartesian product. Before submission, durably save external_ref, external_batch_id, Idempotency-Key, and the canonical payload.

Dry-run every granted tuple, poll each job to terminal, and persist only after validation succeeds and write access is approved. If an outcome is ambiguous, retry the exact durable identity and payload.

Do not start with persistence

HTTP 202 Accepted means queued, not successful. Always poll the job and retrieve every item page.

Next: select an environment and discover live access.