/cnpj/companies

POST /api/cnpj/companies

Price: 1 credit

Get a Brazilian company's registry record from the National Registry of Legal Entities (CNPJ) by its CNPJ number: legal name, trade name, registration status with date and reason, any special legal status (e.g. judicial recovery), activity start date, legal nature, company size, share capital, primary and secondary economic activity (CNAE) codes, full address, contact phones, fax and email, Simples/MEI tax-regime flags, head-office/branch indicator, state tax registrations (Inscrição Estadual) and the partners/shareholders board (name, qualification, age range, entry date, legal representative).

How to use it

Look up one Brazilian company by its CNPJ (e.g. '33000167000101' or '33.000.167/0001-01'). Returns one item with company_name, trade_name, registration_status, legal_nature, company_size, capital, main_activity, secondary_activities, address, contacts, tax-regime flags and partners.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• cnpj string required — Brazilian CNPJ number, 14 digits (accepts the masked 33.000.167/0001-01 form) (examples: "33000167000101")

Response

• @type string (default: "CnpjCompany")
• cnpj string required
• company_name string required
• trade_name string nullable
• is_head_office boolean (default: false)
• registration_status string nullable
• registration_status_date string nullable
• registration_status_reason string nullable
• special_status string nullable
• special_status_date string nullable
• activity_start_date string nullable
• legal_nature string nullable
• legal_nature_code string nullable
• responsible_qualification string nullable
• company_size string nullable
• capital number nullable
• main_activity object nullable
  • @type string (default: "CnpjActivity")
  • code string nullable
  • description string nullable
• secondary_activities array (default: [])
  • @type string (default: "CnpjActivity")
  • code string nullable
  • description string nullable
• address object nullable
  • @type string (default: "CnpjAddress")
  • street_type string nullable
  • street string nullable
  • number string nullable
  • complement string nullable
  • district string nullable
  • city string nullable
  • state string nullable
  • postal_code string nullable
  • country string nullable
• phone_1 string nullable
• phone_2 string nullable
• fax string nullable
• email string nullable
• opted_for_simples boolean nullable
• opted_for_mei boolean nullable
• state_registrations array (default: [])
  • @type string (default: "CnpjStateRegistration")
  • number string required
  • active boolean nullable
  • state string nullable
  • state_name string nullable
• partners array (default: [])
  • @type string (default: "CnpjPartner")
  • name string required
  • document string nullable
  • type string nullable
  • qualification string nullable
  • age_range string nullable
  • entry_date string nullable
  • country string nullable
  • legal_representative_name string nullable
  • legal_representative_document string nullable
  • legal_representative_qualification string nullable
• data_updated_at 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 — No company found for the given CNPJ 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.