API protocol

Legacy Apifox compatibility and migration

Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Legacy Apifox compatibility and migration

Direct answerConfirm the model and endpoint in the marketplace, then migrate paths, fields and task results; legacy release tags do not guarantee gateway availability.

Updated · Reviewed

Using the legacy documentation

This page compares the legacy Apifox directory with gateway code reviewed on November 8, 2026. States are documented gateway contract, conditional support, retired, unimplemented/unregistered, and unverified. A registered route is not proof that a model or channel is callable. Check the exact model, key group and channel in the marketplace. A legacy released label is not a gateway availability guarantee.

Paths and capability migration

Legacy path or scenarioCurrent boundaryIntegration route
/api/token/key/{key}Key in path plus owner ID; raw quota unitsLookup; prefer Bearer usage
Published MJ actionsIndividual action definitions; do not reuse Imagine payloads for every actionMJ guide and the index below
/async/*Retired; returns 410 after authenticationUse explicitly supported async image tasks; changing a prefix is insufficient
/get-asyncRemovedQuery new tasks through their creation protocol; no automatic migration of old IDs
/flux/v1/chat and legacy FLUX model pathsNative converter currently accepts only flux-3-imageNative FLUX; other models need an explicitly supported unified image endpoint
/tran/{url}, /source/{task_id}External/legacy AsyncData service; not registered hereNo equivalent gateway compatibility route
/luma/*, /pika/*, /pixverse/*, /vidu/v1/tasks, /ideogram/v1/*, /avatar/*, /v4/videos/*These legacy native protocols are unregisteredIf a model exposes unified images/videos, rewrite its request and result handling for that protocol; no one-to-one URL substitution
/kling/v1/videos/effectsRegistered, but the adapter omits effect_scene and inputRequires adapter completion and acceptance testing; the Kling guide does not establish effects support
Responses backgroundNot enabled in the request DTO; no background retrieval/cancel routesUse synchronous or SSE Responses
Sora characters and storyboardCharacter creation/retrieval contract unverified; storyboard text is a prompt convention without timing guaranteesModel scenarios
Files, Fine-tuning, Assistants/Threads/Runs, link analysis, UdioLegacy developing/deprecated/conflicting entries are not published as callable APIs; /v1/files etc. are placeholdersCheck the endpoint matrix; Responses tools are not the Assistants API

The legacy “delete fine-tuned model” page used GET /v1/models/{model}. Gateway GET retrieves model information; it does not delete models. Missing legacy protocols do not imply that every model from those providers is unavailable.

The original 21 withdrawals remain. The November 9 review withdrew another 49 references, including legacy lyrics. On November 10, the always-failing legacy log search was also withdrawn, totaling 71 withdrawals. The 70 published references include the separate U1 button upscale contract; see current gateway workflows. Acceptance covers the tested site, key and parameters, not every channel or parameter combination.

Midjourney action index

Fields reuse marketplace quick-start definitions. /mj defaults to fast. See individual references for mode prefixes, token-fixed mode and source-channel affinity.

ActionAPI
Midjourney imaginePOST /mj/submit/imagine
Midjourney high variationPOST /mj/submit/action
Midjourney panPOST /mj/submit/action

Batch retrieval returns the account’s task array. Follow-up customId values must come from actual source-task buttons.

Legacy Suno publication scope

Music generation and existing-task retrieval remain documented. Lyrics and all v2 action and retrieval examples are withheld pending acceptance. Legacy success is not evidence for v2; never reuse resource IDs across protocols.

Validation scope

These statements follow routes, DTOs, adapters and documentation contracts. They are not a verbatim copy of all legacy pages or proof of successful upstream calls. Verify minimum requests, stream completion or terminal states, errors and result decoding for the selected model/group before integration. Inspect records after creation timeouts to avoid duplicate submissions.

The separately verified U1 button workflow is documented in current gateway workflows. The original 21 references remain withdrawn; action success does not establish change support.

Use cases

  • Migrate legacy clients
  • Verify model fields and support boundaries

API protocols

  • /v1/chat/completions
  • /v1/videos

FAQ

Does a legacy released label establish support here?

No. Check gateway routing, field conversion, channel and model-group support.

Can I migrate by changing only the URL?

No. Check authentication, fields, submission responses, task IDs, terminal states and results.

Have all models passed live acceptance tests?

No. This is a code/documentation contract review, not paid upstream acceptance for every model.

Official sources

  1. Tuzi legacy Apifox documentation (comparison source) Official