> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usecroma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MTE (slave labour register)

> Brazil's register of employers caught keeping workers in conditions analogous to slavery (the "Lista Suja"), and the register of employers under a conduct-adjustment agreement, searchable by CNPJ, CPF, name, state and year, updated daily.

Brazil's labour ministry publishes the employers its inspectors caught
keeping workers in conditions analogous to slavery, once the administrative
case is final, and keeps each one listed for two years. Central bank rules
bar rural credit to anyone on it, and banks screen against it for ESG and
KYC. A second register lists the employers who signed a conduct-adjustment
agreement instead.

Search both by CNPJ (or its root, for every branch), CPF, name, state or year
of the inspection, and get each listing with the establishment, the workers
found, the activity and every period it has been on the register.

<Note>
  The whole source, organized and ready to query: every endpoint on this page answers in milliseconds. Every response carries `as_of`: how current the data is. [How datasets work](/datasets).
</Note>

## Search the register

`POST /br/mte/slave-labour-search/v1` <a className="dataset-pill" href="/datasets">Dataset</a>

Finds employers on the registers by document, name, state or year.

| Field             | Type    | Notes                                                                                                                        |
| ----------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `query`           | string  | Optional. Words in the employer's name or the establishment, e.g. `fazenda`. Every word must match.                          |
| `document_number` | string  | Optional. A CNPJ or CPF, with or without punctuation, matched exactly; or a CNPJ's first 8 characters to match every branch. |
| `list`            | enum    | Optional. `slave_labour` or `conduct_adjustment`; both by default.                                                           |
| `party_type`      | enum    | Optional. `individual` (listed by CPF) or `company` (by CNPJ).                                                               |
| `state`           | string  | Optional. Two-letter state of the inspection, e.g. `PA`.                                                                     |
| `inspection_year` | integer | Optional. Year of the inspection, e.g. `2024`. Default `0`.                                                                  |
| `page`            | integer | Optional. 1-based page. Default `1`.                                                                                         |
| `per_page`        | integer | Optional. Results per page, 1-50. Default `20`.                                                                              |

```bash theme={"dark"}
curl https://api.croma.run/br/mte/slave-labour-search/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "fazenda" }'
```

Each employer is `{ id, list, party_type, document_type, document, employer_name, establishment, state, inspection_year, workers_involved, cnae, final_decision_date, listed_on, listing_history[], court_order, conduct_adjustment_on, agreement_url }`.

* `list`: `slave_labour` (the register of employers caught keeping workers in conditions analogous to slavery) or `conduct_adjustment` (employers who signed a conduct-adjustment agreement instead, and leave the first register).
* `document`: a CNPJ in full; a CPF masked (`***.456.789-**`). A CPF written inside a name is masked too.
* `listed_on`: when the current listing started; `listing_history[]` is every period on the register, `{ from, to }`, since a court can suspend a listing and it can return.
* `court_order`: the court decision that put the employer on the register, when a court did.

<Note>
  An employer stays on the register for two years. When one leaves, it leaves
  the data the same day: a search by its document then answers `total: 0`, and
  its id answers `found: false`.
</Note>

## One listing

`POST /br/mte/employer/v1` <a className="dataset-pill" href="/datasets">Dataset</a>

Returns one listing by its id.

| Field | Type   | Notes                                                                     |
| ----- | ------ | ------------------------------------------------------------------------- |
| `id`  | string | **Required.** **Required.** The listing's `id`, as the search returns it. |

```bash theme={"dark"}
curl https://api.croma.run/br/mte/employer/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "id": "slave_labour-3f9a0c12d4e5b6a7" }'
```

Each employer is `{ id, list, party_type, document_type, document, employer_name, establishment, state, inspection_year, workers_involved, cnae, final_decision_date, listed_on, listing_history[], court_order, conduct_adjustment_on, agreement_url }`.

* `list`: `slave_labour` (the register of employers caught keeping workers in conditions analogous to slavery) or `conduct_adjustment` (employers who signed a conduct-adjustment agreement instead, and leave the first register).
* `document`: a CNPJ in full; a CPF masked (`***.456.789-**`). A CPF written inside a name is masked too.
* `listed_on`: when the current listing started; `listing_history[]` is every period on the register, `{ from, to }`, since a court can suspend a listing and it can return.
* `court_order`: the court decision that put the employer on the register, when a court did.

<Note>
  An employer stays on the register for two years. When one leaves, it leaves
  the data the same day: a search by its document then answers `total: 0`, and
  its id answers `found: false`.
</Note>

<Card title="Full reference" icon="code" href="/api-reference/overview">
  Schemas, all response fields, and an interactive playground.
</Card>