NeonAPI Docs
API reference

Qwen image editing

Endpoints, request fields and response schemas for calling NeonAPI.

POST /v1/images/edits

Authentication

Use your NeonAPI API key in Authorization: Bearer YOUR_API_KEY. Keep the key in a trusted application environment.

Availability and compatibility

Check the selected model’s protocol, permissions, price and supported parameters before calling. Unsupported parameters may be rejected. Request examples use placeholders.

This page documents the Qwen-format JSON payload in the current specification. Other image models may use OpenAI-format JSON or multipart input; use the format published for the selected model.

Request fields

application/json

FieldTypeRequiredConstraintsMeaning
modelstringYes—Exact published model ID.
inputobjectYes—Input in the format required by this endpoint.
parametersobjectNo—Provider-specific generation options.

Full field definitions, nested objects and referenced schemas are available in the downloadable specification.

Request example

export NEON_API_KEY="YOUR_API_KEY"
curl https://neon-api.com/v1/images/edits \
  -H "Authorization: Bearer $NEON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "YOUR_MODEL_ID",
  "input": {
    "messages": [
      {
        "role": "user",
        "content": [
          {
            "image": "https://example.com/reference.png"
          },
          {
            "text": "Add a subtle constellation"
          }
        ]
      }
    ]
  },
  "parameters": {
    "n": 1
  }
}'

Responses

Fields vary by model and protocol. The schema below describes the documented successful response; streams use protocol-specific events.

StatusMeaning
200Successful response

Response schema

FieldTypeRequiredConstraintsMeaning
createdintegerNo——
dataobject[]No—Result items returned by this endpoint.

Download the user API OpenAPI specification

See errors and streaming & tasks.