Enterprise API
Data controls, security, capacity and support for production integrations at scale.
The Higgsfield API gives every account the same endpoints. This section collects the controls that matter when you run it in production for an organization: where your data lives and for how long, who can access the API, how much capacity you get, how usage is reported, and how to reach us when something goes wrong.
Keep request inputs and outputs for as little as one hour, or delete a request on demand.
Exclude your inputs and generated outputs from model training.
Verify that every delivery comes from Higgsfield and was not modified.
What an organization shares, and what admins and members can do.
SAML single sign-on, organization roles and API key lifecycle.
Usage analytics in USD and invoice billing.
Status page, incident communication, support and SLAs.
#At a glance
| Area | What you get | Where to configure |
|---|---|---|
| Data retention | Inputs and outputs deleted after 1 hour to 7 days; delete any finished request immediately |
Hf-Expires-After header, account setting, DELETE /requests/{request_id} |
| Model training | Inputs and generated outputs excluded from training | Settings in Higgsfield Console |
| Webhooks | Standard Webhooks signatures with secret rotation | Settings in Higgsfield Console |
| Identity | SAML SSO (Okta, Microsoft, custom), Admin and Member roles with a permission matrix | Organization settings |
| API keys | Named keys with expiration, tags and last-used time | API keys in Higgsfield Console |
| Usage analytics | Per-model usage and estimated cost in USD, for dashboards and monitoring |
GET /models/usage, Higgsfield Console |
| Reliability | Public status page, correlation IDs for every response | status.higgsfield.ai |
Note
Some settings, such as an account-wide retention period, invoice billing and dedicated capacity, are configured by Higgsfield. Email [email protected] or contact your account manager.