Returns the current partners and directors (QSA) of a Brazilian company from the Receita Federal register, with each one's role and start date. Individuals' CPFs are masked as the Receita Federal publishes them. Didit exposes this service through `POST /v3/database-validation/` so you can verify the submitted data against the authoritative source and receive normalized match results. ## Coverage * **Coverage:** \~ 100% * **Country:** Brazil * **Service ID:** `bra_company_directors` * **Data domain:** Government * **Category:** CompanyRegister ## Inputs | Field | Required | Example | | - | -: | - | | `company_registration_number` | Yes | `11222333000181` | | `vendor_data` | No | `user-1234` | * **Required inputs:** `company_registration_number` * **Optional inputs:** `vendor_data` * **Consent:** Not required * **Workflow availability:** Available in workflow with field mapping * **Coverage:** \~ 100% * **Price:** \$0.20 per successful query In a workflow, `company_registration_number` is not printed on an identity document, so no step produces it on its own. Collect it from a Questionnaire answer, a Document AI extraction field, or a value you send when you create the session, and map it on the Database Validation step. Until it is mapped the workflow editor shows this service disabled and names the missing input; at run time a missing input means the check is skipped before any query, so you are never billed for a database that could not be asked. ## Body parameters ISO 3166-1 alpha-3 country code for this database service. Example: `BRA` Array containing this service ID. Pinning the service keeps the request scoped to this exact database. Example: `bra_company_directors` `company_registration_number` value required by this database service. Example: `11222333000181` Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise. Example: `user-1234` ## Input rules & validation notes * `company_registration_number` must match `\d{2}\.?\d{3}\.?\d{3}/?\d{4}-?\d{2}`. ## How to call it ```bash cURL theme={null} curl -X POST "https://verification.didit.me/v3/database-validation/" \ -H "x-api-key: YOUR_API_KEY" \ -F "issuing_state=BRA" \ -F "services=bra_company_directors" \ -F "vendor_data=user-1234" \ -F "company_registration_number=11222333000181" ``` Every successful call returns HTTP `200`. The **`outcome_code`** field tells you what actually happened — distinguishing, for example, a real biometric mismatch (`BIOMETRIC_NO_MATCH`) from a selfie that could not be read (`BIOMETRIC_IMAGE_UNUSABLE`). The `status` shown is the default feature status; your configured [Partial Match / No Match actions](/core-technology/database-validation/database-validation-warnings) can override it. **`MATCH`** — The registry confirmed the identity and every checked field matched. ```json 200 OK — MATCH theme={null} { "request_id": "req_01H…", "status": "Approved", "issuing_state": "BRA", "match_type": "full_match", "validations": [ { "outcome_code": "MATCH", "service_id": "bra_company_directors", "service_name": "Brazil - Company Partners and Directors (QSA)", "source_data": { "directors": [ { "document_number": "***.456.789-**", "entity_type": "person", "name": "MARIA EXEMPLO DA SILVA", "role": "SOCIO-ADMINISTRADOR", "start_date": "2010-03-15" }, { "document_number": "11444777000161", "entity_type": "company", "name": "HOLDING EXEMPLO S A", "role": "SOCIO", "start_date": "2018-06-01" } ], "registration_number": "11222333000181" }, "validation": {} } ] } ``` ## Returned data The exact fields surfaced in `source_data` depend on what the registry returns. The generated example for `bra_company_directors` currently documents this normalized shape: * `directors` * `registration_number` ## Pricing & SLAs Brazil - Company Partners and Directors (QSA) queries are billed only when Didit receives a conclusive result from the validation source. * **Per-call price:** \$0.20 USD. * **Billing:** per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source. * **Latency:** typical p95 \< 2 s. * **Availability:** 99.9% per quarter on Didit's side; downstream source availability varies by country and dataset. ## Continue reading * [Brazil Database Validation overview](/api-reference/database-validation/brazil) * [Database Validation overview](/core-technology/database-validation/overview) * [Outcome Codes](/core-technology/database-validation/database-validation-outcome-codes) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.