Purpose
The Percify API lets you programmatically generate images, transform them into videos, synthesize voice audio, and retrieve published media assets. All endpoints follow predictable credit-based metering.Base URL
Authentication
Use an API key in theAuthorization header:
Common Endpoints
| Action | Method | Path |
|---|---|---|
| Generate Image | POST | /images/generate |
| Video From Image | POST | /videos/from-image |
| Clone Voice | POST | /voices/clone |
| Generate Audio | POST | /audio/generate |
| Avatar Metadata | GET | /avatars/ |
| Credit Balance | GET | /credits/balance |
Response Pattern
Successful async generation requests return a processing object:status becomes completed.
Errors
| Status | Meaning | Typical Cause |
|---|---|---|
| 400 | Bad request | Missing required field / invalid duration |
| 401 | Unauthorized | Missing or bad API key |
| 403 | Forbidden | Banned user or restricted asset |
| 404 | Not found | Invalid resource id |
| 429 | Rate limited | Too many requests in window |
| 500 | Server error | Internal failure; retry later |
Idempotency (Recommended)
For operations that could be retried (e.g., payment intent creation), include anIdempotency-Key header. Future endpoints may enforce uniqueness for safety.
Webhooks (Planned)
Upcoming event types:avatar.generatedvideo.completedaudio.completedcredits.updated
OpenAPI Specification
The full schema resides inapi-reference/openapi.json. Use it to generate client SDKs or validate requests.
Next Steps
- Review authentication details at [/percify/api-auth]
- Explore endpoint examples in the API Reference tab
- Learn credit cost formulas at [/percify/credits]
Need a new endpoint? Request via support with use case details.