# Deprecated field-first history read

This retired address for reading a trader's field history always returns `404 ROUTE_NOT_FOUND` and never returns any entries.

- Endpoint: `GET https://api.returning.ai/v1/communities/{communityId}/user-fields/{fieldId}/users/{userId}/histories`
- Section: Users and data / Field history
- Authentication: `Authorization: Bearer <API_KEY>` (Community API key)
- Permission: `None` (No permission is checked; every request returns the same 404)
- Retries: Never succeeds; don't retry, move to the current read
- Guide: hand-written
- Verified: live, 2026-09-27
- Last updated: 26 Sep 2026
- Web page: https://docs.returning.ai/api-reference/user-fields-user-field-history/deprecated-field-first-history-read

## When to use this

- Older code still calls this address and gets `404 ROUTE_NOT_FOUND`; move it to the current read.
- You're checking whether an old integration can still read history this way. It can't.

**Instead:** Use [Get a trader's field history](https://docs.returning.ai/api-reference/user-fields-user-field-history/get-a-traders-field-history.md) instead. It takes the same values, with the trader before the field in the path.

**Deprecated:** This address no longer works. Every request returns `404 ROUTE_NOT_FOUND`, whatever the key, community, field or trader.

## Authentication

- Header: `Authorization: Bearer <API_KEY>`
- Permission: `None`

This address checks no API key and no permission: every request gets the same `404`. The current read, [Get a trader's field history](https://docs.returning.ai/api-reference/user-fields-user-field-history/get-a-traders-field-history.md), needs a Community API key with the `userFields` permission, shown in the dashboard as User Fields.

## Behaviour

This is the old field-first shape of the trader field history read. It's retired and never returns entries. To move to the current read, swap the two path segments and keep everything else:

```
Old: /v1/communities/{communityId}/user-fields/{fieldId}/users/{userId}/histories
New: /v1/communities/{communityId}/users/{userId}/user-fields/{fieldIdOrName}/histories
```

The current read accepts the same field key or `_id` and trader identifier, plus optional `page` and `limit`.

## Request

### Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `communityId` | `string` | Yes | Not checked. Any value gets the same `404`. |
| `fieldId` | `string` | Yes | Not checked. In the current read, the field key or `_id` goes after the trader. |
| `userId` | `string` | Yes | Not checked. In the current read, the trader comes before the field. |

### Headers

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `Authorization` | `string` | No | Not checked. Any key, or none, gets the same `404`. (`Bearer <API_KEY>`) |

### Example request

```bash
curl --request GET \
  --url https://api.returning.ai/v1/communities/66f000000000000000000010/user-fields/kycstatus/users/3247779/histories \
  --header 'Authorization: Bearer <API_KEY>'
```

## Response

There's no success response. Every request returns `404` with `meta.code` `ROUTE_NOT_FOUND` and `meta.replacementRoute` naming the current read. The `method` and `route` fields tell this apart from a trader or field that doesn't exist.

## Errors

The code is in `meta.code`. Don't treat this `404` as an empty history.

### Do not retry

| Status | Code | What to do |
| --- | --- | --- |
| 404 | `ROUTE_NOT_FOUND` | The address is retired. Call Get a trader's field history, `GET /v1/communities/{communityId}/users/{userId}/user-fields/{fieldIdOrName}/histories`, instead. `meta.replacementRoute` names it. This 404 doesn't mean the trader or field is missing, or that the history is empty. |

**Retries:** Don't retry. This address never succeeds, however often you call it or with whatever key. Move the call to [Get a trader's field history](https://docs.returning.ai/api-reference/user-fields-user-field-history/get-a-traders-field-history.md) instead.

## Next step

- [Get a trader's field history](https://docs.returning.ai/api-reference/user-fields-user-field-history/get-a-traders-field-history.md): `GET /v1/communities/{communityId}/users/{userId}/user-fields/{fieldIdOrName}/histories`. The current read, with paging and the newest entry first. Put the trader before the field in the path.
- [Or read all of a trader's fields with Get user field histories for a specific user](https://docs.returning.ai/api-reference/user-fields-user-field-history/get-user-field-histories-for-a-specific-user.md): `GET /v1/communities/{communityId}/users/{userId}/user-field-histories`.