Concepts: ingest content into AXIS
Type-Specific Metadata
The extensions object carries item-type-specific metadata.
Examples include:
| Item Type | Example Extension Fields |
|---|---|
Movie | SubType, Genres, Advisory, Duration, ReleaseYear, BroadcastDate, Cast, Crew, Copyright, MediaFiles |
Program | SequenceNumber, SubType, Location, Venue, Genres, Advisory, Duration, ReleaseYear, BroadcastDate, EventDate, Cast, Crew, Copyright |
Season | SeasonNumber, Genres, Advisory, ReleaseYear, Cast, Crew, ShowTitle, ShowId, SeasonId |
Episode | EpisodeNumber, Genres, Advisory, Duration, ReleaseYear, BroadcastDate, ShowId, SeasonId, ShowTitle, SeasonNumber, EpisodeTitle, VideoId, MediaFiles |
Only populate extension fields that are supported by the relevant item schema and meaningful for your integration.
Schedules
A schedule represents one day of EPG data for a single channel. Schedules are submitted using an external ID:
POST /v1/{tenantId}/schedules/{externalId}
The externalId in the path is your stable identifier for the
schedule, for example:
bbc-one-2024-10-15
The schedule ID is deterministic, derived from the channel ID and date
label. Submitting the same channel and date combination is idempotent.
Schedule items can link to existing Catalog items using itemId. If
itemId is omitted, the schedule item is broadcast-only and has no
catalog link.
Idempotency and Deduplication
By default, the ingestion service computes a checksum of each ingest
payload.
If an identical payload has already been processed successfully for
the same externalId, the workflow is skipped and 200 OK is
returned immediately.
This makes it safe to resubmit the same feed multiple times.
Use forceUpdate=true when you need to force reprocessing, such as
after fixing a failed image upload step. This bypasses the checksum and
re-runs all workflow steps from the beginning, including re-uploading
images and re-creating offers.