Gallery API¶
Browse 3D assets and collections, retrieve rich embeds and manage your own content through the DABBBLE Gallery API.
This documentation is based on the supplied OpenAPI 3.1 specification, API version 1.0.0. Examples are templates, not live-tested requests. Undocumented server behaviour is identified rather than assumed.
Base URL¶
The Gallery API is separate from the DABBBLE worktaster and events APIs. Its response wrappers, filters and authentication rules are different.
Guides¶
-
Assets¶
Browse, search and filter public 3D assets.
-
Collections¶
Browse public collections and their contents.
-
Files & Formats¶
Understand resource URLs, downloads, thumbnails and format metadata.
-
Login¶
Understand device-code exchange and bearer tokens.
-
oEmbed¶
Retrieve rich embed HTML and display metadata.
-
Users¶
Manage your profile, assets, uploads and collections.
Pagination¶
Asset list responses use assets; collection list responses use collections. Both include a required integer totalSize and an optional nullable nextPageToken.
Pass a non-empty next-page token as pageToken in the next request, preserving filters. Stop when the token is absent, null or empty. Do not construct or decode tokens yourself.
pageSize is declared as a string. Defaults, maximum sizes and token encoding are not documented.
Example Requirements¶
- PHP requires URL access for the stream examples.
- Node.js examples use built-in fetch in Node.js 18 or later.
- Python examples use the Python 3 standard library.
- C# examples use .NET 6 or later with top-level statements.
- Browser fetch requires suitable CORS headers from the deployment; these are not guaranteed by the specification.
Authenticated examples deliberately run server-side or in command-line tools rather than putting long-lived bearer tokens into a browser bundle.
Errors and Limits¶
Some write operations document HTTP 400 responses with an Error object containing message. The specification does not define every possible failure status or payload. Always check HTTP status before parsing a successful result. Do not parse JSON from HTTP 204 responses.
Rate limits, upload limits, cache policy, CORS policy, token expiry and service guarantees are not specified. Confirm them with the operator before depending on them.
Documentation Migration¶
These pages replace the human-facing reference in MkDocs. They do not move API traffic or change routes on the gallery service. A redirect from the old /v1/docs page must be configured on that service separately. Consider keeping the machine-readable OpenAPI endpoint available for tooling.