Zapier Trigger Inbox API

REST discovered

Details

URL: https://api.zapier.com
Docs: https://docs.zapier.com/white-label/trigger-inbox/what-is-trigger-inbox-api

Authentication

Zapier Workflow API user access token oauth2 discovered Set up OAuth ↗

Authorization: Bearer <credential>

First obtain your app's Client ID and Client Secret from Zapier Developer Platform under Embed → Settings → Credentials, and configure redirect URIs there under Embed → Settings → Redirect URIs. Then send the user through Zapier's authorization-code OAuth flow at https://api.zapier.com/v2/authorize; exchange the returned code at https://zapier.com/oauth/token/. Use the resulting bearer token for API requests.

Zapier White Label partner-signed JWT + Zapier Workflow API client ID and client secret discovered

Zapier White Label partner-signed JWT jwt Get key ↗

White Label partners complete onboarding with Zapier, configure a JWKS URL and JWT claim mapping, and receive Zapier client credentials. Your backend then signs a short-lived JWT (for example with sub, tenant/workspace claim, iss, aud=connect.zapier.com, iat, exp, nbf) using a private key whose public key is published at your JWKS URL. Zapier verifies this JWT during token exchange.

Zapier Workflow API client ID and client secret basic Get credentials ↗

Publish your app as a public integration in Zapier's App Directory, then open the Zapier Developer Platform and go to Embed → Settings → Credentials to copy your Client ID and Client Secret. These are used to obtain Workflow API tokens, and the Client ID is also used directly on some V1 endpoints.