Changelog
New features, tighter integrations, and a smoother developer experience. To catch up on our latest releases shaping our developer platform, see the link below.
New features, tighter integrations, and a smoother developer experience. To catch up on our latest releases shaping our developer platform, see the link below.
Stay up to speed with our latest developer platform releases, portal updates, and ecosystem improvements. From major MCP and SDK enhancements to core API changes, we've got your integrations covered.
Throughout this year we significantly expanded the documented API surface — adding full coverage for Brand Guidelines (CXUC), new Metaproperties and Options management endpoints, Automation endpoints, and extended analytics tracking. We also resolved a number of long-standing accuracy issues across upload, OAuth and webhook documentation.
The Bynder developer portal has a new home, with a redesigned API reference, guides and tooling in one place.
authorization_code, client_credentials and refresh_token grants1.0.0.page * limit must be 100,000 or less. Larger requests return 400 with RESULT_WINDOW_TOO_LARGE. Use cursor (start with *) to read beyond that limit.name and label differ, Bynder automatically assigns name as the externalReference. Setting externalReference to null or an empty string will not prevent this.POST /api/1/asset/assets/{assetId}/relations/{relationId} and DELETE /api/1/asset/assets/{assetId}/relations/{relationId} to the Asset API for managing asset relations, now documented under Asset enrichment.customThumbnailFileId and removeCustomThumbnail to Modify Asset.checkForDuplicates query parameter from Create Option — this parameter is no longer supported.https://bynder-public-us-east-1.s3-accelerate.amazonaws.com/ and does not include your portal domain./api/1/cxuc/), covering guidelines, groups, pages and sections.upload_id must be passed as a form field named id, not as a path segment in the URL.brandId in Save as New Asset — this is a required field, not optional.metaproperty field from the Options API v1 response — this field is no longer returned./{id}. The correct path is https://{your-bynder-domain}/v7/webhooks/public/api/subscriptions.https://{your-bynder-domain}/v6/authentication/oauth2/token/..../api/content-access/options/{optionId} and GET/PUT /api/content-access/options/{optionId}/visibility.Throughout this year we focused on tightening our API workflows and expanding the depth of our asset management tools. We rolled out significant upgrades to the Analytics module — including Collection Views V2 and a more robust Asset Usage tracking system — while cleaning up legacy V1 endpoints for a more streamlined integration experience. From adaptive video streaming and custom thumbnail controls to refinements in how metadata such as fileName is retrieved, these updates give you more granular control over your media assets and their performance data.
activeStage in the Modify job endpoint — the set is now restricted.customThumbnailFileId and removeCustomThumbnail in Modify Asset.fileName to the Retrieve assets response.additionalId property to the mediaitems response in Retrieve assets and Retrieve specific asset.Older entries will appear here as the platform evolves. Subscribe to product updates on the Bynder Community to stay informed.