Is your feature request related to a problem? Please describe.
When processing webhook payloads, the alphanumeric model IDs are not included so we're forced to try and cross-reference numeric itemType IDs manually. We need to write business logic on our side for these and it's painful because we have to maintain our own list of models in order to cross-reference. Hard-coding numeric IDs into our business logic is a dead-end. We should always have the alphanumeric model IDs available in response payloads.
Describe the solution you'd like
Include the alphanumeric model IDs in webhook payloads. Mocked webhook payload below. Note: the addition of relationships.item_type.key
Describe alternatives you've considered
We are having to grab a list of all models from the Content Management API and cache it on our server in order to have a list of models to cross-reference the itemType IDs against. Writing business logic against the numeric itemType IDs is painful and not scalable. In order to keep our list up to date, we have to have a second webhook listener to watch for model changes and invalidate our cache.
Is your feature request related to a problem? Please describe. When processing webhook payloads, the alphanumeric model IDs are not included so we're forced to try and cross-reference numeric itemType IDs manually. We need to write business logic on our side for these and it's painful because we have to maintain our own list of models in order to cross-reference. Hard-coding numeric IDs into our business logic is a dead-end. We should always have the alphanumeric model IDs available in response payloads.
Describe the solution you'd like Include the alphanumeric model IDs in webhook payloads. Mocked webhook payload below. Note: the addition of
relationships.item_type.key
Describe alternatives you've considered We are having to grab a list of all models from the Content Management API and cache it on our server in order to have a list of models to cross-reference the itemType IDs against. Writing business logic against the numeric itemType IDs is painful and not scalable. In order to keep our list up to date, we have to have a second webhook listener to watch for model changes and invalidate our cache.
Additional context