Content CMS reverse proxy

GET /v1/content

POST /v1/content

PUT /v1/content

PATCH /v1/content

DELETE /v1/content

HEAD /v1/content

OPTIONS /v1/content

GET /v1/content/{path}

POST /v1/content/{path}

PUT /v1/content/{path}

PATCH /v1/content/{path}

DELETE /v1/content/{path}

HEAD /v1/content/{path}

OPTIONS /v1/content/{path}

devhttps://api.sandbox.ovok.com

Catch-all that forwards every method (GET/POST/PUT/PATCH/DELETE/HEAD/OPTIONS) under /v1/content/* to the project-scoped Payload CMS instance. The Medplum project id is injected as the Payload tenant header, so multi-tenant scoping is automatic — you address Collection/<id> or Collection?where=... exactly as the Payload REST API expects. Response shape and status code are whatever Payload returns; refer to your collection schemas (and the payloadcms.com/docs/rest-api reference) for the per-collection details. 502 surfaces when Payload itself is unreachable.

Responses

Code	Description
200	Success.
400	The request could not be operated by the server.
401	The resource owner or authorization server denied the request.
404	The requested resource could not be found.
422	The request could not be validated by the server.
500	The server encountered an unexpected condition. Please try again later.

200 → ContentProxyResponseDto (application/json)

Payload CMS REST response. Concrete shape (fields, pagination, status code) depends on the target collection and interaction — see payloadcms.com/docs/rest-api and the project-defined collection schema.

Additional properties allowed.

Example

{
  "id": "6650f4a3a1b9e0c8c4f3a3b2",
  "collection": "posts",
  "title": "Hello world",
  "updatedAt": {}
}