Diffio documentation

Documentation

Guides and references for restoring speech audio, reviewing transcripts, and integrating Diffio.

Speech focused restorationAudio and video supportTranscripts and A/B review

Browse models Developer quickstart

Build

Developers

Set up API keys, authenticate requests, and track restoration jobs.

Integrate

API reference

Dive into endpoints, payloads, and model parameters.

Models

Choose the balance of speed and fidelity that fits your workflow.

Fastest turnaround for previews and quick cleanups.

Model iddiffio-2-flash

Low latency option for high volume queues.
Great for rapid iterations and early reviews.
Balanced cleanup for shorter clips.

Reliable baseline model for consistent cleanup.

Model iddiffio-2

Steady results for interviews and podcasts.
Good balance of speed and quality.
Stable output across large batches.

Best quality reconstruction for demanding speech.

Model iddiffio-3.4

Improved clarity in noisy rooms.
Sharper consonants and tighter detail.
Stronger alignment for transcript review.

Explore all models

Browse by capability

Find guidance for the tools you use most in Diffio.

Audio restoration

Remove noise, hiss, and echo while keeping speech clear.

Video support

Extract and enhance speech from video uploads.

Diffio offers three speech restoration models, each tuned for a different balance of speed, cost, and clarity. Choose a model for every generation, and run multiple generations on the same project to compare results.

Model lineup

Use the model id in the SDK model field or call the matching REST endpoint. Each model focuses on speech, with different performance and fidelity targets.

Fastest turnaround for previews and quick cleanups.

Best for: Rapid previews, high volume queues.

Low latency option for high volume queues.
Great for rapid iterations and early reviews.
Balanced cleanup for shorter clips.

Reliable baseline model for consistent cleanup.

Best for: Production cleanup with balanced speed and fidelity.

Steady results for interviews and podcasts.
Good balance of speed and quality.
Stable output across large batches.

Best quality reconstruction for demanding speech.

Best for: Critical clarity work and detailed transcripts.

Improved clarity in noisy rooms.
Sharper consonants and tighter detail.
Stronger alignment for transcript review.

Choosing a model

Start with a fast preview, then move to higher fidelity for final delivery. Keep the same project and create a new generation each time you change models.

diffio-2-flash for rapid previews or high volume queues.
diffio-2 for balanced speed and clarity when throughput matters.
diffio-3.4 for the highest clarity on noisy or distant speech.

Plan access

Diffio 2.0 and Diffio 3.4 require a paid plan. Review billing details for plan options.

Endpoint mapping

Model ids map to specific generation endpoints. Use these paths when calling the REST API directly.

Model id	Label	Endpoint
`diffio-2-flash`	Diffio 2.0 Flash	`POST /v1/diffio-2.0-flash-generation`
`diffio-2`	Diffio 2.0	`POST /v1/diffio-2.0-generation`
`diffio-3.4`	Diffio 3.4	`POST /v1/diffio-3.4-generation`

Next steps

Quickstart

Restore speech audio in a single request.

Full API guide

Walk through projects, generations, and downloads end to end.

API reference

Review endpoints, headers, and error responses.

Template notes

Use this page to document the goal, flow, and core requests for this topic. We will expand each section once the API spec is locked.

Review API pricing

Summary

Outline the intent of this section, the key audience, and the most important takeaways.

Examples

Show a realistic request and response, plus any required headers.

Next steps

Link to related guides, or point to the API reference when it is ready.

Template notes

Use this page to document the goal, flow, and core requests for this topic. We will expand each section once the API spec is locked.

Review API pricing

Summary

Outline the intent of this section, the key audience, and the most important takeaways.

Examples

Show a realistic request and response, plus any required headers.

Next steps

Link to related guides, or point to the API reference when it is ready.

Answers to common billing questions for Diffio API plans, including upgrades, billing thresholds, and invoices.

Upgrading to the Developer tier

What happens when I upgrade to the Developer tier?

When you upgrade, there is no immediate charge. You are billed for usage at month end or when you reach progressive billing thresholds, which are listed below.

Usage is billed per second based on processing time, with a minimum billable duration of 60 seconds per generation request.

Example: a 30 second request is billed as 60 seconds. An 80 second request is billed as 80 seconds.

To upgrade from the Free tier to the Developer tier, add a valid payment method, including a credit card, a United States bank account, or a SEPA debit account.

Your upgrade takes effect immediately. Billing occurs at the end of your monthly billing cycle or when you cross the progressive thresholds of $1, $10, $100, $500, and $1,000.

What are the benefits of upgrading?

The Developer tier is designed for developers and teams who need more capacity with pay as you go pricing.

Usage based billing for production workloads
Spend limits with budget alerts
Audit logs with 7 day retention

Can I downgrade back to the Free tier after I upgrade?

Yes, you can downgrade to the Free tier at any time from your account settings under Billing.

When you downgrade, we issue a final invoice for any outstanding usage that has not yet been billed. You will need to pay this invoice before the downgrade is complete.

After downgrading:

Your account returns to Free tier rate limits and restrictions
You lose access to Developer tier benefits
Usage based charges stop immediately
You can upgrade again whenever you need more capacity

Understanding the Diffio billing model

How does the billing cycle work?

Diffio uses a monthly billing cycle. You receive an invoice in arrears for usage. New Developer tier accounts also follow progressive billing thresholds to ease into pay as you go usage.

How does progressive billing work?

During the progressive billing phase, an invoice is triggered and payment is deducted when your cumulative usage reaches $1, $10, $100, $500, and $1,000.

Special billing for customers in India

Customers with a billing address in India have different thresholds. For India customers, the thresholds are $1, $10, and then every $100 thereafter. The $500 and $1,000 thresholds do not apply.

These thresholds are one time for most customers. Once you cross the $1,000 lifetime usage threshold, only monthly billing continues. For India customers, billing continues at each $100 increment.

What if I do not reach the next threshold?

If you do not reach the next threshold, your usage is billed on your regular end of month invoice.

Example

You cross $1, you are charged immediately.
You then use $2 more for the month. Lifetime usage is $3, still below $10.
The $2 is invoiced at the end of your monthly billing cycle, not immediately.

When is payment withdrawn from my account?

Payment is withdrawn automatically from your connected payment method each time an invoice is issued. This can happen during the progressive billing phase or at the end of each monthly billing cycle.

We only bill you once your usage reaches at least $0.50. If you see a total charge under $0.50, there is no action required on your end.

Monitoring your spending and usage

How can I view my current usage and spending in near real time?

You can monitor usage in the Diffio dashboard. Visit the Usage page to track usage across models and see how consumption aligns with pricing.

Can I set spending limits or receive budget alerts?

Yes. Developer tier accounts can set spend limits and receive budget alerts. Once billing is enabled, configure limits in the dashboard to keep costs on track.

Invoices, billing info, and credits

Where can I find my past invoices and payment history?

You can view and download invoices in the Diffio dashboard under Settings, then Billing. If billing is not yet enabled for your account, this area will appear once it is available.

Can I change my billing info and payment method?

Yes, update billing details anytime from Settings, then Billing in the Diffio dashboard.

What payment methods do you accept?

Diffio accepts credit cards (Visa, MasterCard, American Express, Discover), United States bank accounts, and SEPA debit accounts.

Are there promotional credits or trial offers?

New API Developer upgrades receive a one time $5 usage credit after you add a payment method. The credit applies to future API invoices once checkout completes.

Common billing questions and troubleshooting

How are refunds handled, if applicable?

Refunds are handled on a case by case basis. Contact our support team at support@diffio.ai for assistance.

What if I believe there is an error in my bill?

Check your Usage and Billing pages first. If you still believe there is an issue, contact support at support@diffio.ai.

Under what conditions can my account be suspended due to billing issues?

Account suspension or restriction can occur after prolonged non payment or consistently failed payment attempts. We handle each case individually. If your account is impacted, contact support for guidance.

What happens if my payment fails?

Update your payment method to ensure successful processing. We may retry payments, and failed payments can result in service suspension. We will email you if an invoice is unpaid.

What should I do if my billing question is not answered here?

Contact our support team at support@diffio.ai.

Restore speech audio by creating a project with your media file, running multiple generations, and downloading results. This quickstart sets your API key, installs the SDK, and walks through each step.

Prerequisites

Before you start, have these ready.

A Diffio API key with read and write permissions.
A speech focused audio file, for example sample.wav.
Python 3.8 or later, or Node 18 or later.

Workflow overview

Projects hold your media. Each project can have multiple generations, often one per model, and you can download each result.

A project contains your media. Create multiple generations under it, then download each restored file.

Using the Diffio SDK

1
Create an API key
Create an API key in the developer dashboard and store it as a secret. Pass the key on every request using the Authorization header (X-Api-Key and Xi-Api-Key also work).
.env
DIFFIO_API_KEY=diffio_live_...
2
Install the SDK
Install the Diffio SDK for Python or Node, then load the API key from the environment.
Python
pip install diffio python-dotenv
Node.js
npm install diffio dotenv
SDK source code
Browse the SDK repositories on GitHub: diffio-js and diffio-python .

Create a file named example.py or example.mjs. Then create a project for your media file. The SDK uploads the file as part of project creation.

Python

from dotenv import load_dotenvfrom diffio import DiffioClientimport osload_dotenv()client = DiffioClient(apiKey=os.getenv("DIFFIO_API_KEY"))file_path = "sample.wav"project = client.create_project(    filePath=file_path,)

Create three generations, one per model, so you can compare the results.

Python

models = ["diffio-2-flash", "diffio-2", "diffio-3.4"]generations = []for model in models:    generation = client.create_generation(        apiProjectId=project.apiProjectId,        model=model,    )    generations.append({"model": model, "generation": generation})

Add this block near the end of the file, then poll each generation and download results. Move the node:fs import to the top of the file with the other imports.

Python

import timefor item in generations:    status = "queued"    while status not in ("complete", "failed"):        progress = client.generations.get_progress(            generationId=item["generation"].generationId,            apiProjectId=project.apiProjectId,        )        status = progress.status        print(item["model"], "status:", status)        if status not in ("complete", "failed"):            time.sleep(5)    if status != "complete":        raise SystemExit(f"Generation failed for {item['model']}")    output_name = f"restored-{item['model']}.mp3"    client.generations.download(        generationId=item["generation"].generationId,        apiProjectId=project.apiProjectId,        downloadFilePath=output_name,        downloadType="mp3",    )

Troubleshooting

If you receive 401Unauthorized, treated as auth error. or 403Forbidden, treated as permission error., confirm the API key is valid and has read and write permissions. A 402Payment required, billing issue such as paymentFailed. API usage can be blocked until billing is updated. error indicates a billing issue such as a spend limit or a paymentFailed billing hold. API usage can be blocked until billing is updated. A 409Conflict, treated as not ready yet. error indicates the generation is not complete yet, poll progress and retry the download.

This guide expands on the quickstart and walks through most of the Diffio SDK surface. You will create projects, run generations, track progress, download results, list resources, and set up webhooks so your app can react to status changes. If you want the shortest path, start with the Quickstart.

Prerequisites

Before you start, have these ready.

A Diffio API key with read and write permissions.
A speech focused audio file, for example sample.wav.
Python 3.8 or later, or Node 18 or later.

Workflow overview

Projects hold your media. Each project can have one or more generations, and you can download each result.

A project contains your media. Create multiple generations under it, then download each restored file.

Prefer webhooks in production

Polling works for quick tests. For production, use webhooks so Diffio can notify you when a generation completes. See the Webhooks guide.

Using the Diffio SDK

Follow these steps in order, and add each block to the same file. You will create a project, run a generation, wait for completion, and download the restored audio.

1
Create an API key
Create an API key in the developer dashboard and store it as a secret. Pass the key on every request using the Authorization header (X-Api-Key and Xi-Api-Key also work).
.env
DIFFIO_API_KEY=diffio_live_...
Tip
Store your API key as a managed secret instead of committing it to source control.
2
Install the SDK
Install the Diffio Python or Node SDK, then load your API key from an environment file.
Python
pip install diffio python-dotenv
Node.js
npm install diffio dotenv
SDK source code
Browse the SDK repositories on GitHub: diffio-js and diffio-python .
Note
Use Node 18 or later so fetch is available without extra packages.

Create a file named full_guide.py or full_guide.mjs. Then initialize the client and set global request options like timeouts and retries.

Python

from dotenv import load_dotenvfrom diffio import DiffioClient, RequestOptionsimport osload_dotenv()client = DiffioClient(    apiKey=os.getenv("DIFFIO_API_KEY"),    requestOptions=RequestOptions(        timeoutInSeconds=60,        maxRetries=2,    ),)

Per call overrides

Every SDK call accepts requestOptions so you can override timeouts, retries, headers, or the API key for a single request.

Create a project for your media file. The SDK uploads the file as part of project creation. You can attach optional metadata through params.

Python

file_path = "sample.wav"project = client.create_project(    filePath=file_path,    fileFormat="wav",    params={        "source": "full-guide",        "notes": "First upload from docs",    },)

Start a generation with the model you want. Use sampling or params for model specific settings.

Python

generation = client.generations.create(    apiProjectId=project.apiProjectId,    model="diffio-3.4",    sampling={"preset": "balanced"},    params={"tag": "docs"},)

Poll until the generation completes. The wait helper returns the full progress object.

Python

progress = client.generations.wait_for_complete(    generationId=generation.generationId,    apiProjectId=project.apiProjectId,    pollInterval=3.0,    timeout=900.0,    showProgress=True,)print("Final status:", progress.status)

Shortcut

You can combine creation and polling with client.generations.create_and_wait in Python or client.generations.createAndWait in Node.

7
Download results
Fetch the download URL, then save the restored audio. Signed URLs expire, so request a new URL if needed.
Python
client.generations.download( generationId=generation.generationId, apiProjectId=project.apiProjectId, downloadFilePath="restored.mp3", downloadType="mp3",)
Node.js
import fs from "node:fs"const download = await client.generations.getDownload({ generationId: generation.generationId, apiProjectId: project.apiProjectId, downloadType: "audio",})const audioResponse = await fetch(download.downloadUrl)const audioBuffer = Buffer.from(await audioResponse.arrayBuffer())fs.writeFileSync("restored.mp3", audioBuffer)
Troubleshooting
If you receive 401Unauthorized, treated as auth error. or 403Forbidden, treated as permission error., confirm the API key is valid and has read and write permissions. A 402Payment required, billing issue such as paymentFailed. API usage can be blocked until billing is updated. error indicates a billing issue such as a spend limit or a paymentFailed billing hold. API usage can be blocked until billing is updated. A 409Conflict, treated as not ready yet. error indicates the generation is not complete yet, poll progress and retry the download.

Manage projects and generations

Use list endpoints to build dashboards, resume work, or review past generations.

Python

projects = client.projects.list()for project in projects.projects:    print(project.apiProjectId, project.status, project.originalFileName)

Python

generations = client.projects.list_generations(    apiProjectId=project.apiProjectId,)for generation in generations.generations:    print(generation.generationId, generation.status, generation.modelKey)

Restore audio in one call

The audio isolation helper creates the project, starts a generation, waits for completion, and downloads the restored audio in one call.

Python

from dotenv import load_dotenvfrom diffio import DiffioClientimport osload_dotenv()client = DiffioClient(apiKey=os.getenv("DIFFIO_API_KEY"))file_path = "sample.wav"audio_bytes, info = client.audio_isolation.restore_audio(    filePath=file_path,    model="diffio-3.4",    downloadType="mp3",)if info["error"]:    raise SystemExit(info["error"])with open("restored-one-call.mp3", "wb") as handle:    handle.write(audio_bytes)

Metadata

The helper returns a metadata object with status, errors, and download info you can log or store alongside the result.

Use webhooks for status updates

Webhooks let Diffio notify your service when a generation changes status. This is a condensed walkthrough. For full details, see the Webhooks guide.

1
Create a webhook endpoint
Follow the webhook creation steps in the docs, then open the developer dashboard to add your endpoint URL and choose events. Save the signing secret for verification.
Endpoint scope
Each API key owns its own webhook endpoints and signing secrets.

Use the Diffio SDK helpers to verify signatures against the raw request body, not a parsed JSON object.

Python

from fastapi import FastAPI, Request, HTTPExceptionfrom diffio import DiffioClientimport osapp = FastAPI()client = DiffioClient(apiKey=os.environ["DIFFIO_API_KEY"])@app.post("/webhooks/diffio")async def diffio_webhook(request: Request):    payload = await request.body()    try:        event = client.webhooks.verify_signature(            payload=payload,            headers=request.headers,            secret=os.environ["DIFFIO_WEBHOOK_SECRET"],        )    except Exception:        raise HTTPException(status_code=400, detail="Invalid signature")    print("Webhook received", event.eventType)    return {"ok": True}

Use the SDKs to send a test event and confirm delivery in the portal.

Python

from dotenv import load_dotenvfrom diffio import DiffioClientimport osload_dotenv()client = DiffioClient(apiKey=os.getenv("DIFFIO_API_KEY"))result = client.webhooks.send_test_event(    eventType="generation.completed",    mode="live",)print(result.svixMessageId)

When you receive generation.completed, fetch the download URL and queue any heavy work.

Python

from dotenv import load_dotenvfrom diffio import DiffioClientimport osload_dotenv()client = DiffioClient(apiKey=os.getenv("DIFFIO_API_KEY"))def handle_event(event):    if event.eventType != "generation.completed":        return    download = client.generations.get_download(        generationId=event.generationId,        apiProjectId=event.apiProjectId,        downloadType="audio",    )    print("Download URL:", download.downloadUrl)

Respond quickly

Return a 200Success, treated as complete. response fast and push heavy work to a queue or background job.

Webhooks let Diffio notify your system when a generation changes status, so you do not need to poll. This guide walks through opening the portal, adding an endpoint, testing delivery, verifying signatures, and recovering from failures.

Intro

A webhook is a POST request that Diffio sends to a URL you control. Use one endpoint per service, and let that endpoint handle every event type you subscribe to. Respond with a 200Success, treated as complete. response quickly so delivery is marked successful. If your framework enables CSRF protection, disable it for this endpoint.

Each API key maps to its own webhook application, and each endpoint has its own signing secret. Webhook events are scoped to the API key that created the endpoint.

SDK support

The Diffio SDKs expose a webhooks client. In Python use send_test_event. In JavaScript use sendTestEvent. These call POST /v1/webhooks/send_test_event under the hood.

Events and payloads

Diffio emits events only when a generation status changes.

generation.queued when a generation is queued.
generation.processing when processing begins.
generation.failed when processing fails.
generation.completed when processing finishes.

Each webhook payload includes eventType, eventId, createdAt, apiKeyId, apiProjectId, generationId, status, hasVideo, modelKey, error, and errorDetails. The status values are queued, processing, error, and complete.

Sample payload

{  "eventType": "generation.completed",  "eventId": "evt_123",  "createdAt": "2026-01-28T12:34:56Z",  "apiKeyId": "key_123",  "apiProjectId": "proj_123",  "generationId": "gen_123",  "status": "complete",  "hasVideo": false,  "modelKey": "diffio-2",  "error": null,  "errorDetails": null}

Add an endpoint

1
Create an API key
Create an API key before you set up webhooks. Webhook endpoints and events are tied to the API key that creates them. Use the developer dashboard to create your key.
2
Open the webhook portal
You can open the portal from the developer dashboard to configure endpoints.
Open the webhook portal from the developer dashboard and use Add endpoint to get started.
No server yet
If you do not have a webhook receiver, use the portal to generate a temporary test URL. It lets you inspect payloads before you build your own endpoint. If you use a no code tool that gives you a webhook URL, paste that URL into the portal.
3
Add your endpoint URL and events
In the portal, click Add endpoint, paste your URL, then choose the events you want. If you do not select events, your endpoint receives every event type.
Choose the events, add your destination URL, and use Create test link to get a temporary receiver URL.
4
Save the signing secret
After you create the endpoint, copy the signing secret from the endpoint details and store it in your secret manager. You will use it to verify signatures.
After creation, open the endpoint details and copy the signing secret.

Test endpoints

Use the portal Testing tab to send example events, or send a test event from the SDKs. Test events return a message id so you can locate the delivery in the portal.

Python

from diffio import DiffioClientclient = DiffioClient(apiKey="diffio_live_...")result = client.webhooks.send_test_event(    eventType="generation.completed",    mode="live",    samplePayload={"apiProjectId": "proj_123"},)print(result.svixMessageId)

Node.js

import { DiffioClient } from "diffio"const client = new DiffioClient({ apiKey: "diffio_live_..." })const result = await client.webhooks.sendTestEvent({  eventType: "generation.completed",  mode: "live",  samplePayload: { apiProjectId: "proj_123" }})console.log(result.svixMessageId)

cURL

curl https://api.diffio.ai/v1/webhooks/send_test_event \  -H "Authorization: Bearer diffio_live_..." \  -H "Content-Type: application/json" \  -d "{\"eventType\": \"generation.completed\", \"mode\": \"live\"}"

Tip

You can pass samplePayload to override fields like apiProjectId and generationId for testing.

Verify signatures

Signature verification ensures the webhook really came from Diffio. Use the Diffio SDK helpers and always verify against the raw request body, not a parsed JSON object.

Python

from fastapi import FastAPI, Request, HTTPExceptionfrom diffio import DiffioClientimport osapp = FastAPI()client = DiffioClient(apiKey=os.environ["DIFFIO_API_KEY"])@app.post("/webhooks/diffio")async def diffio_webhook(request: Request):    payload = await request.body()    try:        event = client.webhooks.verify_signature(            payload=payload,            headers=request.headers,            secret=os.environ["DIFFIO_WEBHOOK_SECRET"],        )    except Exception:        raise HTTPException(status_code=400, detail="Invalid signature")    print("Webhook received", event.eventType)    return {"ok": True}

Headers required

The verifier expects svix-id, svix-timestamp, and svix-signature headers.

Retries

Diffio retries failed deliveries with exponential backoff. A typical schedule looks like this, starting immediately after the first failure.

Immediately
After 5 seconds
After 5 minutes
After 30 minutes
After 2 hours
After 5 hours
After 10 hours
After 10 more hours

You can also retry messages manually from the portal, or recover all failed messages from a chosen time window.

Troubleshooting and recovery

Troubleshooting tips

Verify the raw payload, not a reserialized JSON string. Changing formatting breaks signature verification.
Confirm the signing secret matches the endpoint you are verifying. Secrets are unique to each endpoint.
Return a 200Success, treated as complete. response for success and any other status for failure. A 200Success, treated as complete. response always marks the delivery successful.
Respond quickly and queue heavy work. Slow responses lead to timeouts and retries.

Failure recovery

If an endpoint is disabled after repeated failures, enable it again in the portal. To replay messages, open the endpoint, choose Options, then Recover failed messages for a time window. You can also resend a single message from its attempt list.

Use this reference to plan Diffio API requests and responses. All endpoints use JSON over HTTPS at https://api.diffio.ai/v1.

API reference essentials

1
Base URL
Use the production base URL for all API requests.
https://api.diffio.ai/v1
Append the endpoint path to the base URL when calling the REST API directly.
2
Authentication
Send the API key on every request using one of the supported headers.
- Authorization: Bearer <apiKey>
- X-Api-Key: <apiKey>
- Xi-Api-Key: <apiKey>
Use API keys with read and write permissions that match the endpoint.
3
Request conventions
- All /v1 endpoints use POST with JSON bodies.
- OPTIONS is accepted for CORS preflight.
- Send Content-Type: application/json for JSON payloads.
- Request fields use camelCase, for example apiProjectId.
- create_project returns uploadUrl and uploadMethod. Use the returned method and set Content-Type to match contentType.
- Download URLs from get_generation_download are signed and expire after about two hours.
4
Error responses
Errors return JSON with an error message. Some errors include additional fields such as code or billing metadata.
Example error response
{ "error": "Payment failed. Update your payment method in the billing portal.", "code": "paymentFailed"}
Billing holds return 402Payment required, billing issue such as paymentFailed. API usage can be blocked until billing is updated. with code paymentFailed. API usage can be blocked until billing is updated. Spend limit errors use spendLimitExceeded.
5
Rate limits
Rate limits and spend limits depend on your plan and API key settings. Review the API pricing page for current limits and use the developer dashboard to monitor usage.

Endpoints

Use these endpoints to create projects, run generations, and send test webhooks.

Projects

Create project

/v1/create_project

Create a project and return a signed upload URL.

List projects

/v1/list_projects

List projects owned by the API key.

Webhooks

Send test event

/v1/webhooks/send_test_event

Send a test webhook event to your configured endpoints.

Create a project and return a signed upload URL for the original media.

POST/v1/create_projectPermissions: write

Endpoint

HTTP request

https://api.diffio.ai/v1/create_project

Use POST with a JSON body.

Permissions

write

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Send metadata for the file you plan to upload.

Body fields

Field	Type	Required	Description
`fileName`	string	Yes	Original file name for the upload.
`contentType`	string	No	MIME type for the upload. Defaults to application/octet-stream.
`contentLength`	number	No	File size in bytes, must be zero or higher.
`fileFormat`	string	No	Short format label. When params.fileFormat is missing, this value is copied into it.
`params`	object	No	Optional parameters stored with the project.
`params.fileFormat`	string	No	Preferred format for downstream processing.

cURL

curl -X POST "https://api.diffio.ai/v1/create_project" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "fileName": "song.wav",    "contentType": "audio/wav",    "contentLength": 1234567,    "fileFormat": "wav",    "params": {      "fileFormat": "wav"    }  }'

Response

Returns the project id and a signed upload URL.

Response fields

Field	Type	Required	Description
`apiProjectId`	string	Yes	Project identifier for subsequent requests.
`uploadUrl`	string	Yes	Signed URL for uploading the original media.
`uploadMethod`	string	Yes	HTTP method to use when uploading the file.
`objectPath`	string	Yes	Storage path for the uploaded file.
`bucket`	string	Yes	Storage bucket that holds the upload.
`expiresAt`	string	Yes	Upload URL expiration timestamp in ISO 8601 format.

Successful response

{  "apiProjectId": "proj-123",  "uploadUrl": "https://storage.googleapis.com/...",  "uploadMethod": "PUT",  "objectPath": "users/user-123/projects/proj-123/original/song.wav",  "bucket": "diffio_api",  "expiresAt": "2025-01-05T12:35:10Z"}

Return codes

200Success, treated as complete.: Project created, upload URL returned.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body, fileName must be provided as a string, contentType must be a string, contentLength must be a number, contentLength must be zero or higher, params must be an object.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
403Forbidden, treated as permission error.: API key is not active, or missing write permission.
405Client error, treated as fix required.: Method is not POST.
500Server error, treated as retryable.: API key missing userId, failed to create upload record, or failed to generate upload URL.

Notes

fileName is required.
contentLength is coerced to an integer, send whole bytes to avoid truncation.
params can be null, it is treated as an empty object.
fileFormat is expected to be a string, when provided and params.fileFormat is missing it is copied as is.
objectPath uses a sanitized basename of fileName, characters outside letters, digits, period, underscore, and hyphen are replaced with underscores, empty names fall back to upload.bin.
Upload the file to uploadUrl using uploadMethod and set Content-Type to match contentType.
uploadUrl expires at expiresAt, request a new URL if it expires.

List projects owned by the API key.

POST/v1/list_projectsPermissions: read

Endpoint

HTTP request

https://api.diffio.ai/v1/list_projects

Use POST with a JSON body.

Permissions

read

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Send a JSON object to list projects for the API key. Additional fields are ignored.

This endpoint expects an empty JSON object.

cURL

curl -X POST "https://api.diffio.ai/v1/list_projects" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{}'

Response

Returns a list of projects owned by the API key.

Response fields

Field	Type	Required	Description
`projects`	array	Yes	List of project objects.
`projects[].apiProjectId`	string	Yes	Project identifier.
`projects[].status`	string	Yes	Current project status.
`projects[].originalFileName`	string	Yes	Original file name from the upload.
`projects[].contentType`	string	Yes	MIME type for the uploaded file.
`projects[].hasVideo`	boolean	Yes	True when the project includes video.
`projects[].generationCount`	number	Yes	Count of generations stored for the project.
`projects[].createdAt`	string	Yes	Creation timestamp in ISO 8601 format.
`projects[].updatedAt`	string	Yes	Last updated timestamp in ISO 8601 format.

Successful response

{  "projects": [    {      "apiProjectId": "proj-123",      "status": "uploaded",      "originalFileName": "song.wav",      "contentType": "audio/wav",      "hasVideo": false,      "generationCount": 2,      "createdAt": "2025-01-05T12:34:56Z",      "updatedAt": "2025-01-05T12:35:10Z"    }  ]}

Return codes

200Success, treated as complete.: Project list returned.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
403Forbidden, treated as permission error.: API key is not active, or missing read permission.
405Client error, treated as fix required.: Method is not POST.
500Server error, treated as retryable.: Failed to load API projects.

Notes

Returns only projects owned by the API key.
Results are sorted by createdAt in descending order, updatedAt is used when createdAt is missing.
generationCount reflects the size of the project generations list.
hasVideo is derived from stored metadata and file type.

Queue a generation for a project using the diffio-2 model.

POST/v1/diffio-2.0-generationPermissions: write

Endpoint

HTTP request

https://api.diffio.ai/v1/diffio-2.0-generation

Use POST with a JSON body.

Permissions

write

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Provide the project id and optional sampling or params overrides.

Body fields

Field	Type	Required	Description
`apiProjectId`	string	Yes	Project identifier returned by create_project.
`sampling`	object	No	Optional sampling overrides.
`sampling.seed`	number	No	Deterministic seed for repeatable generations.
`params`	object	No	Optional model parameters.
`params.prompt`	string	No	Optional prompt text when supported by the model.

cURL

curl -X POST "https://api.diffio.ai/v1/diffio-2.0-generation" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "apiProjectId": "proj-123",    "sampling": {      "seed": 42    },    "params": {      "prompt": "Warm piano"    }  }'

Response

Returns the queued generation record.

Response fields

Field	Type	Required	Description
`generationId`	string	Yes	Generation identifier for progress and downloads.
`apiProjectId`	string	Yes	Project identifier for the generation.
`modelKey`	string	Yes	Model key set to diffio-2.
`status`	string	Yes	Initial status for the generation, usually queued.

Successful response

{  "generationId": "gen-123",  "apiProjectId": "proj-123",  "modelKey": "diffio-2",  "status": "queued"}

Return codes

200Success, treated as complete.: Generation queued and stored.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body, apiProjectId must be provided as a string, sampling must be an object, params must be an object.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
402Payment required, billing issue such as paymentFailed. API usage can be blocked until billing is updated.: Spend limit exceeded for this API key.
403Forbidden, treated as permission error.: API key is not active, missing write permission, or does not own the project.
404Not found, treated as missing resource.: API project not found.
405Client error, treated as fix required.: Method is not POST.
500Server error, treated as retryable.: Pricing is not configured, or failed to create generation record.

Example error response

Error response

{  "error": "Spend limit exceeded for this API key.",  "code": "spendLimitExceeded",  "currency": "USD",  "spendLimitUsd": 10,  "estimatedCostUsd": 1.5,  "usedUsd": 9.2,  "pendingUsd": 0,  "periodStart": "2026-01-15T00:00:00Z",  "periodEnd": "2026-02-15T00:00:00Z"}

Notes

apiProjectId is required.
sampling and params are optional objects. null is treated as an empty object.
sampling and params are passed through without schema validation. Nested fields are not validated.
modelKey is always set to diffio-2.
Use /v1/get_generation_progress to track progress after queuing.

Queue a generation for a project using the diffio-2-flash model.

POST/v1/diffio-2.0-flash-generationPermissions: write

Endpoint

HTTP request

https://api.diffio.ai/v1/diffio-2.0-flash-generation

Use POST with a JSON body.

Permissions

write

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Provide the project id and optional sampling or params overrides.

Body fields

Field	Type	Required	Description
`apiProjectId`	string	Yes	Project identifier returned by create_project.
`sampling`	object	No	Optional sampling overrides.
`sampling.seed`	number	No	Deterministic seed for repeatable generations.
`params`	object	No	Optional model parameters.
`params.prompt`	string	No	Optional prompt text when supported by the model.

cURL

curl -X POST "https://api.diffio.ai/v1/diffio-2.0-flash-generation" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "apiProjectId": "proj-123",    "sampling": {      "seed": 42    },    "params": {      "prompt": "Warm piano"    }  }'

Response

Returns the queued generation record.

Response fields

Field	Type	Required	Description
`generationId`	string	Yes	Generation identifier for progress and downloads.
`apiProjectId`	string	Yes	Project identifier for the generation.
`modelKey`	string	Yes	Model key set to diffio-2-flash.
`status`	string	Yes	Initial status for the generation, usually queued.

Successful response

{  "generationId": "gen-123",  "apiProjectId": "proj-123",  "modelKey": "diffio-2-flash",  "status": "queued"}

Return codes

200Success, treated as complete.: Generation queued and stored.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body, apiProjectId must be provided as a string, sampling must be an object, params must be an object.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
402Payment required, billing issue such as paymentFailed. API usage can be blocked until billing is updated.: Spend limit exceeded for this API key.
403Forbidden, treated as permission error.: API key is not active, missing write permission, or does not own the project.
404Not found, treated as missing resource.: API project not found.
405Client error, treated as fix required.: Method is not POST.
500Server error, treated as retryable.: Pricing is not configured, or failed to create generation record.

Example error response

Error response

{  "error": "Spend limit exceeded for this API key.",  "code": "spendLimitExceeded",  "currency": "USD",  "spendLimitUsd": 10,  "estimatedCostUsd": 1.5,  "usedUsd": 9.2,  "pendingUsd": 0,  "periodStart": "2026-01-15T00:00:00Z",  "periodEnd": "2026-02-15T00:00:00Z"}

Notes

apiProjectId is required.
sampling and params are optional objects. null is treated as an empty object.
sampling and params are passed through without schema validation. Nested fields are not validated.
modelKey is always set to diffio-2-flash.
Use /v1/get_generation_progress to track progress after queuing.

Queue a generation for a project using the diffio-3.4 model.

POST/v1/diffio-3.4-generationPermissions: write

Endpoint

HTTP request

https://api.diffio.ai/v1/diffio-3.4-generation

Use POST with a JSON body.

Permissions

write

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Provide the project id and optional sampling or params overrides.

Body fields

Field	Type	Required	Description
`apiProjectId`	string	Yes	Project identifier returned by create_project.
`sampling`	object	No	Optional sampling overrides.
`sampling.seed`	number	No	Deterministic seed for repeatable generations.
`params`	object	No	Optional model parameters.
`params.prompt`	string	No	Optional prompt text when supported by the model.

cURL

curl -X POST "https://api.diffio.ai/v1/diffio-3.4-generation" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{	    "apiProjectId": "proj-123",	    "sampling": {	      "seed": 42	    },	    "params": {	      "prompt": "Warm piano"	    }	  }'

Response

Returns the queued generation record.

Response fields

Field	Type	Required	Description
`generationId`	string	Yes	Generation identifier for progress and downloads.
`apiProjectId`	string	Yes	Project identifier for the generation.
`modelKey`	string	Yes	Model key set to diffio-3.4.
`status`	string	Yes	Initial status for the generation, usually queued.

Successful response

{	  "generationId": "gen-123",	  "apiProjectId": "proj-123",	  "modelKey": "diffio-3.4",	  "status": "queued"	}

Return codes

200Success, treated as complete.: Generation queued and stored.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body, apiProjectId must be provided as a string, sampling must be an object, params must be an object.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
402Payment required, billing issue such as paymentFailed. API usage can be blocked until billing is updated.: Spend limit exceeded for this API key.
403Forbidden, treated as permission error.: API key is not active, missing write permission, or does not own the project.
404Not found, treated as missing resource.: API project not found.
405Client error, treated as fix required.: Method is not POST.
500Server error, treated as retryable.: Pricing is not configured, or failed to create generation record.

Example error response

Error response

{  "error": "Spend limit exceeded for this API key.",  "code": "spendLimitExceeded",  "currency": "USD",  "spendLimitUsd": 10,  "estimatedCostUsd": 1.5,  "usedUsd": 9.2,  "pendingUsd": 0,  "periodStart": "2026-01-15T00:00:00Z",  "periodEnd": "2026-02-15T00:00:00Z"}

Notes

apiProjectId is required.
sampling and params are optional objects. null is treated as an empty object.
sampling and params are passed through without schema validation. Nested fields are not validated.
modelKey is always set to diffio-3.4.
Use /v1/get_generation_progress to track progress after queuing.

Fetch progress and stage details for a generation.

POST/v1/get_generation_progressPermissions: read

Endpoint

HTTP request

https://api.diffio.ai/v1/get_generation_progress

Use POST with a JSON body.

Permissions

read

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Provide a generation id and optionally the project id.

Body fields

Field	Type	Required	Description
`generationId`	string	Yes	Generation identifier returned by a generation request.
`apiProjectId`	string	No	Optional project id to speed up the lookup.

cURL

curl -X POST "https://api.diffio.ai/v1/get_generation_progress" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "generationId": "gen-123",    "apiProjectId": "proj-123"  }'

Response

Returns the overall status plus stage objects for each job step.

Response fields

Field	Type	Required	Description
`generationId`	string	Yes	Generation identifier for the request.
`apiProjectId`	string	Yes	Project identifier for the generation.
`status`	string	Yes	Overall status for the generation.
`hasVideo`	boolean	Yes	True when the project includes video.
`preProcessing`	object	No	Stage object for preprocessing.
`inference`	object	No	Stage object for inference.
`restoredVideo`	object	No	Stage object for video restoration when present.
`error`	string	No	Error summary when a stage fails.
`errorDetails`	string	No	Detailed error information when available.

Successful response

{  "generationId": "gen-123",  "apiProjectId": "proj-123",  "status": "processing",  "hasVideo": true,  "preProcessing": {    "jobId": "job-pre",    "jobState": "SUCCEEDED",    "status": "complete",    "progress": 100,    "statusMessage": null,    "error": null,    "errorDetails": null  },  "inference": {    "jobId": "job-cloud-run-gpu",    "jobState": "RUNNING",    "status": "running",    "progress": 45,    "statusMessage": "Processing audio",    "error": null,    "errorDetails": null  },  "restoredVideo": {    "jobId": "job-restored",    "jobState": "PENDING",    "status": "pending",    "progress": 0,    "statusMessage": "Queued",    "error": null,    "errorDetails": null  }}

Stage object

{  "jobId": "job-123",  "jobState": "RUNNING",  "status": "running",  "progress": 30,  "statusMessage": "Processing",  "error": null,  "errorDetails": null}

Stage object fields

Stage objects share the same fields across preProcessing, inference, and restoredVideo.

Field	Type	Required	Description
`jobId`	string	No	Job identifier when available.
`jobState`	string	No	Cloud job state, for example RUNNING or SUCCEEDED.
`status`	string	Yes	Stage status, for example pending, running, complete, or failed.
`progress`	number	Yes	Progress percentage from 0 to 100.
`statusMessage`	string	No	Optional status message for the current stage.
`error`	string	No	Error summary when the stage fails.
`errorDetails`	string	No	Detailed error information when available.

Return codes

200Success, treated as complete.: Progress returned.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body, generationId must be provided as a string, apiProjectId must be a string when provided.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
403Forbidden, treated as permission error.: API key is not active, missing read permission, or does not own the project or generation.
404Not found, treated as missing resource.: Generation not found.
405Client error, treated as fix required.: Method is not POST.

Notes

generationId is required and apiProjectId is optional.
Overall status values are pending, processing, complete, failed.
Audio projects return preProcessing and inference only.
Video projects include restoredVideo and complete when all stages are complete.
When a stage fails, the top level status is failed and error fields are populated.
preProcessing reports complete when audioOriginalMp3Ready is true even if the job document is missing.
When a stage is missing, it reports pending with progress set to 0.

Return a signed download URL for restored audio or video.

POST/v1/get_generation_downloadPermissions: read

Endpoint

HTTP request

https://api.diffio.ai/v1/get_generation_download

Use POST with a JSON body.

Permissions

read

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Provide the project id, generation id, and optional download type.

Body fields

Field	Type	Required	Description
`generationId`	string	Yes	Generation identifier returned by a generation request.
`apiProjectId`	string	Yes	Project identifier for the generation.
`downloadType`	string	No	audio or video. Defaults to video for video projects, otherwise audio.

cURL

curl -X POST "https://api.diffio.ai/v1/get_generation_download" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "generationId": "gen-123",    "apiProjectId": "proj-123",    "downloadType": "audio"  }'

Response

Returns a signed download URL and file metadata.

Response fields

Field	Type	Required	Description
`generationId`	string	Yes	Generation identifier for the request.
`apiProjectId`	string	Yes	Project identifier for the generation.
`downloadType`	string	Yes	audio or video based on the request and project type.
`downloadUrl`	string	Yes	Signed URL for downloading the restored file.
`fileName`	string	Yes	File name for the restored asset.
`storagePath`	string	Yes	Storage path for the restored file.
`bucket`	string	Yes	Storage bucket that holds the restored file.
`mimeType`	string	Yes	MIME type of the restored file.

Successful response

{  "generationId": "gen-123",  "apiProjectId": "proj-123",  "downloadType": "audio",  "downloadUrl": "https://storage.googleapis.com/...",  "fileName": "diffio_ai_upload.wav",  "storagePath": "users/user-123/projects/proj-123/generations/gen-123/restored.mp3",  "bucket": "diffio_api",  "mimeType": "audio/mpeg"}

Return codes

200Success, treated as complete.: Download URL returned.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body, generationId and apiProjectId must be strings, downloadType must be a string, downloadType must be audio or video, video downloads are only available for video projects.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
403Forbidden, treated as permission error.: API key is not active, missing read permission, not permitted to download generations, or does not own the project or generation.
404Not found, treated as missing resource.: Generation not found, restored audio path is not available, restored audio file not found, restored video path is not available.
405Client error, treated as fix required.: Method is not POST.
409Conflict, treated as not ready yet.: Generation is not ready yet because processing is not complete or the generation is not marked complete, restored video is not ready yet because the restored job has not succeeded or the blob does not exist.

Notes

downloadType defaults to video for video projects, otherwise audio.
downloadUrl expires after about two hours, request a new one if it expires.
Audio downloads require the generation to be complete and the restored audio file to exist.
Video downloads require a video project, the generation to be complete, and the restored video job to be complete.
API keys must have read permission and downloadGenerations must be true when present.

List generations for a project.

POST/v1/list_project_generationsPermissions: read

Endpoint

HTTP request

https://api.diffio.ai/v1/list_project_generations

Use POST with a JSON body.

Permissions

read

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Provide the project id to list its generations.

Body fields

Field	Type	Required	Description
`apiProjectId`	string	Yes	Project identifier returned by create_project.

cURL

curl -X POST "https://api.diffio.ai/v1/list_project_generations" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "apiProjectId": "proj-123"  }'

Response

Returns a list of generations for the project.

Response fields

Field	Type	Required	Description
`apiProjectId`	string	Yes	Project identifier for the request.
`generations`	array	Yes	List of generation objects.
`generations[].generationId`	string	Yes	Generation identifier.
`generations[].status`	string	Yes	Current generation status.
`generations[].modelKey`	string	Yes	Model key used for the generation.
`generations[].progress`	number	No	Progress percentage when available.
`generations[].createdAt`	string	Yes	Creation timestamp in ISO 8601 format.
`generations[].updatedAt`	string	Yes	Last updated timestamp in ISO 8601 format.

Successful response

{  "apiProjectId": "proj-123",  "generations": [    {      "generationId": "gen-123",      "status": "processing",      "modelKey": "diffio-2",      "progress": 45,      "createdAt": "2025-01-05T12:40:00Z",      "updatedAt": "2025-01-05T12:41:00Z"    }  ]}

Return codes

200Success, treated as complete.: Generation list returned.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body, apiProjectId must be provided as a string.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
403Forbidden, treated as permission error.: API key is not active, missing read permission, or does not own the project.
404Not found, treated as missing resource.: API project not found.
405Client error, treated as fix required.: Method is not POST.
500Server error, treated as retryable.: Failed to load generations.

Notes

apiProjectId is required.
Returns only generations owned by the API key.
Results are sorted by createdAt in descending order, updatedAt is used when createdAt is missing.
progress can be null when the generation has not reported progress.

Send a test webhook event to all endpoints configured for the API key.

POST/v1/webhooks/send_test_eventPermissions: read

Endpoint

HTTP request

https://api.diffio.ai/v1/webhooks/send_test_event

Use POST with a JSON body.

Permissions

read

API keys must be active.

Authentication

Send the API key on every request using one of the supported headers.

Authorization: Bearer <apiKey>
X-Api-Key: <apiKey>
Xi-Api-Key: <apiKey>

Request

Provide the event type and mode for the test webhook.

Body fields

Field	Type	Required	Description
`eventType`	string	Yes	Webhook event type to send.
`mode`	string	Yes	Webhook mode, either test or live.
`apiKeyId`	string	No	Optional API key id to assert; must match the authenticated key.
`samplePayload`	object	No	Optional fields to merge into the generated test payload.
`samplePayload.apiProjectId`	string	No	Optional project id override for the test payload.

cURL

curl -X POST "https://api.diffio.ai/v1/webhooks/send_test_event" \  -H "Authorization: Bearer $DIFFIO_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "eventType": "generation.completed",    "mode": "live"  }'

Response

Returns the message id and metadata for the test webhook.

Response fields

Field	Type	Required	Description
`svixMessageId`	string	Yes	Message id assigned by Svix.
`eventId`	string	Yes	Event id generated for the test event.
`eventType`	string	Yes	Event type that was sent.
`mode`	string	Yes	Webhook mode used for delivery.

Successful response

{  "svixMessageId": "msg_123",  "eventId": "evt_123",  "eventType": "generation.completed",  "mode": "live"}

Return codes

200Success, treated as complete.: Test webhook sent.
204Success, treated as empty response.: CORS preflight when method is OPTIONS.
400Bad request, treated as client error.: Invalid JSON body, eventType is required, eventType is not supported, mode must be test or live, samplePayload must be an object.
401Unauthorized, treated as auth error.: Missing API key, or invalid API key.
403Forbidden, treated as permission error.: API key is not active, missing read permission, or does not match apiKeyId.
405Client error, treated as fix required.: Method is not POST.
500Server error, treated as retryable.: Svix is not configured, failed to initialize webhook app, or failed to send test webhook.

Notes

eventType must be one of generation.queued, generation.processing, generation.failed, or generation.completed.
mode controls whether the test event is delivered to test or live endpoints.
samplePayload can override payload fields, but eventType, eventId, createdAt, apiKeyId, and status are always set by Diffio.

Endpoint

HTTP request

Permissions

Authentication

Request

Body fields

Response

Response fields

Return codes

Notes

Documentation

Developers

API reference

Models

Diffio 2.0 Flash

Diffio 2.0

Diffio 3.4

Browse by capability

Audio restoration

Video support

Model lineup

Diffio 2.0 Flash

Diffio 2.0

Diffio 3.4

Choosing a model

Endpoint mapping

Next steps

Quickstart

Full API guide

API reference

Template notes

Summary

Examples

Next steps

Template notes

Summary

Examples

Next steps

Upgrading to the Developer tier

What happens when I upgrade to the Developer tier?

What are the benefits of upgrading?

Can I downgrade back to the Free tier after I upgrade?

Understanding the Diffio billing model

How does the billing cycle work?

How does progressive billing work?

Special billing for customers in India

What if I do not reach the next threshold?

When is payment withdrawn from my account?

Monitoring your spending and usage

How can I view my current usage and spending in near real time?

Can I set spending limits or receive budget alerts?

Invoices, billing info, and credits

Where can I find my past invoices and payment history?

Can I change my billing info and payment method?

What payment methods do you accept?

Are there promotional credits or trial offers?

Common billing questions and troubleshooting

How are refunds handled, if applicable?

What if I believe there is an error in my bill?

Under what conditions can my account be suspended due to billing issues?

What happens if my payment fails?

What should I do if my billing question is not answered here?

Prerequisites

Workflow overview

Using the Diffio SDK

Create an API key

Install the SDK

Create a project

Run multiple generations

Download each result

Prerequisites

Workflow overview

Using the Diffio SDK

Create an API key

Install the SDK

Configure the client

Create a project

Create a generation

Wait for completion

Download results