We've added a safeguard to prevent accidental type changes that could break your content delivery.

What changed

The Ingest API will now reject requests that attempt to change the type of an existing source entity. If you re-ingest a source entity with a different type than what was originally stored, you'll receive a 422 validation error.

Why we made this change

When a source entity's type changes, any routes or views bound to that type become stale — potentially breaking content delivery without warning. This guard makes type mismatches fail loudly rather than silently, giving you immediate visibility into the issue.

What you need to do

In most cases, nothing. This guard only triggers if your ingest pipeline is attempting to change the type of an entity that already exists.

If you see the error and the type change is intentional, you have two options:

1. Delete the entity first — Remove the source entity via the delete endpoint, then re-ingest with the new type. This is the recommended approach as it properly invalidates dependent routes and views.
2. Use the bypass header — Include the X-Enterspeed-Force-Type header in your ingest request to override the protection. Only use this if you're certain the type change won't cause downstream issues.

Example error response

If you encounter this unexpectedly, it likely indicates a data inconsistency in your ingest pipeline that's worth investigating.

Questions or concerns? Reach out to us on our support Slack channel or at support@enterspeed.com — we're happy to help.