Skip to main content

1. Get an API key

Company Matching uses customer API keys, not login JWTs, on the match endpoints. Contact support@thedatacity.com for a key. Keys look like:
Treat the key like a password. Store it in an environment variable or secrets manager. Never commit it to source control or ship it in a browser bundle. See Authentication for details.

2. Match one company

Send a POST to /api/v1/match with at least input_name. Include your key in the Authorization header.
Set your client timeout to at least 60–120 seconds. Matching can call several external sources; cold runs are slower than cached ones. Optional fields that improve accuracy when you have them:

3. Read the result

A successful response looks like this:
If no confident match is found, matched_company_number (and related fields) are null. That is still a 200 — check for a present CRN rather than assuming every call resolves.

Matching a list

For more than one company, use the batch API: submit the list, then poll status or receive a completion webhook.

What’s next

Authentication

How keys work and how to send them.

Response reference

Every field in the response, and when it is empty.

Errors

Status codes and retry guidance.

Endpoint reference

Full request/response schema with the interactive playground.
Last modified on August 20, 2026