/zauba/directors

POST /api/zauba/directors

Price: 20 credits

Get an India MCA director profile by DIN (Director Identification Number): the director name and the companies they are or have been associated with, each with the company CIN/LLPIN, company name, designation, date of appointment, date of cessation (past associations only), and whether the association is current.

How to use it

Fetch a single India-registered director by DIN (8-digit, e.g. 00001620), or a Zauba director URL. Returns one item with din, name, and companies — a list of associations each with cin (the company's CIN or LLPIN, usable with zauba/companies), company_name, designation, appointment_date, cessation_date (set for past associations), and is_current (true for current associations).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• director string required — India MCA director id (DIN, 8 digits) or a Zauba director page URL containing it (examples: "00001620", "00121863", "https://www.zaubacorp.com/NIKHIL-RASIKLAL-MESWANI-00001620"; minLength: 1)

Response

• @type string (default: "ZaubaDirectorProfile")
• din string nullable
• name string nullable
• companies array (default: [])
  • @type string (default: "ZaubaDirectorCompany")
  • cin string nullable
  • company_name string nullable
  • designation string nullable
  • appointment_date string nullable
  • cessation_date string nullable
  • is_current boolean 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 — Director not found (well-formed but nonexistent DIN, or page has no director 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.

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.