# field_too_long

> A field is too long

- Status: 400 Bad Request
- Returned by: /api/public
- Operations: [createOnboardingLink](https://developers.rivr.io/reference/api-public/createOnboardingLink.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/field_too_long
- Try it: `GET https://developers.rivr.io/errors/simulate/field_too_long` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

A field is longer than allowed: `email` 320 characters, `contactName` and `companyName` 200, `phone` 40. `propertyName` says which.

## What your system does

Shorten the field and send again.

## 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 400 Bad Request
Content-Type: application/json

{
  "propertyName": "email",
  "message": "email is longer than 320 characters.",
  "errorCode": "field_too_long",
  "code": "field_too_long",
  "type": "https://developers.rivr.io/errors/field_too_long"
}
```

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