Answer in brief

Company data APIs use three access models. Keyless APIs take no credential and limit by client address, API key APIs identify your application, and OAuth or bearer token APIs act for a user or carry scopes. Pick the model your deployment can protect, keep keys out of code and chats, and expect the transport to change when you move between models.

Disclosure. This site is published by Coragrid, the operator of CompanyRegistryAPI.com, and promotes it. “Best” is our editorial choice, not a measured ranking. Other products are described only from their own official pages. How we choose

Keyless

The client sends no credential. The provider identifies callers by their address and limits each one.

curl "https://api.companyregistryapi.com/v1/search?q=example&address_country=FI"

The free CompanyRegistryAPI.com API works this way: no key, no account and 60 requests per minute per client address. The SEC says the same of its EDGAR APIs on data.sec.gov, which need no authentication or API key.

Good for: prototypes, browser calls (where the API allows them), agents running in a user’s browser, and teams that cannot manage secrets yet.

API key

The client sends a key issued to your application. How it is sent differs by provider, so read the authentication section closely. The Companies House API, for example, takes the key as the username of HTTP Basic authentication with an empty password:

curl "https://api.company-information.service.gov.uk/company/00000006" \
  -H "Authorization: Basic $(printf '%s:' "$COMPANIES_HOUSE_API_KEY" | base64)"

Good for: server-side integrations where you want a per-application allowance and usage you can attribute.

OAuth and bearer tokens

The client sends a token in the Authorization header. RFC 6750 defines a bearer token as one that any party in possession of it can use, so it must be protected in storage and in transit:

curl "https://api.coragrid.com/v1/me" \
  -H "Authorization: Bearer $CORAGRID_API_KEY"

That example is from CompanyRegistryAPI.com’s page on Coragrid API keys: the full Coragrid API takes its key as a bearer token, and /v1/me returns the key’s scopes and limits. Full OAuth 2.0 adds a user’s consent on top; the Companies House API uses OAuth 2.0 for functionality that acts for an end user, such as filing.

Good for: scoped access, per-user actions, and higher limits tied to an identity.

Keeping a key safe

The Coragrid key guidance is a good baseline for any provider:

  1. Keep the key in the operating system keyring on a developer machine.
  2. Inject it into the process environment from a secret store in automation.
  3. Never write it to a shell profile or another file, and never paste it into a conversation with an agent.
  4. Check what the key can do before you rely on it: a status call that prints its scopes and limits catches a wrong key early.

Moving between models

A change of access model is a change of transport, even when the data is the same. Moving from the free CompanyRegistryAPI.com API to a Coragrid key keeps company IDs and field names, but adds bearer authentication and turns search into a QUERY request with a JSON body. Keep credentials and request building in one module so the switch touches one file.

Questions and answers

Is a keyless API less secure?

Not for reading public register data. There is no secret to leak, and the provider limits use per client address instead. It does mean you cannot get a higher allowance by identifying yourself.

Can I put an API key in front-end code?

No. Anything shipped to a browser is public. Call a keyed API from your server, or use a keyless API that allows browser requests.

Where should an API key live?

In a secret store, injected into the process environment at run time, or in the operating system keyring on a developer machine. Never in a repository, a shell profile or a conversation with an AI agent.

Sources for this entry

  1. CompanyRegistryAPI.com API docs Coragrid. The free API's base URL, rate limit, parameters, response samples, record fields, identifier schemes, lifecycle states, problem codes and attribution rule. Retrieved 17 November 2026.
  2. CompanyRegistryAPI.com Get an API key Coragrid. What a Coragrid API key adds over the free API, how keys are issued and stored, and the first calls with a key. Retrieved 17 November 2026.
  3. Companies House API authorisation Companies House. How the Companies House API takes an API key through HTTP Basic authentication, and where it uses OAuth 2.0. Retrieved 17 November 2026.
  4. EDGAR Application Programming Interfaces U.S. Securities and Exchange Commission (SEC). What the data.sec.gov APIs deliver and that they need no authentication or API key, in the SEC's words. Retrieved 17 November 2026.
  5. RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage RFC Editor (IETF). What a bearer token is and how it is sent in HTTP requests. Retrieved 17 November 2026.

Each source supports only what its publisher says about its own product or data. Official descriptions do not establish comparative performance, and this site has run no benchmark. All sources

Continue reading

How the related websites connect

This is one of 3 coordinated reference sites published by Coragrid. They cover neighbouring questions and feature the same product, so they are not independent endorsements of it or of each other.

Cite this entry

Best Company Data API. “Keyless, API key and OAuth access to company data.” Content reviewed . https://bestcompanydataapi.com/keyless-key-and-oauth-access