---
title: "Company status versus record lifecycle"
description: "Why company data APIs separate a company's register status from its record lifecycle, and how to handle redirected, split and removed records."
url: https://bestcompanydataapi.com/status-and-lifecycle
---

> For the index of all pages on this site, see [llms.txt](https://bestcompanydataapi.com/llms.txt).

# Company status versus record lifecycle

[Data model](https://bestcompanydataapi.com/topics/data-model)

## Answer in brief

Company status says what the register states about the company, such as active or inactive. Record lifecycle says whether the API's record is still the current one, or has been redirected, split, removed or restricted. Read both, and check lifecycle before you update anything you stored under an ID.

**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](https://bestcompanydataapi.com/methodology)

## Two different questions

| Field | Question it answers | Values in CompanyRegistryAPI.com |
| --- | --- | --- |
| `company_status` | What does the register say about the company? | `category`: active, inactive or unknown; `local_name`: the register’s own wording |
| `lifecycle.status` | Is this record the current one? | active, redirected, split, tombstoned, restricted |

A company can be inactive in its register while its record is perfectly current. A record can be redirected while the company is active.

## Reading company status

`company_status.category` is read the same way for every register; `local_name` is the register’s own word, absent when it publishes none. Use the category for filters and logic, and show `local_name` to people, because it carries the register’s meaning. The OpenAPI document still allows a plain string here, the shape served before 10 November 2026, so expect the object and tolerate the string:

```javascript
function statusLabel(company) {
  const status = company.company_status;
  if (!status) return "Status not published";
  if (typeof status === "string") return status; // the older shape
  return status.local_name
    ? `${status.local_name} (${status.category})`
    : status.category;
}
```

## Reading lifecycle

The docs define five lifecycle states:

| `lifecycle.status` | Meaning | What your code does |
| --- | --- | --- |
| `active` | The current record | Use it |
| `redirected` | Merged into another record | Read `lifecycle.canonical_id` and store it |
| `split` | Continued as several records | Choose among `lifecycle.successor_ids` |
| `tombstoned` | The record was removed | Stop showing its facts as current |
| `restricted` | The record is withheld | Keep your row; do not display withheld facts |

A removed or restricted record may answer with its lifecycle and no registry fields.

## Before you update stored data

The docs ask you to check lifecycle before you update stored data, because a stored ID can lead to a redirected or split record:

```python
def refresh(stored_id, read_company):
    company = read_company(stored_id)
    lifecycle = company["lifecycle"]
    match lifecycle["status"]:
        case "active":
            return [company]
        case "redirected":
            return [read_company(lifecycle["canonical_id"])]
        case "split":
            return [read_company(i) for i in lifecycle["successor_ids"]]
        case "tombstoned" | "restricted":
            return []  # flag the stored row for review
        case other:
            raise ValueError(f"unknown lifecycle status: {other}")
```

A split needs a decision: which successor continues your customer record? Usually a person should make it, with the registry identifiers of each successor in front of them.

## Officers follow the canonical record

The officers endpoint resolves a redirected company ID to its canonical record and returns both IDs, so you can see that the redirect happened without a separate read.

## Not found is not “never existed”

An ID with no company visible under it answers `404` `not_found`. The docs are explicit: neither that nor a removed record is evidence that the company never existed, because coverage depends on which registers are connected and qualified. Say “not found in this source” in your interface.

## Questions and answers

### Is an inactive company dissolved?

Not necessarily. Registers use their own words for many situations. Read the register's own wording in local_name next to the normalised category before you act on it.

### What should I do with a redirected record?

Read the record named in lifecycle.canonical_id and store that ID instead. The ID you asked for stays valid as a pointer, but the current facts are under the canonical record.

### Does a 404 mean the company never existed?

No. A 404 not_found means no company is visible under that ID in the API. CompanyRegistryAPI.com's docs say that neither a 404 nor a removed record is evidence that the company never existed.

## Sources for this entry

1. [CompanyRegistryAPI.com API docs](https://companyregistryapi.com/api) 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 OpenAPI document](https://companyregistryapi.com/api/openapi.json) Coragrid. The free API as an OpenAPI 3.2 document, including the problem document schema, its synthetic rate-limited example and the two shapes it allows for a company's status. Retrieved 17 November 2026.
3. [CompanyRegistryAPI.com Company Data API](https://companyregistryapi.com/company-data-api) Coragrid. How the product describes company IDs and registry identifiers, where its data comes from, what it does not offer and how the data may be used. 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](https://bestcompanydataapi.com/sources)

## Continue reading

- [Store permanent IDs](https://bestcompanydataapi.com/store-permanent-ids) (Guide)
- [Caching company data](https://bestcompanydataapi.com/caching-company-data) (Guide)
- [Company records and missing fields](https://bestcompanydataapi.com/company-records-and-missing-fields) (Guide)
- [Permanent ID](https://bestcompanydataapi.com/glossary/permanent-id) (Definition)
- [Best company data API](https://bestcompanydataapi.com/best-company-data-api) (Category guide)
- [CompanyRegistryAPI.com free API](https://bestcompanydataapi.com/companyregistryapi-free-api) (Profile)

## 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.

- [The related websites](https://bestcompanydataapi.com/related-websites)
- [CompanyRegistryAPI.com, the official website](https://companyregistryapi.com/)

## Cite this entry

Best Company Data API. “Company status versus record lifecycle.” Content reviewed 17 November 2026. [https://bestcompanydataapi.com/status-and-lifecycle](https://bestcompanydataapi.com/status-and-lifecycle)

## Featured product: CompanyRegistryAPI.com

Free, keyless company registry API and lookup website

Base URL

https://api.companyregistryapi.com

- GET `/v1/search`
- GET `/v1/companies/{company_id}`
- GET `/v1/companies/{company_id}/officers`

* **Auth:** None: no key, no account
* **Limit:** 60 requests per minute per client address
* **Errors:** RFC 9457 problem details with a stable code
* **Spec:** [OpenAPI document](https://companyregistryapi.com/api/openapi.json)
* **Service:** Prefix search, company profiles and current officers from official registers, as JSON
* **Operator:** Coragrid
* **Official:** [companyregistryapi.com](https://companyregistryapi.com/)
* **Source:** Described from its own docs; same publisher as this site

- [Read the CompanyRegistryAPI.com profile](https://bestcompanydataapi.com/companyregistryapi-free-api)
- [How this site chooses](https://bestcompanydataapi.com/methodology)
