POST /api/zauba/companies
Price: 20 credits
Get full India MCA company master data by CIN or LLPIN: name, status, class, category and sub category, ROC, registration number, date of incorporation, listed/unlisted, authorised and paid-up share capital, NIC code and activity description, registered address, email, member count, previous names and CINs, annual compliance dates, current and past directors (DIN, name, designation, appointment/cessation), and registered charges (secured loans).
Fetch a single India-registered company by CIN (21-char, e.g. L17110MH1973PLC019786) or LLPIN (e.g. AAC-9143), or a Zauba company URL. Returns one item with cin, name, status (Active/Amalgamated/Struck off/etc), company_class (Public/Private), category, sub_category, roc, registration_number, date_of_incorporation, is_listed, authorized_capital/paid_up_capital (INR), member_count, nic_code and nic_description (principal activity), registered_address, email, website_url, last_agm_date, last_balance_sheet_date, previous_names, previous_cins, directors (din, name, designation, appointment_date, cessation_date, is_current), and charges (charge_id, creation/modification/closure dates, amount, charge_holder).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)company string required — India MCA company id (CIN or LLPIN) or a Zauba company page URL containing it (examples: "L17110MH1973PLC019786", "AAC-9143", "https://www.zaubacorp.com/RELIANCE-INDUSTRIES-LIMITED-L17110MH1973PLC019786"; minLength: 1)@type string (default: "ZaubaCompany")cin string requiredname string requiredis_llp boolean (default: false)status string nullablecompany_class string nullablecategory string nullablesub_category string nullableroc string nullableregistration_number string nullabledate_of_incorporation string nullableis_listed boolean nullableauthorized_capital number nullablepaid_up_capital number nullableobligation_of_contribution number nullablemember_count integer nullablepartner_count integer nullabledesignated_partner_count integer nullablenic_code string nullablenic_description string nullableregistered_address string nullableemail string nullablewebsite_url string nullablelast_agm_date string nullablelast_balance_sheet_date string nullableprevious_names array (default: [])previous_cins array (default: [])directors array (default: [])@type string (default: "ZaubaDirector")din string nullablename string nullabledesignation string nullableappointment_date string nullablecessation_date string nullableis_current boolean nullablecharges array (default: [])@type string (default: "ZaubaCharge")charge_id string nullablecreation_date string nullablemodification_date string nullableclosure_date string nullableassets string nullableamount number nullablecharge_holder string nullable422 — 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 — Company not found (well-formed but nonexistent CIN/LLPIN, or page has no company data) 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.