Content types - Neuro Developer Documentation

Agent API resources use the HTTP Content-Type header to interpret request bodies and Accept to select a response representation. Send both headers even when an operation currently documents only one representation; individual resources may support additional representations over time.

Common representations

Media type	Meaning
`application/json`	JSON-encoded request or response
`text/plain`	Plain text
`text/xml`	XML document

Most documented Agent API operations use POST with JSON. Follow the generated operation’s request body instead of assuming every resource accepts every media type.

JSON request

POST /Agent/Account/Info HTTP/1.1
Host: <NEURON_HOST>
Referer: https://app.example.com/
Authorization: Bearer <JWT>
Accept: application/json
Content-Type: application/json

{}

An operation with no input fields still receives {} when its request body is required.

Binary and attachment data

Some operations represent attachment or binary content inside their documented JSON or XML request. Do not assume a generic /files endpoint or multipart/form-data contract. Use the exact request schema and encoding documented for that operation.

Content negotiation failures

400 Bad Request can indicate that the body does not match the operation’s schema.
406 Not Acceptable can indicate that the requested response representation is unsupported.
415 Unsupported Media Type may be returned by HTTP infrastructure when the request representation is unsupported; confirm the deployed behavior before depending on it.

See API basics and the generated endpoint reference for operation-specific requirements.