Person required
type | https://docs.frem.sh/reference/api/errors/person-required |
| HTTP status | 403 Forbidden |
What it means
The endpoint is per person, and the token does not act for a frem.sh user: for example a runner job token, a registry robot, or a token minted for a service.
Example detail messages returned with this error:
- The event feed is per person, and this token does not act for a frem.sh user. Use a token minted by a person,
fremforge auth login, or an OBO token. - This account cannot sign in, so it reads no events.
What to do
Use a credential that acts for a person: a token you minted yourself, the token from fremforge auth login, or a token your agent exchanged on your behalf (OBO). An agent reads with its person’s access.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/person-required",
"title": "Forbidden",
"status": 403,
"detail": "..."
}Branch on type, not on title or detail - those are human-readable and may be reworded.