FIREANIME API
Browse API97 operations
API / V1ConnectRPC

Build with the
FireAnime graph.

Search anime, read release data, and connect community features through one generated, type-safe API contract.

97operations
15services
223message types
JSONrequest format
01

Five-minute start

One URL. One JSON body.

Every unary operation accepts a POST request. Public methods work without credentials; protected methods use the same Bearer token returned by the Auth service.

  1. 1Choose an operation.
  2. 2Send JSON to its procedure path.
  3. 3Read the JSON response.
curl 'https://fireani.me/api.v1.GenreService/GetGenres' \
  -X POST \
  -H 'Content-Type: application/json' \
  --data-raw '{}'
JSON over ConnectRPC
02

Authentication

Bearer tokens, only where needed.

Public

Public

Call the operation without an Authorization header.

Bearer optional

Context-aware

A token personalizes the response, but a public identifier can also be used.

Bearer required

Protected

Send Authorization: Bearer YOUR_JWT_TOKEN.

Obtain a token with AuthService.Login. Keep it private and never expose it in public client logs.

03

Service map

Start with a domain.

04

Failure handling

Errors follow Connect semantics.

invalid_argument

The request is missing data or contains an invalid value.

unauthenticated

A required Bearer token is missing, invalid, or expired.

not_found

The requested anime, user, topic, or related resource does not exist.

resource_exhausted

The caller exceeded an enforced request limit. Retry with backoff.

internal

The server could not complete the request. Retry only when appropriate.

Active-development API

Backward compatibility is not guaranteed yet. Usage is limited to private, non-commercial integrations and remains subject to the Terms of Use.