Connect
Your leads, over a plain REST API.Read, write, revoke.
Bearer tokens with read and write scopes, JSON errors with codes, paging, and an OpenAPI document you can import.
GET /api/v1/leads?stage=new&band=hot&limit=2 Authorization: Bearer nwc_...
{ "data": [
{ "id": "6f1c3a52-...", "name": "Mia Fischer",
"stage": "new", "score": 75, "band": "hot",
"placement": "dw27-badge", "consent": true }
],
"page": 1, "limit": 2, "total": 9, "pages": 5 }Sample request and response. Tokens are read-only or read and write, shown once and revocable.
In short
The 1Namecard digital business card API is a REST API over the cards, short links, leads, meetings and funnel of one organisation. Bearer tokens made on the API page carry a read or write scope, can be revoked at once, and are limited to 600 requests per 10 minutes. The OpenAPI 3.1 document is public at /api/v1/openapi.json.
Last updated
What it does.
Authenticate with revocable tokens.
Owners and admins make a token under API with Create token. It is shown once, and only its hash is kept. read covers every GET, write covers POST, PATCH and DELETE. Revoking is immediate.
Reach the same data as the admin.
Under
/api/v1you get cards, short links (redirects), leads, notes, meetings, stats and the funnel. You can publish a card, create a short link, move a lead, assign an owner and add a note.Filter leads the way the admin does.
GET /leadstakesq,stage,owner,card,band,quick(due today, overdue, untouched for 48 hours), dates andsort. New hot leads are one query.Import the OpenAPI document.
GET /api/v1/openapi.jsonis a public OpenAPI 3.1 file, generated from the registry the routes use. Load it into any client generator.Get errors you can handle.
Errors are JSON with a
codesuch asinvalid_request,unauthorized,forbidden,not_found,conflictorrate_limited, a message and the fields at fault. Unknown fields are rejected, so a typo is never ignored.Page through lists.
Lists take
pageandlimit(1 to 200, default 50) and returntotalandpages. A page past the end is empty, so a loop until empty always ends.Stay inside the privacy line.
The API never returns IP addresses or user agents. A token reaches its own organisation only, and another organisation's id answers 404. Actions are logged under the person who made the token.
600
requests per 10 minutes for each token
3.1
OpenAPI version of the public document
How it works in three steps.
Step 01
Create a token.
Open API, name the token, choose read, write or both and press Create token. Copy the token now.
Step 02
Send it as a bearer header.
Add
Authorization: Bearer <token>and callGET /api/v1/leads?stage=new&band=hot.Step 03
Import the OpenAPI file.
Point your client generator or API tool at
/api/v1/openapi.jsonto get typed calls.
Who it is for.
Developers
You want leads and funnel numbers in your own code.
Sales operations
You feed a dashboard or move leads from a script.
Agencies
You create short links and read results per client.
Limits by plan.
- Included: Every plan has the API and the OpenAPI document.
- Included: Each token may make 600 requests per 10 minutes, shared with the MCP server.
- Included: Plan limits still apply to what a token creates: Starter 10 short links, Team 200, Business 2,000.
What it does not do yet.
- Not included: There is no delete endpoint for leads. Removing personal data stays in the admin.
- Not included: A token acts as an admin of its organisation. There is no narrower role than read and write.
- Not included: A token does not expire on its own, and it keeps working after its creator leaves, until you revoke it.
- Not included: The API is for asking. To be told about new leads, use signed webhooks.
A REST API for leads, short links and the funnel.
| Resource | What you can do | Scope |
|---|---|---|
| cards | List, read, create, change, publish and unpublish | read, write |
| redirects | List with 7 and 30 day clicks, create, change, soft delete, restore | read, write |
| leads | List with filters, read with score reasons, change stage, owner, next action and value | read, write |
| leads/{id}/notes | List and add internal notes | read, write |
| meetings | List, read, change status and note | read, write |
| stats | Dashboard totals and per-card 30 day views, saves and leads | read |
| funnel | The funnel by rep, placement or card for a period | read |
Dates are ISO 8601 in UTC. PATCH changes only the fields you send. Bodies over 100 kB are refused. Every response carries X-Request-Id: quote it if you need help.
Lead data is personal data.
Leads carry consent, the wording the visitor saw and their message. Use them only for the follow-up they were collected for, and keep tokens to the people and systems that need them. Read-only tokens suit dashboards.
Questions about this feature.
Is there an OpenAPI description of the API?
Yes. The OpenAPI 3.1 document is public at /api/v1/openapi.json and needs no token. It is generated from the same registry the routes use.
What are the rate limits?
600 requests per 10 minutes per token, shared with the MCP server. Over that the API answers 429 with a Retry-After header in seconds.
Who can create a token?
Owners and admins, on the API page. A token acts as an admin of the organisation, sees only that organisation, and is shown once.
Does the API return IP addresses?
No. IP addresses and user agents are never returned. Leads carry the consent flag and the consent wording.
Can I use the API to delete leads?
No. Short links can be soft deleted and restored, but removing a lead is done in the admin.