unsupported_media_type

HTTP status

415

Title

Unsupported media type

Code

unsupported_media_type

What it means

The body is not sent as application/json.

It is also the catch-all of status 415: an error of that status that has no more specific code answers with this one.

What to do

Send JSON with Content-Type: application/json.

Example

Errors are RFC 9457 problem details, sent as application/problem+json. See Errors for every field.

{
  "type": "https://docs.furniops.com/errors/unsupported_media_type",
  "title": "Unsupported media type",
  "status": 415,
  "code": "unsupported_media_type",
  "detail": "An explanation of this occurrence.",
  "request_id": "req_…",
  "doc_url": "https://docs.furniops.com/errors/unsupported_media_type"
}

Operations that answer it

• PATCH /v1/agents/{agent}
• POST /v1/agreements/{kind}/acceptances
• POST /v1/assistant/conversations
• POST /v1/assistant/conversations/{conversation}/turns
• PATCH /v1/assistant/me
• POST /v1/assistant/memories
• PATCH /v1/assistant/memories/{memory}
• PATCH /v1/assistant/settings
• POST /v1/billing/credits/purchases
• POST /v1/billing/credits/purchases/preview
• PATCH /v1/billing/credits/settings
• PATCH /v1/billing/details
• POST /v1/billing/preview
• POST /v1/billing/subscription
• PATCH /v1/brand
• POST /v1/brand/claims
• POST /v1/brand/invitations/preview
• POST /v1/catalogue/visibility
• POST /v1/catalogue/withdraw
• POST /v1/demand
• POST /v1/exports
• POST /v1/mappings/{id}/confirm
• PATCH /v1/matching/judge-settings
• POST /v1/proposals/{id}/reject
• POST /v1/source-probes
• POST /v1/sources
• PATCH /v1/sources/{id}
• POST /v1/sources/{id}/categories
• PUT /v1/sources/{id}/credentials
• POST /v1/sources/{id}/records
• POST /v1/sources/{id}/runs
• POST /v1/sources/{id}/uploads
• POST /v1/test/events
• POST /v1/webhook-endpoints
• PATCH /v1/webhook-endpoints/{id}
• POST /v1/webhook-endpoints/{id}/recover
• POST /v1/webhook-endpoints/{id}/rotate-secret