Access

Higgsfield developer access

Create one Higgsfield API key. Keep it on the server.

Copy the full credential when it is created. Send it only from your backend with the Key authorization scheme. Keep each request ID tied to the user who started the job.

Server requestREST
curl -X POST https://api.higgsfield.ai/bytedance/seedance-2.0/text-to-video \
  -H "Authorization: Key ${HF_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"A cinematic tracking shot along a sunlit coastal road","resolution":"720p","generate_audio":true,"duration":5,"aspect_ratio":"16:9"}'

Authorization: Key ${HF_API_KEY}

Four setup steps

Make the first request without exposing the key.

The API console, REST host, and website studio are different surfaces. Create the key in the console. Use it against api.higgsfield.ai from the server.

  1. 01

    Create

    Open the API console, fund the separate balance, and create a key.

  2. 02

    Copy

    Save the complete credential when it appears. The full value is shown once.

  3. 03

    Store

    Put it in a server-only secret such as HF_API_KEY.

  4. 04

    Send

    Use the Key authorization scheme and save the returned request ID.

The full key is shown onceA lost key must be replaced with a new one.
20 concurrent requestsHiggsfield says creating a key unlocks this starting limit.

Do not mix the paths

API key and MCP login solve different jobs.

CheckDeveloper APIMCP
API keyRequiredNot used
BillingPrepaid US dollarsWebsite plan credits
Best forBuilding a productGenerating from an agent
ConnectionREST or SDKAccount sign-in

Five key answers

Create, send, replace, and fund the key.

How do I get a Higgsfield API key?

Create an API account, add a payment method and funds, then generate a key in the Open Higgsfield console. The full key appears only once, so copy it when it is created.

Open the API console

Sign up for an API account at Open Higgsfield. Add a payment method and fund the separate US dollar API balance.

Create and copy the key

Generate a key on the API Keys page. The full credential appears only at creation, so save it before closing the view.

Store it on the server

Put the complete value in a server-only environment variable such as HF_API_KEY. Do not place it in client code, localStorage, logs, or a committed file.

What header does the Higgsfield API key use?

Direct REST requests use Authorization: Key followed by the complete copied API key. The value itself should not contain another added Key prefix.

Build the header

Set Authorization to Key, one space, and the complete copied credential. A server environment variable keeps the value out of browser code.

Use the current API host

Send REST generation requests to api.higgsfield.ai. The older platform.higgsfield.ai endpoint has been deprecated.

Keep model fields exact

Open the selected model's documentation and use its current endpoint and input schema. Different models can require different fields and limits.

Can I see my Higgsfield API key again?

No. Higgsfield says the full API key is visible only at creation. If it is lost, generate a new key and update the server credential used by the integration.

Treat the first view as the save step

Copy the complete credential when the console creates it. A later console visit will not reveal the full value again.

Replace a lost key

Create a new key, place it in the server secret store, deploy the change, and verify a request with the replacement.

Retire the old credential

After the new key works everywhere, remove the lost or old key from active use so only the replacement can authenticate requests.

Does Higgsfield MCP need an API key?

No. Higgsfield MCP uses account sign-in and plan credits. The developer API is a separate product that uses an API key and a prepaid US dollar balance.

Use MCP for an agent connection

A supported agent connects to Higgsfield and signs into the website account. The connector does not ask for an API key.

Use the API for a product

An app that sends direct REST or SDK requests uses the separate developer API key and API balance.

Do not mix the two balances

MCP work uses plan credits. API work uses the separate prepaid dollar balance, so one does not fund the other.

Do I need a Higgsfield subscription to use the API?

No. Higgsfield says the API works without a website subscription. It uses its own API account, key, and prepaid US dollar balance.

Keep the products separate

The website subscription is for the visual studio and plan features. The API is for code and can be used on its own.

Fund the API balance

Add at least $5 to the separate prepaid balance. New requests wait when that balance reaches zero.

Estimate before generation

Use the estimate endpoint for the selected model and settings before starting a paid job. Successful jobs are charged and failed jobs are refunded.

One video key and one job shape

Compare the narrower Cre8vid access path.

Get API access