Skip to main content
Integrations settings in the admin

Settings > Integrations

​
Definition

The Settings > Integrations page is where you wire TWICE into the rest of your stack. It surfaces the identifier, credentials, and webhook endpoints external systems need in order to read from or push data into TWICE.

​
What ships in the admin

Payment providers are configured separately under Settings → Payments, not here.

​
Account ID

Every API call and webhook payload references your Merchant ID (the tenant identifier). The Account ID card displays it with one-click copy. Share it with any partner or developer integrating against your account.

​
API Keys

API keys authenticate calls to the TWICE Admin API.
  • Create a key from the Create key action — the full key is shown once.
  • Each key shows its label, when it was created, and which user created it.
  • Keys can be revoked at any time — revocation takes effect immediately.
  • Calls made with an API key are attributed to that key in the Activity Log (the actor renders as API: <label>).
API keys grant tenant-wide access — there are no per-key scopes. Treat them like passwords and never commit them to source control.
See API Keys for usage and rate limits.

​
Webhooks

Webhooks push events from TWICE to your systems in near real-time. Each subscription has: A subscription listens to exactly one event type and applies account-wide — create one subscription per event you want to receive. The order lifecycle events are emitted today: order.created, order.updated, and order.deleted. See Webhooks for the payload format.
Webhooks require a plan that includes them — accounts without it see an upgrade prompt. See plans.

​
How integration data flows

Inbound requests authenticate via API key; outbound events flow over webhooks. The Merchant ID scopes both directions to your account.

API Keys

Authenticate and call the Admin API

Webhooks

Subscribe to events