How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Creatify AI Avatar API

Lipsync v1/v2 and Aurora avatar video generation.

Creatify AI Avatar API is one of 10 APIs that Creatify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include AI Avatar. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 6 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.creatify.ai/api.

6 operations 6 paths 2 schemas 2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.creatify.ai/api
Authentication
API Key, API Key
Contact
Resource Areas
1

Authentication & Security 2

Creatify AI Avatar API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-API-ID (apiId). An API key is passed in the header as X-API-KEY (apiKey). By default, every request must be authenticated.

  • apiId — Your unique Creatify API identifier from the in-app API Dashboard.
  • apiKey — Your secret Creatify API key. Keep it server-side.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

AI Avatar 6

Lipsync v1/v2 and Aurora avatar video generation.

POST
/lipsyncs/
Create an AI avatar video (Lipsync v1)
createLipsync body → 200401
POST
/lipsyncs/preview/
Preview an AI avatar video (Lipsync v1)
previewLipsync body → 200401
GET
/lipsyncs/{id}/
Get an AI avatar video (Lipsync v1)
getLipsync 1 param → 200401404
POST
/lipsyncs/{id}/render/
Render an AI avatar video (Lipsync v1)
renderLipsync 1 param → 200401404
POST
/lipsyncs_v2/
Create a multi-scene AI avatar video (Lipsync v2)
createLipsyncV2 body → 200401
GET
/lipsyncs_v2/{id}/
Get a multi-scene AI avatar video (Lipsync v2)
getLipsyncV2 1 param → 200401404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are VideoJob (12 properties), Error (2 properties). Each schema is shown below with its type and property counts.

VideoJob
object
A generic asynchronous video-generation job.
12 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

creatify-ai-avatar-api-openapi.yml Raw ↑

Other APIs Creatify publishes across the network.

Creatify AI Editing API
Creatify AI Shorts API
Creatify Custom Templates API
Creatify Link-to-Video API
Creatify Music API
Creatify Personas API
Creatify Product-to-Video API
Creatify Text-to-Speech API
Creatify Voices API
Where this information came from

This is an independent, third-party profile of Creatify AI Avatar API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.