Answer in brief

The glossary defines the terms used across this reference in one sentence each, from HTTP and API terms such as 429, Retry-After and problem details to company data terms such as permanent ID, jurisdiction code and LEI. Every definition has its own page with a practical note and its sources.

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

How to use it

Use a definition page when a guide mentions a term you want to pin down. Each page links back to the guides that use the term.

Terms

  • API key

    A secret string an API issues to identify the application calling it, sent with each request so the provider can authorise use and apply limits.

  • Attribution

    The credit line or source mention an API or data licence requires wherever you display its data, such as "Powered by Coragrid".

  • Bearer token

    A token that any party holding it can use to access protected resources, sent in the Authorization header and defined for OAuth 2.0 in RFC 6750.

  • Cursor

    An opaque token an API returns with a page of results, which the client passes back unchanged to get the next page, until the API returns none.

  • HTTP 429

    The HTTP status code that tells a client it has sent too many requests in a given amount of time, defined in RFC 6585 for rate limiting.

  • Idempotent request

    An HTTP request whose intended effect on the server is the same whether it is sent once or several times, which makes it safe to retry.

  • ISO 3166

    The international standard for codes of countries (part 1, such as FI) and their subdivisions (part 2, such as CA-QC), used by company data APIs.

  • JSON

    JavaScript Object Notation, a lightweight, text-based, language-independent format for structured data, defined in RFC 8259.

  • Jurisdiction code

    A code naming the place whose register issued a company's number, written as ISO 3166 country or subdivision codes such as FI or CA-QC.

  • Legal Entity Identifier (LEI)

    A unique 20-character alphanumeric code for a legal entity, based on the ISO 17442 standard and administered by GLEIF.

  • MCP

    The Model Context Protocol, an open protocol that connects LLM applications to external data sources and tools, with messages in JSON-RPC 2.0.

  • OpenAPI

    A standard, language-agnostic description format for HTTP APIs that lets people and software discover an API's paths, parameters and responses.

  • Permanent ID

    An identifier a data service gives a company that stays valid through renames, mergers and splits, unlike names and registry numbers.

  • Prefix search

    A search that matches records whose name or number starts with the text typed, such as CompanyRegistryAPI.com's search by the start of a name or business ID.

  • Problem details

    An RFC 9457 JSON format for HTTP API errors, served as application/problem+json, with type, title, status, detail and instance members.

  • Rate limit

    The number of requests an API accepts from one client in a time window, such as 60 per minute per client address, beyond which it refuses requests.

  • Retry-After

    An HTTP response header telling the client how long to wait before a follow-up request, as a number of seconds or an HTTP date, under RFC 9110.

  • WebMCP

    A draft web API, from the W3C Web Machine Learning Community Group, that lets a web page offer JavaScript tools to an AI agent in the browser.

Questions and answers

Where do the definitions come from?

Standards terms rest on the RFC or specification that defines them. Product terms rest on the documentation of the API that uses them.

Why are some terms specific to CompanyRegistryAPI.com?

Because its field names, such as next_cursor or country_scope, are used as worked examples throughout the guides. Each definition says where the term is product-specific.

Sources for this entry

  1. RFC 9457: Problem Details for HTTP APIs RFC Editor (IETF). What a problem detail is, its members and the application/problem+json media type. Retrieved 17 November 2026.
  2. OpenAPI Specification v3.2.0 OpenAPI Initiative. What an OpenAPI description is for, in the specification's own words. 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. “Company data API glossary.” Content reviewed . https://bestcompanydataapi.com/glossary