REST API & Personal API Tokens

ApproveThis exposes a v1 REST API so your own systems can create workflows, submit requests, record approvals or denials, and manage outbound webhook subscriptions. Calls are authenticated with a personal API token, which an Administrator creates on the API Tokens tab under Integrations. This guide covers creating that token and capturing it from its one-time reveal; the interactive API reference generated from the live v1 routes is served at /docs/api. You'll need Administrator access to the workspace.

Who this is for: admin.

On the 'API Tokens' tab, create a token named for what will use it, and copy it from the one-time reveal

Before any code can call the v1 REST API, you need a bearer token to authenticate with, and the token value is shown only once at creation. Note the constraints on what that token can do: every v1 call requires an active subscription (teams without billing access get 402 Subscription Required), and tokens are all-or-nothing — v1 endpoints authorize by policy, not by token scopes, so there is no scoped or least-privilege key.

1. Sign in as an Administrator.

2. Click API Tokens.

   

3. In Token Name, enter a name describing the system or script that will use the token — e.g., Reporting script.

   

4. Click Create token.

   

A modal titled "API Token" opens showing the token value once, with the message Please copy your new API token. For your security, it won't be shown again. — copy it now and store it where your integration can read it.