Gracenote Integration
Bring your licensed Gracenote metadata into Origin Studio and use it to enrich your Records.
If your organisation licenses Gracenote, you can connect your Gracenote account to Origin Studio. Origin Studio pulls in the Gracenote data your licence covers, then checks regularly for updates. That data appears on your Records for review alongside other external sources.
How it works
Connect: an administrator adds your Gracenote API key and chooses how often to check for updates.
Initial load: Origin Studio downloads the Gracenote data your licence covers. This runs once and can take a long time, potentially 24 hours or more for large catalogues.
Ongoing updates: after the initial load finishes, Origin Studio checks Gracenote on your chosen schedule.
Enrich: add a Gracenote ID (TMS ID) to a Record to see its Gracenote data in the External Data tab.
Set up the integration
Go to Administration › Integrations › Gracenote.
Enter your Gracenote API key. It's stored securely and never shown again. Afterwards, only its first and last two characters are displayed.
Choose how often to check for updates:
SettingOptionsWhat it checksProgram updates
Every 15, 30, 45 or 60 minutes
New and changed titles
Taxonomy updates
Daily or weekly
Gracenote reference lists, which change rarely
Each check uses your Gracenote API quota. More frequent checks mean fresher data but higher usage. There's no default, so choose what suits your licence.
Save, then start the initial load. [Confirm: does the load start automatically on save, or from a separate button?]
You can follow the initial load's progress in Background Jobs.
Check the integration's status
The Gracenote page shows:
Initial load status: Not started, In progress, Finished or Failed. If it fails, the reason is shown.
Update health for each feed:
Pending
Scheduled but not yet checked
OK
The last check succeeded
Unauthorised
Gracenote rejected your API key. Replace the key (see below).
Error
Something else went wrong. The message explains what to do.
You'll also see when each feed last checked successfully, when the next check is due, and whether it's fully up to date. A feed marked stalled is overdue for a check. Contact support if it stays stalled.
Pause and resume updates
Use Pause to stop checking Gracenote for updates, for example to save API quota. Select Resume to start again.
While paused:
No update checks run and no API quota is used.
Your existing Gracenote data and settings are kept.
An initial load already in progress still finishes.
Replace your API key
Enter a new key at any time, for example when your current one expires. Your existing Gracenote data is kept, and updates continue with the new key.
Change the update schedule
Change the program or taxonomy settings at any time. The new schedule takes effect from the next check.
Use Gracenote data on a Record
Add the title's Gracenote ID (TMS ID) to the Record.
Open the External Data tab to review the Gracenote values.
Copy the values you need into the Record. [Confirm: can the AI assistant apply Gracenote values?]
Video descriptors from Gracenote are shown in a readable format rather than as raw codes. [Confirm: where descriptors appear and what they include]
Gracenote data is used to enrich Records one at a time. It can't be used to bulk-import titles.
Disconnect Gracenote
Disconnecting deletes your stored API key immediately and stops all updates. [Confirm: what happens to cached Gracenote data. The API reference says it's kept, but the original spec says it's purged to meet licensing terms.]
For developers
The integration can also be managed through the API. See Licensed Metadata.
Last updated