Returning.AIDocs
v1

API reference / User Fields / User Field History

.md

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.

Last updated 28 Oct 2026API v1

Method
GET
Path
https://api.returning.ai/v1/communities/{communityId}/user-fields/{fieldId}/users/{userId}/histories
Permission
None
Retries
Never succeeds; don't retry, move to the current 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.

Authentication#

Header
Authorization: Bearer <API_KEY>
Permission
NoneNo permission is checked; every request returns the same 404

This address checks no API key and no permission: every request gets the same 404. The current read, Get a trader's field history, 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:

TEXT
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#

communityId#stringREQUIRED
Not checked. Any value gets the same 404.

Eg"66f000000000000000000010"

fieldId#stringREQUIRED
Not checked. In the current read, the field key or _id goes after the trader.

Eg"kycstatus"

userId#stringREQUIRED
Not checked. In the current read, the trader comes before the field.

Eg"3247779"

Headers#

Authorization#stringOPTIONAL
Not checked. Any key, or none, gets the same 404.

RuleBearer <API_KEY>

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.

{
  "meta": {
    "status": "error",
    "statusCode": 404,
    "method": "GET",
    "route": "/v1/communities/{communityId}/user-fields/{fieldIdOrName}/users/{userIdentifier}/histories",
    "attemptedMethod": "GET",
    "documentedRouteId": "user-fields/history/list",
    "documentedRoute": "GET /v1/communities/{communityId}/user-fields/{fieldId}/users/{userId}/histories",
    "replacementRoute": "GET /v1/communities/{communityId}/users/{userId}/user-fields/{fieldIdOrName}/histories",
    "code": "ROUTE_NOT_FOUND"
  },
  "message": "API request rejected error.",
  "detail": "This documented legacy route does not exist.",
  "solution": "Read error detail and try again."
}

Errors#

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

Do not retry01

404ROUTE_NOT_FOUNDDo not retry
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 instead.

{
  "meta": {
    "status": "error",
    "statusCode": 404,
    "method": "GET",
    "route": "/v1/communities/{communityId}/user-fields/{fieldIdOrName}/users/{userIdentifier}/histories",
    "attemptedMethod": "GET",
    "documentedRouteId": "user-fields/history/list",
    "documentedRoute": "GET /v1/communities/{communityId}/user-fields/{fieldId}/users/{userId}/histories",
    "replacementRoute": "GET /v1/communities/{communityId}/users/{userId}/user-fields/{fieldIdOrName}/histories",
    "code": "ROUTE_NOT_FOUND"
  },
  "message": "API request rejected error.",
  "detail": "This documented legacy route does not exist.",
  "solution": "Read error detail and try again."
}

Next step#

Get a trader's field historyGET/v1/communities/{communityId}/users/{userId}/user-fields/{fieldIdOrName}/historiesThe current read, with paging and the newest entry first. Put the trader before the field in the path.