# onboarding_not_enabled

> Onboarding isn't switched on

- Status: 403 Forbidden
- Returned by: /api/public
- Operations: [createOnboardingLink](https://developers.rivr.io/reference/api-public/createOnboardingLink.md)
- Retry (`retryWhen`): `later`
- Did anything happen? (`outcome`): `none` (It did not happen)
- Onboarding links in /api/public
- Page in the portal: https://developers.rivr.io/errors/onboarding_not_enabled
- Try it: `GET https://developers.rivr.io/errors/simulate/onboarding_not_enabled` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

Onboarding through the API isn't switched on for your platform. Rivr switches it on per platform. The body used to be a text in Swedish.

## What your system does

Contact Rivr to switch onboarding on for the platform, first in the sandbox.

## Is it worth retrying?

Only once the situation has changed, see above. Sending the same call straight away gets the same answer.

`retryWhen`: `later`. The same request can succeed, but only once something outside it has changed: another payment has finished, a permission has been given or Rivr has switched something on. Sending it again straight away gets the same answer. Follow the order or wait for the change.

## Did anything happen?

`outcome`: `none`. **It did not happen.** This call did not do what you asked for and changed nothing else that you can see or that concerns money. Where the code has an `outcomeNote`, it takes precedence.

## Example: /api/public

```http
HTTP/1.1 403 Forbidden
Content-Type: application/json

{
  "propertyName": null,
  "message": "Onboarding through the API is not enabled for your platform. Contact Rivr.",
  "errorCode": "onboarding_not_enabled",
  "code": "onboarding_not_enabled",
  "type": "https://developers.rivr.io/errors/onboarding_not_enabled"
}
```

The `title`, `detail`, `message` and `error_description` texts are exactly as the API writes them today.