NeonAPI Docs
API reference

Gemini Generate Content

Endpoints, request fields and response schemas for calling NeonAPI.

POST /v1beta/models/{model}:generateContent

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.

Path and query parameters

FieldInTypeRequired
modelpathstringYes

Request fields

application/json

FieldTypeRequiredConstraintsMeaning
contentsobject[]Yes—Gemini content turns with parts.
generationConfigobjectYes—Gemini generation and modality settings.

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/v1beta/models/YOUR_MODEL_ID:generateContent \
  -H "Authorization: Bearer $NEON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "contents": [
    {
      "role": "user",
      "parts": [
        {
          "text": "Draw a constellation"
        }
      ]
    }
  ],
  "generationConfig": {
    "responseModalities": [
      "TEXT",
      "IMAGE"
    ]
  }
}'

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
candidatesobject[]No——
usageMetadataobjectNo——

Download the user API OpenAPI specification

See errors and streaming & tasks.