Versioned source contract

AniFix API

These are the routes implemented by the current AniFix server. API access uses scoped bearer credentials plus client identity headers. Example credentials and unimplemented compatibility URLs are intentionally not shown.

GET/v1/capabilities

Supported protocol, filters, identity fields, and feature flags.

GET/v1/status

Current service state, queue health, workspaces, cleanup, and restoration estimate.

POST/v1/search/releases

Cursor-paginated release search using canonical IDs, titles, episode identity, and media filters.

POST/v1/selection-plans

Deterministic Good, Better, or Best recommendations with coverage and storage estimates.

GET/v1/releases/{release_id}

Published artifact records for one stable release ID.

GET/v1/releases/{release_id}/artifacts

Published artifacts attached to one release.

GET/v1/artifacts/{artifact_id}

Artifact metadata, availability, repairability, verification, and manifest.

GET/v1/artifacts/{artifact_id}/download

Account-authorized NZB delivery.

POST/v1/artifacts/{artifact_id}/reports

Submit a correction or integrity report.

GET/api?t=caps|search|tvsearch|get

Newznab-compatible capabilities, search, and account-authorized NZB retrieval.

Integration status

Native API: Implemented
Emaki integration: Contract ready; client connection pending
Newznab adapter: Implemented
Account-scoped credentials: Available to verified accounts

Signed-in members can create display-once, least-privilege credentials from their API credentials page.