Use the generated operation page as the contract for path, method, security override, required fields, and documented success shape.
Requests
- Build URLs as
https://<NEURON_HOST>/Agent/<GROUP>/<RESOURCE>.
- Use the generated method. Most current operations use
POST; GET /Agent/Account/DomainInfo is the documented exception.
- Send
Content-Type: application/json.
- Send
{} when a documented POST operation has an empty JSON request.
- Preserve field names and capitalization exactly; examples include both lower-camel-case fields and capitalized collection fields.
- Do not add a shared
/v1 prefix.
Responses
The specification documents 200 success responses. Some contain a JSON object with required fields, some allow additional deployment fields, and some have no documented body schema. Validate required fields before using them and ignore unknown fields unless the operation says otherwise.
A 200 response shape does not establish business completion for an asynchronous workflow. Persist the returned identifier and observe the later state using the mechanism verified for that workflow.
Non-success response bodies are not yet defined by one platform-wide schema. See Error handling.