Publish identity
GET /api/releases/publish — inspect the key; does not write.
AuthorizationBearer <token>字幕组 API Key。Authorization: Bearer <KEY>。与 X-API-Key 二选一,Bearer 优先。
Key scope:releases:publish、releases:delete、releases:sync:read,至少选一个。
当前 Key 的发布身份
application/json- response
ok*truetrueresult*curl -X GET 'https://anibt.net/api/releases/publish'{ "ok": true, "result": { "groupId": "org_example", "groupName": "Example Group", "groupSlug": "example", "apiKeyId": "sgak_example", "apiKeySuffix": "abcd1234", "scopes": [ "releases:publish", "releases:delete", "releases:sync:read" ], "kind": "anime" }}Subscription RSS GET
GET /rss/subscriptions.xml — private merged feed from saved subscriptions.
Publish anime POST
POST /api/releases/publish — publish with an API Key. Idempotency-Key binds the complete request from first acceptance. Changed requests return 409 CONFLICT; unfinished legacy uploads without a binding return legacy_request_binding_missing. Use a new key for either case. Publishing a version the group already has returns 409 CONFLICT with error.reason RELEASE_VERSION_EXISTS. A torrentStorageId whose torrent another release or another user's unexpired preview already uses returns 409 CONFLICT with error.reason TORRENT_IN_USE. See Conventions and authentication for replay and 503 retry rules.
