Create an API token.

Create and use a token.

1. 01
   Step 1.

   Open API in the sidebar. On a phone, tap More, then API under Organisation.

   API
2. 02
   Step 2.

   In Create a token, type a Name, up to 80 characters. Name the tool that will use it, for example Zapier or CRM sync.

3. 03
   Step 3.

   Under Scopes, keep read, write or both ticked. read lists and reads cards, short links, leads, meetings, stats and the funnel. write creates, changes and deletes short links, edits cards, moves and assigns leads and adds notes. write does not include read, so most tokens have both. You must choose at least one.

4. 04
   Step 4.

   Press Create token. The token appears once and starts with nwc_. Copy it into a password manager or a secret variable. The page shows it only now. If you lose it, revoke it and create a new one.

   Create token
5. 05
   Step 5.

   Send the token on every request in the header Authorization: Bearer followed by the token. The base URL is https://app.1namecard.com/api/v1.

6. 06
   Step 6.

   Try one call. To list your newest hot leads, send a GET request to https://app.1namecard.com/api/v1/leads?stage=new&band=hot&limit=20 with the header. The answer is JSON with a data list and the page, limit, total and pages of the result.

7. 07
   Step 7.

   For every endpoint, open the OpenAPI 3.1 document at https://app.1namecard.com/api/v1/openapi.json. It needs no token. The API page also links to it as OpenAPI document.

8. 08
   Step 8.

   To stop a token, find it under Tokens and press Revoke, then confirm. Anything using it stops working at once.

Limits and errors.

Each token may make 600 requests per 10 minutes, counting REST and MCP together. Over that, the API answers 429 with a Retry-After header in seconds. A missing, wrong or revoked token gets 401. A token without the right scope gets 403. An id from another organisation gets 404, the same as a missing record. Lists take page and limit, from 1 to 200, with 50 as the default. Times are ISO 8601 in UTC.

The Tokens list shows each token's Name, its first characters, its Scopes, who created it, when, and when it was Last used. Actions made through a token appear in Activity under the person who created it.