API tokens let your own scripts or applications call NameGrid's public API instead of clicking through the dashboard by hand.

Generating a token

  • Log in and open API tokens from the sidebar.
  • Give it a name that tells you where it's used later (e.g. "Production server" or "Local testing") — you can create as many named tokens as you need, one per app or environment.
  • Click Generate token.

Your full token is shown exactly once, right after you generate it — copy it somewhere safe immediately. After that, NameGrid only ever shows a shortened prefix, so if you lose it you'll need to revoke it and generate a new one.

Using it

Send your token in the x-api-key header on requests to the API. Every token is rate-limited, and usage is tracked so you can see when a token was last used from the API tokens page.

Full API reference

This article covers getting a token; for the complete list of endpoints, request/response shapes, and error codes, see the full API reference at docs.namegrid.org.

Revoking a token

If a token is no longer needed — or you think it's been exposed — click Revoke next to it on the API tokens page. Revocation is immediate and can't be undone; generate a new token if you need to keep using the API from that app.

Frequently asked questions

Yes — create a separate named token for each application or environment (production, staging, a local script) so you can tell them apart and revoke just one without affecting the others.

Still stuck?

Browse the rest of the Help Center, or reach out and a real person will get back to you.