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.
Diffio 2.0
diffio-2
Balanced
Fast, reliable cleanup for everyday restoration.
Best for: General restoration, quick turnaround, high volume work.
Fastest turnaround in the product lineup.
Reliable cleanup for interviews and podcasts.
Best fit for high volume production queues.
Diffio 3.5
diffio-3.5
Best
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 for rapid previews or high volume queues.
diffio-2 for balanced speed and clarity when throughput matters.
diffio-3.5 for the highest clarity on noisy or distant speech.
Plan access
Diffio 2.0 and Diffio 3.5 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.
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?
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.
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", )
Node.js
import fs from "node:fs"for (const item of generations) { let status = "queued" while (!["complete", "failed"].includes(status)) { const progress = await client.generations.getProgress({ generationId: item.generation.generationId, apiProjectId: project.apiProjectId, }) status = progress.status console.log(item.model, "status:", status) if (!["complete", "failed"].includes(status)) { await new Promise((resolve) => setTimeout(resolve, 5000)) } } if (status !== "complete") { throw new Error(`Generation failed for ${item.model}`) } const download = await client.generations.getDownload({ generationId: item.generation.generationId, apiProjectId: project.apiProjectId, downloadType: "audio", }) const audioResponse = await fetch(download.downloadUrl) const audioBuffer = Buffer.from(await audioResponse.arrayBuffer()) const outputName = `restored-${item.model}.mp3` fs.writeFileSync(outputName, 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.
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.
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.
1
List projects
Python
projects = client.projects.list()for project in projects.projects: print(project.apiProjectId, project.status, project.originalFileName)
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.
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.
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.
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.
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.
