# Get Bulletin Status

Used to find out what happened to one or more bulletins, sent in the body by the bulletin reference on the device (`refBoletimSilvDispositivos`). If there is one, it also returns the status of the equipment linked to the bulletin.
Resend rule: entries with Erro status can be sent again while the import process is still in Erro. Cancelado entries can only be sent when the import process is Processado.

Endpoint: POST /roads/bulletin-status
Version: v2
Security: API-Key, Client-Code

## Security:

  - `API-Key` (unknown)
    apiKey in header Authorization

  - `Client-Code` (unknown)
    apiKey in header Client-Code

## Request fields (application/json):

  - `refBoletimSilvDispositivos` (array, required)

## Response 200:

  - `200` (unknown)
    Success.

## Response 200 fields (application/json):

  - `requestId` (string | null)

  - `status` (string)
    Request outcome. Open list: new values may be added; clients should tolerate unknown values.
    Enum: "success", "processing", "accepted", "bad_request", "unprocessable_entity", "error", "service_unavailable"

  - `message` (string)

  - `dados` (array)

  - `dados.apontamentoId` (string)

  - `dados.status` (string)
    Enum: "Cancelado", "Erro", "Processado"

  - `dados.mensagem` (string | null)

  - `dados.equipamentos` (array)

  - `dados.equipamentos.apontamentoId` (string)

  - `dados.equipamentos.status` (string)

  - `dados.equipamentos.mensagem` (string | null)

  - `dados.equipamentos.horaInício` (string)

  - `dados.equipamentos.horaTérmino` (string)

  - `dados.equipamentos.horas` (number)

  - `dados.equipamentos.equipamentoId` (string)

  - `errors` (object | null)
    Validation or rejection errors, per field (field -> list of messages). The `$` key identifies a rejection not tied to a specific field. It is null on technical failures.

## Response 202:

  - `202` (unknown)
    Your request is being processed.

## Response 202 fields (application/json):

  - `requestId` (string | null)

  - `status` (string)
    Request outcome. Open list: new values may be added; clients should tolerate unknown values.
    Enum: "success", "processing", "accepted", "bad_request", "unprocessable_entity", "error", "service_unavailable"

  - `message` (string)

  - `dados` (object | array | null)

  - `errors` (object | null)
    Validation or rejection errors, per field (field -> list of messages). The `$` key identifies a rejection not tied to a specific field. It is null on technical failures.

## Response 400 fields (application/json):

  - `requestId` (string | null)

  - `status` (string)
    Request outcome. Open list: new values may be added; clients should tolerate unknown values.
    Enum: "success", "processing", "accepted", "bad_request", "unprocessable_entity", "error", "service_unavailable"

  - `message` (string)

  - `dados` (object | array | null)

  - `errors` (object | null)
    Validation or rejection errors, per field (field -> list of messages). The `$` key identifies a rejection not tied to a specific field. It is null on technical failures.

## Response 401:

  - `401` (unknown)
    Unauthorized. It happens when the API Key sent does not pass authentication.

## Response 401 fields (application/json):

  - `error` (string)

## Response 403:

  - `403` (unknown)
    Forbidden. It happens when the API Key sent does not have access to the specified client.

## Response 403 fields (application/json):

  - `error` (string)

## Response 422:

  - `422` (unknown)
    The destination system rejected the request. The `errors` field details the reason per field; the `$` key indicates a rejection not tied to a specific field.

## Response 422 fields (application/json):

  - `requestId` (string | null)

  - `status` (string)
    Request outcome. Open list: new values may be added; clients should tolerate unknown values.
    Enum: "success", "processing", "accepted", "bad_request", "unprocessable_entity", "error", "service_unavailable"

  - `message` (string)

  - `dados` (object | array | null)

  - `errors` (object | null)
    Validation or rejection errors, per field (field -> list of messages). The `$` key identifies a rejection not tied to a specific field. It is null on technical failures.

## Response 500 fields (application/json):

  - `requestId` (string | null)

  - `status` (string)
    Request outcome. Open list: new values may be added; clients should tolerate unknown values.
    Enum: "success", "processing", "accepted", "bad_request", "unprocessable_entity", "error", "service_unavailable"

  - `message` (string)

  - `dados` (object | array | null)

  - `errors` (object | null)
    Validation or rejection errors, per field (field -> list of messages). The `$` key identifies a rejection not tied to a specific field. It is null on technical failures.

## Response 502:

  - `502` (unknown)
    The destination system returned an invalid response or could not be reached.

## Response 502 fields (application/json):

  - `requestId` (string | null)

  - `status` (string)
    Request outcome. Open list: new values may be added; clients should tolerate unknown values.
    Enum: "success", "processing", "accepted", "bad_request", "unprocessable_entity", "error", "service_unavailable"

  - `message` (string)

  - `dados` (object | array | null)

  - `errors` (object | null)
    Validation or rejection errors, per field (field -> list of messages). The `$` key identifies a rejection not tied to a specific field. It is null on technical failures.

## Response 503:

  - `503` (unknown)
    The destination system or the service is temporarily unavailable or at capacity. Retry after the interval indicated in the `Retry-After` header.

## Response 503 fields (application/json):

  - `requestId` (string | null)

  - `status` (string)
    Request outcome. Open list: new values may be added; clients should tolerate unknown values.
    Enum: "success", "processing", "accepted", "bad_request", "unprocessable_entity", "error", "service_unavailable"

  - `message` (string)

  - `dados` (object | array | null)

  - `errors` (object | null)
    Validation or rejection errors, per field (field -> list of messages). The `$` key identifies a rejection not tied to a specific field. It is null on technical failures.

## Response 503 headers (application/json):

  - `Retry-After` (integer)
    Time to wait, in seconds, before retrying.

## Response 504:

  - `504` (unknown)
    The destination system did not respond in time.

## Response 504 fields (application/json):

  - `requestId` (string | null)

  - `status` (string)
    Request outcome. Open list: new values may be added; clients should tolerate unknown values.
    Enum: "success", "processing", "accepted", "bad_request", "unprocessable_entity", "error", "service_unavailable"

  - `message` (string)

  - `dados` (object | array | null)

  - `errors` (object | null)
    Validation or rejection errors, per field (field -> list of messages). The `$` key identifies a rejection not tied to a specific field. It is null on technical failures.