White-label API for AI content generation
Resell AI content generation as your own service. Agencies and SaaS platforms call the white-label API from their own backend, with one workspace and one key per customer. Responses carry zero supapost branding, so your domain, your pricing, and your support own the relationship end to end.
This page covers what a white-label content API is, how per-tenant integration works, what your customers see, and how to bill them for usage.
What is a white-label API?
A white-label API is a service you resell under your own brand. Your product calls the provider's endpoints and receives plain data back, with no provider branding attached. Your customers see only your interface, your domain, and your pricing, while the provider runs the models and infrastructure behind it.
supapost is a white-label content API in exactly that sense. Responses are JSON containing the generated post, its variations, and hashtag suggestions. Nothing in the payload names supapost, so an agency can sell content generation as a service and a SaaS platform can ship an AI writing feature without disclosing the engine behind it.
How does white-label API integration work?
Your backend stores one API key per customer and calls the endpoint on their behalf. Each key is bound to a workspace holding that customer's brand voice, so requests stay isolated and usage is metered per tenant. Responses return as JSON your own interface renders. Integration is a single POST call.
Per-tenant isolation
One workspace per customer. Brand voice, assets, and usage counters never cross between tenants.
Server-side keys
Keys stay on your backend. Customers call your endpoint; your endpoint calls ours.
Usage you can bill
Per-workspace counters via /api/v1/usage map one-to-one to a customer invoice.
How white-labeling works
Create workspaces for your customers
Each of your customers gets their own workspace with dedicated brand voice, content settings, and API keys. Onboard them in seconds with URL-based brand detection.
Call the API from your product
Your frontend or backend calls our REST API with the customer's workspace API key. We return engaging, platform-ready content as JSON. You render it however you want.
Track usage, bill your way
Query per-workspace usage via the API. Know exactly how many posts each customer generated. Build your own pricing model on top of our infrastructure.
Why teams white-label supapost
Zero supapost branding
Your users never see our name. The API returns raw content, and you control the entire UX and presentation.
Per-client API keys
Create separate workspaces and API keys for each of your customers. Usage is tracked per workspace for billing.
Brand context per tenant
Each workspace has its own brand voice, industry, audience, and content pillars. Your customers' content sounds like them, not a template.
Simple REST integration
One POST request to generate content. Bearer auth, JSON responses, rate limit headers. Integrate in an afternoon.
Trained on top performers
Our AI is optimized for engagement: posts that get actual clicks and views, not generic filler content.
Multi-platform output
Generate for X, LinkedIn, Instagram, and Facebook, each formatted for the target platform's rules and audience.
Integration is one API call
Your product calls our API with your customer's workspace key. We return engaging content. You display it.
// Your backend generates a post for your customer
const response = await fetch('https://supapost.ai/api/v1/content/generate', {
method: 'POST',
headers: {
'Authorization': 'Bearer ' + customer.supapostApiKey,
'Content-Type': 'application/json',
},
body: JSON.stringify({
type: 'social',
platform: 'linkedin',
topic: customer.selectedTopic,
}),
});
const { content, variations, hashtags } = await response.json();
// Display in YOUR UI - no supapost branding anywhereWhite-label API questions
What is a white-label API?
A white-label API is a service you resell under your own brand. Your product calls the provider's endpoints, and the responses carry no provider branding, so your customers see only your interface, your domain, and your pricing. You own the relationship; the provider runs the infrastructure.
How does white-label API integration work?
Your backend holds one API key per customer and calls the endpoint on their behalf. Requests carry that customer's workspace key, responses come back as plain JSON, and your application renders them however it wants. Typical integration is a single POST call and takes an afternoon.
Can my users see supapost branding?
No. The API returns raw content as JSON. There's no supapost branding in API responses. You control the entire user experience.
How do I bill my customers for usage?
Each workspace tracks usage separately (posts generated, API requests, images). Use the /api/v1/usage endpoint to query per-workspace metrics and build your own billing on top.
Can each of my customers have their own brand voice?
Yes. Each workspace has independent brand settings: voice, tone, industry, audience, content pillars, and custom instructions. Brand detection from URL also works per workspace.
What's the API rate limit for white-label?
Agency plan includes 2,000 API requests/day with up to 10 workspaces. For higher volume, contact us for custom enterprise pricing.
White-label versus reselling versus an integration: what is the difference?
Reselling passes a branded third-party product to your customer. An integration shows the provider's name inside your product. White-labeling hides the provider entirely: your customers never learn who generates the content, and switching providers later requires no change on their side.
Who owns the content generated through the API?
You and your customers do. Generated content is yours to publish, modify, or resell with no attribution requirement. supapost claims no ownership over API output and does not use your customers' generated content to train models.
Can I run the white-label API on my own domain?
Yes, by proxying. Your backend exposes an endpoint on your domain, calls supapost server-side, and returns the result. Customers only ever see your host. Keep the key server-side: a browser calling supapost directly would expose it and leak the provider.
Ready to white-label?
Agency plan: 10 workspaces, 2,000 API req/day. Start free to test.