Unsupported Media Type

What it means

A request with a body wasn't sent as application/json (or application/merge-patch+json on PATCH).

This usually points at your integration's setup rather than anything the end user did. Show the end user a generic message like "Something went wrong on our end.", and log detail for your own debugging.

How to fix it

1. 1.

   The Content-Type header is missing, or set to something else (form data, text/plain, etc.).

   Set Content-Type: application/json (application/merge-patch+json for PATCH) and send a JSON-encoded body.

Where this happens

• POST/api/v0/feedback· Create a piece of feedback
• PATCH/api/v0/feedback/{feedback_id}· Update a piece of feedback
• DELETE/api/v0/feedback/{feedback_id}· Delete a piece of feedback
• POST/api/v0/feedback/{feedback_id}/notes· Add a note
• POST/api/v0/buffers· Create a buffer
• PATCH/api/v0/buffers/{buffer_id}· Update a buffer
• DELETE/api/v0/buffers/{buffer_id}· Delete a buffer
• PUT/api/v0/buffers/{buffer_id}/feedback/{feedback_id}· Add a piece of feedback to a buffer
• DELETE/api/v0/buffers/{buffer_id}/feedback/{feedback_id}· Remove a piece of feedback from a buffer
• POST/api/v0/buffers/{buffer_id}/move-all· Move all feedback to another buffer
• POST/api/v0/routing/test· Test the routing logic
• POST/api/v0/reactions· Submit a reaction
• POST/api/v0/targets· Create a target
• PATCH/api/v0/targets/{target_id}· Update a target
• DELETE/api/v0/targets/{target_id}· Delete a target
• POST/api/v0/targets/import/oas· Import targets from an OpenAPI spec
• POST/api/v0/research/queries· Ask a research question
• POST/api/v0/research/queries/{query_id}/follow_ups· Ask a follow-up question