Embedded Editor
Mount a configurable JavaScript editor inside your application. Control layout, enabled tools, asset sources, project behavior and visual theme.
Embed the guided workflow for your users or orchestrate recommendations and generation from your backend. Two integration paths, one platform.
Start with one integration path and add the other later. Authentication and credit usage remain part of the same Voxify account model.
Mount a configurable JavaScript editor inside your application. Control layout, enabled tools, asset sources, project behavior and visual theme.
Call recommendation, formatting, voice-over, mixing and complete audio-ad generation workflows from your own services.
Use automation for the standard path and open projects in Studio when a producer needs deeper script, timeline, mix or delivery control.
The editor mounts into your page and uses authentication callbacks supplied by your application. Your backend remains responsible for obtaining and refreshing end-user access tokens.
window.VoxifyStudioEditor.create({
target: '#voxify-editor',
auth: {
getToken: async (userId) => {
const response = await fetch(
'/api/voxify/token',
{ method: 'POST' }
);
return (await response.json())
.accessToken.token;
},
refreshToken: async (expired) => {
// refresh through your backend
}
},
layout: { height: '600px' }
});
Use individual endpoints for a vocal, format or mix, or start with a higher-level recommendation and generate a complete audio ad from the chosen composition.
curl -X POST \ https://api.voxify.studio/v1/recommend/url \ -H "x-api-key: $VOXIFY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "project_id": "campaign-summer-01", "url": "https://brand.example/offer", "duration": 30, "max_recommendations": 3 }' # 202 Accepted → poll the returned poll_url # or provide webhook configuration in the request
The API surfaces operational identifiers, usage information and asset metadata so your application can follow work across asynchronous steps.
Use an account API key for server-to-server calls or obtain a short-lived access token for an embedded end-user session.
Send a stable project identifier so recommendations, generated assets and follow-up operations can share the same context.
Compose individual voice-over and mixing calls, or use the higher-level URL and product recommendation jobs followed by complete audio-ad generation.
For asynchronous work, poll the job status URL or receive terminal completion through the configured webhook endpoint.
Receive generated asset metadata together with exact voice and music details where the workflow supports them, plus standard usage and billing information.
Load the bundle, mount the editor, connect authentication and validate the first session.
Understand project, vocal, music, mastering, tools, layout and theme configuration.
Review exact schemas, required fields, status codes and endpoint-specific examples in ReDoc.
Start with the SDK documentation, inspect the API contracts or talk to us about the right integration boundary.