Raster REST API
API by Raster · rest
Resource-oriented HTTP API for Raster libraries and assets. Every response uses a { data } (success) or { error: { code, message } } (failure) envelope — code is a stable machine-readable identifier, message is human-readable copy that may be reworded at any time. Branch on code, never on message. Versioning. Every request must send an Api-Version header holding a date string (e.g. Api-Version: 2026-07-08). Responses carry Vary: Api-Version. During the Alpha every value receives the current behavior, so a breaking change reaches every integration. Deprecation policy. A version is announced as deprecated at least 180 days before it stops being served. During that window every response to a request pinning it carries an RFC 9745 Deprecation header, an RFC 8594 Sunset header holding the retirement date, and a Link header with rel="deprecation" pointing at the migration notes. Nothing is retired without those headers appearing first. Policy:…
Endpoint: https://api.raster.app/
Verification: observed. Source: crawl.
Capabilities (22)
- Create an organization library and API key with no account.
- Resolve the credential's organization and library scope.
- List libraries the credential can reach.
- Create a library in this organization.
- Get one library by id.
- Rename a library.
- List assets (paginated optional tag approval media-type and uploader…
- Upload up to 20 files.
- Move up to 100 assets to trash (soft delete).
- Suggest names for up to 100 assets.
- Rename up to 100 assets all or none.
- Apply up to 20 tags to up to 100 assets.
- Move up to 100 assets to another library.
- Remove up to 20 tags from up to 100 assets.
- Get one asset by id.
- Set one asset's approval state.
- Replace one asset's description.
- Make a variant the asset's default.
- Suggest up to three names for a library.
- List a library's tags by usage count.
- Suggest where each asset fits best 200 assets per page.
- Search assets across libraries (ranked highlighted).