Skip to main content
An organization = one of your EMS customers. It’s the container for webhooks, card holders, and event routing.

​
Create

POST /accounts/{accountId}/organizations
Scope: organizations-write

{
  "reference_id": "client_acme_001",
  "tpa_id": 42,
  "name": "Acme AB"
}
FieldNotes
reference_idYour internal client ID. Required. Unique per account.
tpa_idMust be a TPA on this account (ideally signed)
nameDisplay name

​
When to use multiple orgs for one client

Usually 1 org = 1 client. But split into multiple orgs when you need:
  • Different webhook endpoints per card type
  • Different event subscriptions
  • Separate card holder groups with different configs
Example: Client wants corporate cards in Org A (webhook → accounting system) and private cards in Org B (webhook → different endpoint).

​
Organization “tabs” (conceptual)

Think of an org as having config sections:
SectionWhat it controls
IssuerWhich TPA + card types flow through this org
ConnectionWebhook URL + auth
Webhook eventsWhich event types to subscribe
Card holdersWhich people get data
All configured via API — no dashboard required for integration.

​
Query / update / delete

GET    /accounts/{accountId}/organizations
GET    /accounts/{accountId}/organizations/{organizationId}
PUT    /accounts/{accountId}/organizations/{organizationId}
DELETE /accounts/{accountId}/organizations/{organizationId}
Delete cascades: webhooks, card holders, etc. gone. Be careful.