API ReferenceGraphQL API
Changelog
Every notable change to the Raster GraphQL API, by version.
This page tracks every notable change to the Raster GraphQL API. The format follows Keep a Changelog, and the API follows Semantic Versioning.
The API is in Alpha. Until the Beta release, minor versions may include breaking changes — review this page before upgrading an integration.
0.3.0-alpha — 2026-05-22
Changed
- Coded errors now return the data layer's explicit HTTP status on
GraphQL, matching the new REST API. Previously,
formatErrordiscarded the underlyingextensions.http.statusand hardcoded401forUNAUTHORIZEDand400for every other known code. With this change, the same error returns the same HTTP status on both transports — for exampleORGANIZATION_NOT_FOUNDnow surfaces as404(was400). The hardcoded401/400mapping remains only as the fallback when the thrown error carries no explicit status. Clients dispatching onextensions.codeare unaffected; only clients switching onextensions.http.statusfor an affected code see the new (semantically correct) value.
0.2.0-alpha — 2024-08-13
Added
assetsquery:pageandpageSizeparameters for pagination.assetsquery:tagsparameter to filter by up to 5 tags.Librarytype: atagsfield returning detailed tag information.- New
tagsquery for retrieving a library's tags.
Changed
- Optimized database queries for better performance.
assetsnow returns both user-created and AI-generated tags.
Security
- Hardened API key authentication checks for library access.
0.1.0-alpha — 2023-06-20
Added
- Initial Alpha release of the Raster GraphQL API.
- Queries for assets, libraries, and tags.
- API key authentication.
- Pagination for asset queries and tag filtering.
Changed
- Adopted Apollo Server for the GraphQL endpoint.
- Set up the Firebase Admin SDK for data access.
Security
- Introduced API key authentication for all queries.