Higgsfield owns the promotion and its terms. Check the current offer on their site before you plan around it.
What changes when you bring a key
Everything else about the call is identical. You do not change your code to switch — you save a key, and Router uses it.
1
Get a Higgsfield API key
Create a key in your Higgsfield account. Higgsfield issues it as an id and secret pair, and Comfy stores it as the single string
id:secret — keep the colon, and do not split it into two fields.2
Save it in Comfy
Open Provider keys in your Comfy profile, choose Higgsfield, and paste the
id:secret value.Your key is encrypted at rest and is never returned by the API once saved. Router reads it only to sign your own calls.3
Create a Comfy API key
This is the key that authenticates you to Comfy, separate from the Higgsfield one. Create it in your Comfy workspace, then set:Keep API keys on your server or in your local environment. These examples are for a terminal or server, not browser JavaScript.
4
Run a model
Copy and paste a code snippet below for your selected model.
Models
- Kling 3.0 std
- Kling 3.0 pro
- Kling 3.0 4K
- Kling 3.0 turbo
- Wan 3.0
Balanced quality and speed.
duration accepts 3–15 seconds.Reading the result
run returns Higgsfield’s own terminal document. The download URL is at video.url:
queued and in_progress never reach you — you get the finished document or an error. nsfw, failed and canceled are the terminal failures; failed carries detail in error.
Notes
- Validation happens before Higgsfield is called. A body outside the published bounds comes back
422with the offending field named, and nothing is sent upstream — so a bad request costs you nothing. - Your key is used only for models you have a key for. Saving a Higgsfield key changes nothing about how any other provider on Router is billed.
- Full request and response schemas for every model are in the Comfy Router reference.