Question 1

How do I add Fairu as a subgraph to my existing gateway?

Accepted Answer

You point your gateway at the Fairu GraphQL endpoint and compose your supergraph. The subgraph runs on our side and the schema is introspectable, so there is nothing to install, no SDL to hand-write and no service to host.

Question 2

Can my other services reference Fairu assets by id only?

Accepted Answer

Yes. Store the asset id in your own subgraph and the gateway resolves name, metadata, copyright and delivery URL from Fairu. The references arrive batched, so a whole page of assets is resolved in one round trip instead of one per asset.

Question 3

Do I need a second call to get a resized image URL?

Accepted Answer

No. The url field takes width, height, quality and focal point as arguments and returns the finished delivery URL in the same response. What comes back from the query is what your template renders, so you never assemble URLs in code.

Question 4

What about services in my stack that do not speak GraphQL?

Accepted Answer

Every asset is also readable over the REST API with the same token — name, copyright, licenses and a ready-made delivery URL come back in one JSON response. Statamic has an official addon, and Raku credentials give S3-compatible access, so tools that only speak buckets read the same files.

Question 5

How does authentication work for the GraphQL endpoint?

Accepted Answer

You create a token in the API keys area of your workspace, tick the permissions it may use and set an expiry. The gateway sends it as a bearer token, and the workspace follows from the token, so there is no tenant id to pass around.

Media should be part of your application.

GraphQL queries and federation for your library

Questions about the GraphQL API

Connect media to your application data.