Overview

Nureta is the No.1 unfiltered NSFW AI video platform, trusted by 50,000+ users. The Nureta Developer API is the same engine, open to your code. It turns prompts and reference media into video, images and scripts.

Every endpoint shares one authentication model, one task lifecycle (create → poll → terminal), and one set of callbacks and errors. This page documents them. The details for each medium are under Video, Image and Script.

What the API does

Video works in two modes. With the seahorse-* models, both run up to 180 seconds (3 minutes) as stitched multi-segment scenes. The direct Seedance models (seedance2.0-fast, seedance2.0-pro) render single clips of 5, 8, 10, 12 or 15 seconds, without scenes.

Video runs at 480p–1080p and 5s–180s. The API is built for automated, scalable production with granular control. You can:

• generate in batches from your own pipeline
• supply your own storyboard segments[], with a per-shot explicit flag
• pin first/last frames
• turn on auto chaining for smoother joins between the shots of a long video (the render takes longer, the price stays the same)
• review and edit the draft storyboard before rendering (beats, durations, background plates, shared world/wardrobe/character)
• attach up to 9 images (reference images and pinned frames count together) and optional audio
• generate characters and backgrounds, save them in your Library, and use them in any video by ID
• receive signed webhooks

The Nureta consumer app (nureta.ai) runs on this same API. The Nureta app and the Nureta Developer API both offer 480p, 720p and 1080p.

Content policy

The API is built for adult content: explicit adult scenes that mainstream APIs refuse. Nureta's content policy governs its use. It allows adults only, with no minors, no real people without consent and no public figures. The API rejects reference images that look like a public figure automatically.

Base URL

All endpoints are served from https://developer.nureta.ai. The examples use a $NURETA_URL shell variable for it. Set it once:

export NURETA_URL="https://developer.nureta.ai"

SDKs

SDKs are available on request. Every example works with plain curl. There is no proprietary transport, just REST.

Authentication

Every request except the model lists (GET /api/v3/models, /api/v3/images/models, /api/v3/scripts/models) authenticates with an API key. Create one on the API keys page. Pass it as a bearer token:

Authorization: Bearer sk-...
Content-Type: application/json

You can revoke a key on the API keys page. When you request deletion of your account, every key of the account is revoked at once. Undoing the deletion does not restore the keys. Create new ones.

Balance

Generations are billed to your balance at the posted model prices. GET /api/v3/account returns your current balance:

curl -s "$NURETA_URL/api/v3/account" -H "Authorization: Bearer sk-..."
# => {"balance_usd": 12.5}

Quick start

1. Create an API key on the API keys page.
2. Create a task. The response is 201 with the task view.
3. Poll the task until status is succeeded or failed. Or pass callback_url at create time to receive a signed webhook instead.

# 1. Create a video task.
curl -s -X POST "$NURETA_URL/api/v3/contents/generations/tasks" \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{"model": "seahorse-480p", "content": [{"type": "text", "text": "your prompt"}], "duration": 5}'
# => HTTP 201 with the task view: {"id": "cgt-...", "status": ..., ...}

# 2. Poll it.
curl -s "$NURETA_URL/api/v3/contents/generations/tasks/cgt-..." \
  -H "Authorization: Bearer sk-..."
# => {"id": "cgt-...", "status": "succeeded", "content": {"video_url": "..."}, "usage": {...}}

Image and script tasks work the same way on their own routes.

Tasks

Video, image and script tasks follow the same pattern. Each kind has its own routes:

The task view

Create, retrieve and list return the same shape: the task view. It includes your inputs: prompt, for video and image the reference media as [{url, type}], and for video the pinned first_frame and last_frame when they are set. Video list items do not carry re-render runs. GET the task for those.

Delete a task

A task that is not finished returns 409 Conflict. Cancel an edit-mode draft first (POST …/cancel), or wait until a running task finishes. Deleting a video stops any re-render of it that is still running and refunds that run. If the run cannot be stopped, the delete returns 409 Conflict. Try again shortly.

You can delete at most 10 tasks per minute per account. More returns 429 RateLimitExceeded.

Upload a reference image

POST /api/v3/contents/uploads gives you a short-lived signed URL for a reference image. Use it when you do not already host the image at a public URL. It authenticates with your API key. Uploading is free: you are billed only when you create a generation. Your balance must be above $0 to upload; otherwise the request returns 403 AccountOverdueError.

1. Ask for a signed upload URL.
2. PUT the image bytes straight to storage.
3. Pass the returned assetUrl as an image_url.url in a generation task.

# 1. Ask for a signed upload URL.
UPLOAD=$(curl -s -X POST "$NURETA_URL/api/v3/contents/uploads" \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{"fileName": "ref.jpg", "contentType": "image/jpeg"}')
# => {"uploadUrl": "https://...signed...", "assetUrl": "https://.../ref.jpg",
#     "contentType": "image/jpeg", "previewUrl": "https://...signed.../ref.jpg"}

# 2. Upload the bytes to the signed URL (same Content-Type, no auth header).
UPLOAD_URL=$(echo "$UPLOAD" | jq -r .uploadUrl)
ASSET_URL=$(echo "$UPLOAD" | jq -r .assetUrl)
curl -s -X PUT "$UPLOAD_URL" -H "Content-Type: image/jpeg" --data-binary @ref.jpg

# 3. Reference ASSET_URL as an image_url when you create a generation task:
#    {"type": "image_url", "image_url": {"url": "'"$ASSET_URL"'"}}

Request fields

Response fields

Pass assetUrl, not previewUrl, as the task input.

Library

Save characters and backgrounds, and use them in any video by their ID. Describe a person or a place, the API draws 2 images, and you save the one you want. You can also save a background that you upload. Your saved items belong to your account only: no other account can see or use them. A saved item is kept for 1 year after you save it, then it is deleted.

A character is always one that the library draws itself. You cannot save an uploaded photo of a person, or the result of an image task: an uploaded photo of a person is used for one task only. Every character is an original adult, 20 or older; the description is checked before anything is drawn. An uploaded background is checked before it is saved.

You can also generate and manage items on the Library page of the console.

Generate, save and use

# 1. Generate 2 candidate images ($0.10).
GEN_ID=$(curl -s -X POST "$NURETA_URL/api/v3/library/generations" \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{"kind": "character",
       "spec": {"sex": "female", "age_group": "30s", "style": "anime",
                "hair": "short red hair", "outfit": "green raincoat"},
       "prompt": "freckles, a calm smile",
       "time_zone": "Asia/Tokyo"}' | jq -r .id)

# 2. Poll until status is done, rejected or failed (usually under a minute).
curl -s "$NURETA_URL/api/v3/library/generations/$GEN_ID" -H "Authorization: Bearer sk-..."
# => {"id": "gen_...", "status": "done",
#     "candidates": [{"ref": "gen_...#0", "thumb_url": "https://..."}, ...], ...}

# 3. Save the candidate you want. The name is optional: without one, the API names it.
curl -s -X POST "$NURETA_URL/api/v3/library/items" \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{"name": "Mira", "from": "'"$GEN_ID"'#0"}'
# => 201 {"id": "chr_...", "ref": "library:chr_...", "kind": "character", "source": "generated", "name": "Mira", ...}

# 4. Use it in a video.
curl -s -X POST "$NURETA_URL/api/v3/contents/generations/tasks" \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{"model": "seahorse-480p", "content": [
        {"type": "text", "text": "She waits by the window, rain outside."},
        {"type": "library_item", "library_item": {"id": "chr_..."}}
      ]}'

Generation fields

Save fields

Send exactly one of from or image_url. A body with both, or with neither, returns 422 library_bad_source.

# Upload a background, then save it.
curl -s -X POST "$NURETA_URL/api/v3/library/items" \
  -H "Authorization: Bearer sk-..." \
  -H "Content-Type: application/json" \
  -d '{"kind": "background", "image_url": "https://.../room.jpg", "consent": true, "name": "Rainy loft"}'
# => 201 {"id": "bg_...", "ref": "library:bg_...", "kind": "background", "source": "upload", "name": "Rainy loft", ...}

The API downloads the image once and checks it before it saves it. An upload save answers within about 75 seconds: wait at least 90 seconds before you give up on the call. An image over 15 MB or 40 megapixels returns 422 library_upload_too_large. An image that cannot be downloaded, is not a JPEG, PNG or WebP, or is animated, returns 422 library_upload_unreadable. When the image may show a minor, the save returns 422 library_upload_rejected. When the check cannot decide, it returns 422 library_upload_unchecked: try again later.

The generation

When the library does not answer. Generate can return 503 LibraryUnavailable with a pending_id (lgc_...) after you were charged: the generation may have started. Poll GET /api/v3/library/generations/{pending_id}. It shows status: "pending" until the API knows, then the generation itself. If it never starts, it is refunded within an hour.

Pricing and refunds. A generation costs $0.10 and is charged when you create it. When it ends rejected or failed (no image), the $0.10 is refunded automatically, also if you never poll it. A generation that ends done with 1 image (a draw still failed after its retries) is not refunded. Saving is free.

The item

Use an item in a video

Send {"type": "library_item", "library_item": {"id": "chr_..."}} in the content of a video task. A character is a reference image of a person. A background is a reference image of the place. Storyboard edits take library:bg_... and library:chr_... in their image fields. See Library items in a video.

The video is checked like any video with an uploaded image. A library item is not available for first or last frames, for image tasks, or with the direct Seedance models.

Delete an item

The item is deleted at once. A new task or storyboard edit that uses it, and the render of a draft that holds it, fails with 404 library_item_not_found. A task that is already running finishes. Its image and preview are deleted about an hour later, when no running task uses them.

Limits

A day ends at midnight in your time_zone. A limit returns 409 library_limit_reached with limit (max_characters, max_backgrounds, daily_generations, daily_saves or running_generations) and, for a daily limit, resets_at. The upload checks return 429 library_upload_limit with limit (daily_upload_checks with resets_at, or one_at_a_time).

Library errors

Errors use the error format. A library error can also carry limit, resets_at and categories.

Media links are private

Uploaded references and generated outputs are stored privately.

Media can only be referenced by the account that uploaded or generated it. Using another account's URL returns 403 MediaNotOwned.

Callback webhook

When callback_url is provided on task creation, Nureta Developer POSTs the terminal task view to that URL. This happens when the task becomes succeeded or failed, or when you cancel an edit-mode draft (the body then has status: "cancelled").

The JSON body of generation.task.completed and generation.task.planned is the same task view that retrieving the task returns.

Delivery

Events

Headers

POST /webhooks/nureta-developer HTTP/1.1
Content-Type: application/json
User-Agent: tokenstore-webhook/1.0
X-Nureta-Event: generation.task.completed
X-Nureta-Task-Id: cgt-...
X-Nureta-Delivery: 00000000-0000-0000-0000-000000000000
X-Nureta-Timestamp: 1781220120
X-Nureta-Signature: sha256=<hex-hmac>  # only when callback_secret was provided

Every X-Nureta-* header is also sent under its legacy X-Tokenstore-* name with the identical value (for example X-Tokenstore-Event, X-Tokenstore-Signature). The User-Agent stays tokenstore-webhook/1.0. This keeps existing receivers working. Use either name. New integrations should read X-Nureta-*.

Signature verification

When callback_secret was provided:

1. Compute an HMAC-SHA256 hex digest over X-Nureta-Timestamp + "." + rawBody, using the secret.
2. Remove the sha256= prefix from X-Nureta-Signature (the same value as X-Tokenstore-Signature).
3. Compare the rest with your digest in constant time.

Safety rules for callback_url

• It must use HTTPS.
• It must not include credentials.
• It must be 2048 characters or fewer.
• It must not target localhost, or private, loopback, link-local, multicast or otherwise reserved IP ranges.

An IP literal or a localhost name is rejected with 400 InvalidParameter. A hostname is checked at each delivery. If it resolves to such an address, the task is still accepted, but no delivery to it succeeds.

Rate limits

Every request made with an API key counts toward that key's rate limit. This includes task creation, status polling, storyboard edits and uploads. New keys default to 10 requests/second. You can adjust each key between 1 and 100 req/s on the API keys page.

Exceeding the limit returns 429 RateLimitExceeded with standard RateLimit headers. Back off briefly and retry.

Some routes have an additional fixed cap:

Errors

Errors return a JSON body {"error": {"code": "...", "message": "..."}}:

The re-render routes have their own codes (IdempotencyKeyReused, rerender_running). See Fix part of a video. The library has its own codes (library_*). See Library errors.

Task errors

A task that fails has status: "failed" and an error object. Its price is refunded automatically. error.code is one of:

Other upstream failure codes can also appear, with the message "Generation failed. You have been refunded."

Changelog

2026-11-03

• POST /api/v3/contents/uploads accepts only image, video and audio types a task can use (see Upload a reference image). Without contentType, the type comes from the fileName extension; with neither, the request returns 400 InvalidParameter. The response has a new contentType field: send it on the PUT.
• An upload with a balance of $0 or less returns 403 AccountOverdueError.
• The upload presign cap (30 per minute) is now per account, not per key.
• Re-render: at most one quote at a time per video and two per account (429 quote_running). A replay of a start that is still in progress returns 503 start_in_progress; retry it with the same Idempotency-Key.