Create or update Titles via the API using External IDs

Keeping Titles in sync between Mediagenix On-Demand and external systems is now simpler: integrations can create or update Titles using External IDs directly.

Until now, updating a Title through the API required the internal MOD Title ID. This meant API clients had to search for a Title first, retrieve its internal ID, and only then apply the update.

We’ve now added a dedicated UPSERT flow for the Title API. This allows API integrations to create or update a Title using an External ID in a single request.

✨ What’s new?

You can now create or update a Title by External ID using a PUT request.

When the External ID does not exist yet, MOD creates a new Title.

When the External ID already exists, MOD updates the matching Title.

This keeps the existing Title API behaviour unchanged, while giving integrations a simpler way to synchronise catalogue data with external systems.

API update

Two Title UPSERT formats are now available.

For the Default External ID, use:

PUT /api/titles/ext/{external-id}

For accounts using Multiple External IDs, use the External ID Type keyword:

PUT /api/titles/ext/{external-id-type-keyword}/{external-id}

The API returns:

As with normal Title creation, the request must include all mandatory fields when a new Title needs to be created.

Full request examples are available in the developer documentation: Upserting titles by External ID.

Why this matters

External systems often know their own identifiers, but not the internal MOD Title ID. This change reduces the need for extra lookup calls before updating catalogue records.

That means integrations can use a simpler and more efficient synchronisation flow: send the Title information with the External ID, and let MOD create or update the correct record.

This helps reduce API traffic, avoids unnecessary integration logic, and makes automated catalogue updates easier to maintain.

Important notes

This change is backwards compatible. Existing Title API endpoints and existing integration behaviour are not changed.

For Multiple External IDs, the selected External ID Type must uniquely identify a single Title. External ID Types that allow shared values cannot be used for UPSERT, because MOD would not be able to determine safely which Title to update.

There are no permission or feature-flag requirements beyond existing API access.

Have feedback or questions?

If you have any questions about this change, or you’d like to discuss how it could simplify your integrations, please reach out to your Customer Success team.