Files
2 files · 1.1 MB · verbatim copies of public vendor filesREADME — provenance
DAM Wiki downloaded these files on 2026-09-30 from public vendor URLs (no login needed). They are unmodified copies; DAM Wiki refreshes them when the API changelog (https://api.bynder.com/changelog/2026) announces changes.
| File | Format | Version / date | Public source URL |
|---|---|---|---|
bynder_postman_collection.json | Postman collection v2.1.0 | "updated 8-25-26" (name in the file); 177 requests in 37 folders; stored byte-for-byte (SHA-256 2375d451…1f33) | https://dam.bynder.com/m/5f2d178f1d6308bf/original/Bynder-Postman-Collection.json (linked from https://api.bynder.com/docs/getting-started) |
bynder_readme_openapi_fragments.jsonl | JSON Lines, one OpenAPI 3.1.0 / 3.0.0 fragment per line | 221 fragments (one per operation), page updatedAt 2024-12 → 2026-09 | Each line's source_url = https://api.bynder.com/reference/{slug}.md (index: https://api.bynder.com/llms.txt) |
Notes
- No full OpenAPI download is offered. The developer portal (ReadMe,
api.bynder.com) has its "download OpenAPI" option disabled (show_openapi_download: disabledin the page configuration, observed 2026-09-30). Every reference page, however, embeds the OpenAPI definition of its own operation in its public Markdown export (…/reference/{slug}.md, "OpenAPI definition" block). bynder_readme_openapi_fragments.jsonlholds those embedded blocks. The OpenAPI content is unchanged; only the JSON whitespace was compacted, and each block is wrapped in{source_url, page_updatedAt, fetched, openapi}. Fragments that share aninfo.titlebelong to the same API family (37 families, 221 operations). They were not merged: overlappingcomponentsare left as published.- The families use different placeholder servers (
https://{your-bynder-domain}/,https://{your-bynder-domain}/api/1/automation-workflow/,https://$ACCOUNT.bynder.com/api/1/authoring,https://api.example.com), and different security-scheme names (OAuth2+permanentToken,httpAuth,bearerAuth, none). All of them take a Bearer token in theAuthorizationheader. - Bynder wrote the Postman collection. It contains the vendor's own sample portal hostnames, placeholder IDs and example bodies, kept exactly as published. Its description tells users to authenticate with a permanent token.
- A legacy Apiary-hosted reference (https://bynder.docs.apiary.io/) is still online and still linked from the Universal Compact View page. It was not copied.
- Quick inventory:
python -c "import json;[print(r['openapi']['info']['title'],list(r['openapi']['paths'])) for r in map(json.loads,open('bynder_readme_openapi_fragments.jsonl',encoding='utf-8'))]"