# onboarding_link_not_found

> Onboarding not found

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

## What it means

There is no onboarding with the id at your platform. Another platform's onboarding gets the same answer. The body used to be the framework's ProblemDetails without a code.

## What your system does

Check the id. `GET /api/public/onboarding-links` lists your onboardings.

## Is it worth retrying?

No, not without changing the call.

`retryWhen`: `after_fix`. Change the request first, as the code's page says: a value, the token, a header or a new key. Then send it.

## 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 404 Not Found
Content-Type: application/json

{
  "propertyName": "id",
  "message": "There is no onboarding with this id for your platform.",
  "errorCode": "onboarding_link_not_found",
  "code": "onboarding_link_not_found",
  "type": "https://developers.rivr.io/errors/onboarding_link_not_found"
}
```

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