REST API
API quickstart
Create a key, inspect a model, submit an asynchronous media job, and receive your first result using the MakeInfluencer REST API.
Base URL
https://www.makeinfluencer.ai/api/v1/models/{modelId}/generationsAll REST endpoints start with https://www.makeinfluencer.ai/api/v1. Requests and responses use JSON except the raw file upload described in the asset guide.
REST and MCP are separate integration surfaces
1. Create an API key
Open Developer API → Keys, create a named key, and copy the secret immediately. Only its hash is stored, so the full key cannot be shown again.
Authorization: Bearer mi_YOUR_API_KEY2. Choose a model
Every model has a live contract with its input fields, defaults, limits, capabilities, and representative credit quote. Start in the model directory or requestGET /models.
3. Create a generation
Send the selected model's fields inside input. Include a unique idempotency key whenever your client might retry the request. A successful submission returns HTTP 202 and one or more owned generation IDs.
curl --request POST \
https://www.makeinfluencer.ai/api/v1/models/happyhorse1/generations \
--header "Authorization: Bearer $MAKEINFLUENCER_API_KEY" \
--header "Idempotency-Key: first-video-001" \
--header "Content-Type: application/json" \
--data '{
"input": {
"prompt": "A fashion creator walking through neon Tokyo",
"aspectRatio": "9:16",
"duration": 5,
"resolution": "720p"
}
}'Preview the exact charge first
POST /models/{modelId}/preview-credits. Preview requests validate the model input and do not spend credits.4. Poll the result
Save the first returned ID and poll the matching image or video status endpoint. Stop when terminal is true. A successful result also hasready: true.
curl https://www.makeinfluencer.ai/api/v1/generations/video/GENERATION_ID \
--header "Authorization: Bearer $MAKEINFLUENCER_API_KEY"{
"id": "GENERATION_ID",
"status": "success",
"ready": true,
"terminal": true,
"refunded": false,
"url": "https://assets.makeinfluencer.ai/…/video.mp4",
"creditsCost": 35088
}Credits and billing
REST, MCP, and dashboard generations use the same account balance at the same model price. There is no second API subscription. CheckGET /account for the current balance and top-up URL.
Failed dispatches are refunded