API Changelog and Compatibility

The public API is versioned in the path: every route lives under /api/v1/. This page records what has changed and what you can rely on.

Compatibility Promise

Within v1, these changes are additive and can ship at any time without notice:

• New routes
• New optional fields in responses
• New optional fields in request bodies
• New scopes, and new values in enumerations your client should already handle unknown values for

These are breaking and will only ship under a new version path:

• Removing or renaming a field
• Changing a status code or the error envelope
• Making an optional request field required
• Changing the meaning of an existing scope

Write your client to ignore fields it does not know and to tolerate new enum values, and additive changes will never reach you as an error.

Changelog

2026-10-19: v1 initial release

• Organization API keys with scopes, created by organization owners in Organization → Settings → API keys
• Assets: list, get, download URL, update metadata, move, publish and unpublish, hide and unhide, tag and untag, delete, bulk delete
• Folders: list, create, rename, delete
• Tags: list
• Collections: list, create, get, update, delete, add and remove assets, list, add, and remove members
• Approvals: list, create, get, update, deactivate, regenerate passcode
• Upload links: list, create, revoke, resend
• Uploads: presign, complete
• Interactive API reference generated from the same schemas the server validates with

What's Next

• Authenticating with an API Key: start here
• API reference: every endpoint