Skip to content
← Go back

API support for enumerations and their mappings

December 2nd, 2019 (Revision 1), print this page

We’ve added API support for enumerations, and any related mappings. This note describes this change in full, and as usual you can contact support or your Technical Account Manager for further clarification.

At BeBanjo we ❤️ our APIs. Letting our products play nicely with other systems is a large part of why our customers find it so easy to integrate with us.

Until recently, we hid a number of configuration items for our products away behind the scenes. Enumerations are lists of things. We often use them to define constrained lists when configuring Metadata for our customers. For example, you likely all represent your list of genres (action, drama, sci-fi, etc) using an enumeration.

These enumerations might also have mappings (you just want to store your genre of drama, because for another system that you publish to, the value might really be urn:tva:metadata:cs:ContentCS:2010:3.4 and who wants to remember that? Yuck!). Currently, BeBanjo takes care of those mappings so you don’t have to.

We also find it convenient at times to store configuration data in enumerations and now, all of that configuration data is also exposed via the API in the same way! Talk to your Technical Account Manager to discuss this further if this might be useful for your workflow.

All of this data is now exposed via our API. You can find comprehensive documentation relating to this change, and for our entire API, in the documentation section of our website, and for this change specifically in the Enumeration section.


  • movida#9073 API support for enumerations
  • movida#9401 API support for enumeration mappings