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

Higgsfield API

Asynchronous generative-media API. Submit a generation request to any of the 100+ model endpoints (POST /{model_id}), then retrieve status (GET /requests/{request_id}/status), cancel a queued request (POST /requests/{request_id}/cancel), or receive a webhook when the request reaches a final status (completed, failed, nsfw). Authenticated with an API key + secret via the "Authorization: Key {key}:{secret}" scheme.

This API exposes 50 operations across 50 paths, and defines 1 schema. It is described by OpenAPI .

Requests are made against a single base URL, https://platform.higgsfield.ai.

50 operations 50 paths 1 schemas 1 GET49 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI
Base URL
https://platform.higgsfield.ai
Resource Areas
1

Paths & Operations 50

Across 50 paths, the API surfaces 50 operations — 1 GET, 49 POST. Each is listed below with its method, path, parameters, and response codes.

Operations 50
GET
/requests/{request_id}/status
Get Generation Status
get_request_status 1 param → 200
POST
/requests/{request_id}/cancel
Get Generation Status
get_request_status 1 param → 202
POST
/higgsfield-ai/dop/turbo
body → 200
POST
/higgsfield-ai/dop/lite
body → 200
POST
/higgsfield-ai/dop/standard
body → 200
POST
/higgsfield-ai/popcorn/auto
body → 200
POST
/higgsfield-ai/soul/character
body → 200
POST
/higgsfield-ai/soul/reference
body → 200
POST
/higgsfield-ai/soul/standard
body → 200
POST
/veo3.1
body → 200
POST
/veo3.1/image-to-video
body → 200
POST
/veo3.1/first-last-frame-to-video
body → 200
POST
/veo3.1/fast/image-to-video
body → 200
POST
/veo3.1/fast
body → 200
POST
/veo3.1/fast/first-last-frame-to-video
body → 200
POST
/veo3.1/reference-to-video
body → 200
POST
/bytedance/seedance/v1/lite/image-to-video
body → 200
POST
/bytedance/seedance/v1/lite/text-to-video
body → 200
POST
/bytedance/seedance/v1/pro/fast/image-to-video
body → 200
POST
/bytedance/seedance/v1/pro/fast/text-to-video
body → 200
POST
/flux-pro/kontext/max/text-to-image
body → 200
POST
/kling-video/v2.1/master/image-to-video
body → 200
POST
/kling-video/v2.1/master/text-to-video
body → 200
POST
/kling-video/v2.1/pro/image-to-video
body → 200
POST
/kling-video/v2.1/standard/image-to-video
body → 200
POST
/kling-video/v2.5-turbo/pro/image-to-video
body → 200
POST
/kling-video/v2.5-turbo/pro/text-to-video
body → 200
POST
/kling-video/v2.5-turbo/standard/image-to-video
body → 200
POST
/minimax/hailuo-02/pro/image-to-video
body → 200
POST
/minimax/hailuo-02/pro/text-to-video
body → 200
POST
/minimax/hailuo-02/standard/image-to-video
body → 200
POST
/minimax/hailuo-02/standard/text-to-video
body → 200
POST
/minimax/hailuo-2.3-fast/pro/image-to-video
body → 200
POST
/minimax/hailuo-2.3-fast/standard/image-to-video
body → 200
POST
/minimax/hailuo-2.3/pro/image-to-video
body → 200
POST
/minimax/hailuo-2.3/pro/text-to-video
body → 200
POST
/minimax/hailuo-2.3/standard/image-to-video
body → 200
POST
/minimax/hailuo-2.3/standard/text-to-video
body → 200
POST
/nano-banana
body → 200
POST
/reve/edit
body → 200
POST
/reve/fast/edit
body → 200
POST
/reve/fast/remix
body → 200
POST
/reve/remix
body → 200
POST
/reve/text-to-image
body → 200
POST
/sora-2/image-to-video
body → 200
POST
/sora-2/image-to-video/pro
body → 200
POST
/sora-2/text-to-video
body → 200
POST
/sora-2/text-to-video/pro
body → 200
POST
/wan-25-preview/image-to-video
body → 200
POST
/wan-25-preview/text-to-video
body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is RequestStatus (4 properties). Each schema is shown below with its type and property counts.

RequestStatus
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

higgsfield-openapi-original.json Raw ↑
Where this information came from

This is an independent, third-party profile of Higgsfield 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.