/cac/companies/search

POST /api/cac/companies/search

Price: 1 credit

Search the Nigeria Corporate Affairs Commission (CAC) registry by company name, RC number or AV code, optionally restricted to a business classification. Returns each match's approved name, RC number, internal company id, classification (business name, company, incorporated trustee or partnership), nature of business, registration date and status.

How to use it

Search Nigerian businesses in the CAC registry by name (e.g. 'DANGOTE'). Set search_type to RC_NUMBER for an exact RC number, AV_CODE for an availability code, or APPROVED_NAME for an exact name. Optionally pass classification to narrow by entity type. Returns name, rc_number, company_id, classification, nature_of_business, registration_date and status. Feed rc_number into cac/companies for the full record with tax id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Company name, RC number or AV code to search (examples: "DANGOTE"; minLength: 1)
• search_type string — Match the keyword as any term, an exact RC number, an AV code or an exact approved name (default: "ALL"; one of: "ALL", "RC_NUMBER", "AV_CODE", "APPROVED_NAME")
• classification string — Restrict results to a single business classification (default: "ALL"; one of: "ALL", "BUSINESS_NAME", "COMPANY", "INCORPORATED_TRUSTEE", "LIMITED_PARTNERSHIP", "LIMITED_LIABILITY_PARTNERSHIP")
• count integer required — Max number of results to return (min: 1; max: 50)

Response

• @type string (default: "CacCompanySearchItem")
• name string required
• rc_number string nullable
• company_id integer nullable
• classification string nullable
• classification_id integer nullable
• nature_of_business string nullable
• registration_date string nullable
• status string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.