API Reference
REST API v1Integrate Wubble's AI audio generation into your applications with our comprehensive REST API
Overview
The Wubble API provides programmatic access to AI audio generation capabilities. Generate music, speech, and sound effects through simple HTTP requests, then track request status, usage, and webhook deliveries from the same developer surface.
Built for developers, our RESTful API is designed with simplicity, reliability, and performance in mind. Whether you're building a content creation platform, a game audio system, or an automated video production pipeline, Wubble API scales with your needs.
What You Can Build
https://prod-backup-backend.wubble.ai/v1Key Features
Music Generation
Generate original music from text descriptions. Control style, mood, tempo, and instrumentation with natural language.
Voice Generation
Generate natural-sounding speech from text. Choose from voices or clone custom voices for your brand.
Sound Effects
Generate custom sound effects for games, videos, and interactive experiences from simple descriptions.
Usage & Webhooks
Inspect request usage, monitor limits, and react to completed jobs with webhook events and dashboard telemetry.
Quick Start
Get started with the Wubble API in three simple steps:
Get Your API Key
Generate an API key from your API Keys dashboard. Keep it secure and never commit it to version control.
Make your first API call
Use standard HTTP clients directly against /v1 endpoints (for example fetch, requests, or curl).
/v1/creditsconst API_BASE_URL = "https://prod-backup-backend.wubble.ai";
const API_KEY = process.env.WUBBLE_API_KEY ?? "wbk_your_api_key";
const response = await fetch(`${API_BASE_URL}/v1/credits`, {
headers: { Authorization: `Bearer ${API_KEY}` },
});
if (!response.ok) throw new Error(`HTTP ${response.status}`);
const { success, data, error } = await response.json();
if (!success) throw new Error(error?.message ?? "Request failed");
console.log("API calls remaining:", data.api_calls_remaining);Try more endpoints
Use the API playground for a quick glance at core calls, then jump into the endpoint reference for full route coverage.
Using cURL
You can also interact with the API directly using cURL or any HTTP client:
# Check API call allowance (GET) — swap in your real API key
curl -s https://prod-backup-backend.wubble.ai/v1/credits \
-H "Authorization: Bearer YOUR_API_KEY"API Principles
The Wubble API is designed with the following principles to ensure a great developer experience:
RESTful Design
Predictable route families with standard HTTP methods such as GET, POST, and DELETE
JSON First, Multipart Where Needed
Most routes use JSON, with multipart uploads for speech files and music source uploads
Secure by Default
HTTPS only, API key authentication, and comprehensive security best practices
Fast and Reliable
Async request polling, webhook delivery, and CDN-backed output URLs for completed artifacts
Comprehensive Monitoring
Real-time usage analytics, detailed error messages, and debugging tools
Versioned
API versioning ensures backward compatibility and smooth upgrades
Pricing and usage at a glance
- Free: 5 API calls
- Basic: 10 API calls
- Business: 50 API calls
- API Starter: SGD 29 / month for 150 calls
- API Business: SGD 99 / month for 700 calls
- Each billable generation request consumes 1 API call
Error Handling
The API uses standard HTTP status codes and returns detailed error messages in JSON format to help you debug issues quickly:
{
"error": {
"code": "invalid_request",
"message": "The 'prompt' parameter is required",
"details": {
"param": "prompt",
"type": "missing_required_field"
}
}
}Common Status Codes
| Status Code | Meaning | When to Expect |
|---|---|---|
200 OK | Request successful | Normal operation |
201 Created | Resource created | POST requests |
400 Bad Request | Invalid parameters | Validation errors |
401 Unauthorized | Invalid API key | Authentication failure |
403 Forbidden | Insufficient permissions | Quota exceeded or scope limited |
429 Too Many Requests | Rate limit exceeded | Too many requests |
500 Internal Server Error | Server error | Something went wrong on our end |
Next Steps
Explore the documentation to learn more about authentication, endpoints, and best practices:
Authentication
API keys, Bearer tokens, and security best practices
Rate Limits
Understand rate limits, quotas, and optimization strategies
API keys
Create keys, set scopes, and secure integrations
Playground
Try real /v1 calls with a selected key from the dashboard
Platform endpoints
Health, request status, webhooks, and API key management
Async jobs
Handle 202 responses, request IDs, and polling correctly
Webhooks
Receive signed completion events instead of polling
Billing & usage
Understand API call allowance, usage logs, and 402 behavior
Errors
Map status codes, retry behavior, and failure envelopes
Need Help?
If you have questions about the API, reach out to our developer support team at support@wubble.ai or join our developer community on Discord.