# onboarding_approval_not_offered (/en/docs/errores/onboarding_approval_not_offered)

This onboarding step is not asking for an authorization right now.

|                |                                   |
| -------------- | --------------------------------- |
| **Code**       | `onboarding_approval_not_offered` |
| **Type**       | `conflict_error` — State conflict |
| **HTTP**       | `409`                             |
| **Retriable?** | No                                |

## What to do [#what-to-do]

Read `GET /v1/empresas/\{id\}/onboarding`: `steps[].pending_action.approval` names the decision, its `act` and whose it is, whenever there is one to take.

> **Warning**
>
> Retrying the same request will fail the same way. Change the request, not the frequency.

## The envelope [#the-envelope]

```json
{
  "error": {
    "type": "conflict_error",
    "code": "onboarding_approval_not_offered",
    "message": "…",
    "hint": "Read `GET /v1/empresas/{id}/onboarding`: `steps[].pending_action.approval` names the decision, its `act` and whose it is, whenever there is one to take.",
    "retriable": false,
    "doc_url": "https://docs.facturia.cl/errors/onboarding_approval_not_offered",
    "request_id": "req_01K2R7Q9M4T2VB"
  }
}
```

Program against `code`, never against `message` — the prose can be rewritten, the code cannot (§5.8).

`hint` and `retriable` arrive in the response with these exact values: they are a function of `code` and come from the same dictionary `GET /v1/error_codes` serves, so the envelope and the dictionary cannot disagree. Both are English on the wire by design — one registry, one language. More in [The error envelope](/en/docs/errores).

## See also [#see-also]

- [Every code](/en/docs/errores/codigos): The full table, grouped by where you will run into it.

- [The error envelope](/en/docs/errores): The nine types, the request_id and how to handle them in practice.

The machine-readable copy of this page lives at `GET /v1/error_codes`, unauthenticated.