Unprocessable Entity

unprocessable-entity · 422

The API sends this type when a reference names a service or database in another site.

The refusal carries code: reference_across_sites, and its fields name both ends: service and serviceSite for the service holding the reference, target and targetSite for the one it names. The 422 the API does send is idempotency-key-reused.

This type adds no members to the ones every error carries.

Common causes

  • A ${{Service.VAR}} reference names a service or database in another site.

How to fix the call

  • Read targetSite and serviceSite. A reference works only within one site, so point it at a service or database in the same site.
  • To reach a web service in another site, give its public URL, not a reference.
  • Don't retry unchanged: the same reference is refused again.

Example response

json
{
  "type": "unprocessable-entity",
  "title": "Unprocessable Entity",
  "status": 422,
  "detail": "The request could not be processed",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "method": "POST",
  "instance": "POST /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "docs": "https://ghaym.me/docs/errors/unprocessable-entity"
}