Skip to main content
🔍

DAM Audit Webinar

Learn how to clean, organize, and optimize your DAM portal.

Hello - we are seeing some inconsistencies with the API that I have not been able to replicate successfully. 

  • In our logs I am seeing occasional responses from the API /media endpoint where metadata properties come back with all metadata options
    • Even though the media item does not have all metadata options
  • I then grab the asset ID from the logs and manually hit the endpoint with the same asset ID / same request 
    • In these cases I always see the expected response

Hi ​@sbuck I am continuing the conversation on the thread here.

These issues are for the API (we are seeing it in the Constellation instance).

Essentially what is happening:

  • We have a service that hits the media API endpoint
  • We are seeing cases where the API response is 1. not consistent and 2. doesn't align with what is shown in the Bynder UI.
  • I believe these issues are coming from the same thing.
  • We have logs from the Bynder API showing responses with this behavior.
  • I have not been able to replicate it. 
  • In our logs we see responses where the media item has all metadata options in the response. For example, an asset will come through with all brands on it.
  • When I make the same request or check in the UI - the asset(s) only have 1 brand tagged to it.
  • We are seeing this across other fields - user audience and internal/external were also flagged. 

Thank you for your patience ​@sbuck. After discussing with the team, we determined that the best way to address these types of questions is through a live call. I’ll reach out to the account’s CSM to coordinate next steps.

Bynder Community TermsCookie settingsAccessibility statement