Higgsfield API vs Sume Videos API for a Sora port: five changes

Porting from Sora to Higgsfield means five code changes: key id plus secret auth, model-specific endpoints, JSON instead of form-data, request_id instead of id, and a webhook set per request. Porting to Sume's /v1/videos means a bearer key, one endpoint, and a model field you swap. Both are real migrations; they differ in how much of your client you rewrite.

What Higgsfield's guide says

Higgsfield published a Sora 2 shutdown and migration guide. Read on 2026-10-07, it recommends Seedance 2.5, Kling 3.0 and Wan 3.0 as replacements, and describes the changes in the table below. OpenAI's own deprecations page lists no replacement for the Videos API.

Neither path preserves OpenAI's request shape, so plan the work as a rewrite of one module: the function that submits a job, the function that reads its status, and the webhook receiver. The rest of your application should only see a job id, a status and a URL.

Five changes, side by side

Same model families, one call shape

Sume's catalog carries the same three families Higgsfield recommends: seedance-2.5 (4 to 30 seconds, 480p to 1080p), kling-3 (4 to 15 seconds, 720p and 1080p) and wan-3.0 (2 to 30 seconds). Because the model is a field rather than a path, trying the second family is a one-word change in your config, not a second client.

The model names Higgsfield recommends are also valid choices on Sume, which is useful if you want to compare vendors with the same prompts. Run the same prompt on seedance-2.5, kling-3 and wan-3.0 and keep the output you prefer, then decide whether the model or the integration is the reason for your choice.

Webhook handling

The webhook side is where the two differ most in practice. Sume signs deliveries with an HMAC over the timestamp and raw body, retries up to 10 times, and lets you request a redelivery by job id. The details are in the webhook docs, and the retry numbers are sized in this receiver post.

Which to pick

If you already hold a Higgsfield account and only need one family, its guide is the shorter path. If you want to keep the option to move between Seedance, Kling, Wan and others without touching the client, put the model id in config and use the single route. Design the swap before the first call, not after.

Cost behavior differs in a way worth checking in your own test. Higgsfield's guide says failures are not charged and a balance cannot go negative, with requests queued instead. Sume reserves the cost at submit and returns a 402 insufficient_credits when it cannot, so build the retry for that status, not for a hung request.