On Fire TV, the single biggest discovery driver is voice - and Alexa voice queries route through the Video Skills Kit (VSK). If your Fire TV app does not implement Alexa deep linking, you are invisible to roughly 40% of all Fire TV content searches. Here is how to fix that.
What Alexa deep linking actually does
When a Fire TV user says "Alexa, play The Crown," Alexa needs to know (a) that your app has that title, (b) where to send the user inside your app, and (c) whether the user is entitled to play it. Video Skills Kit gives Amazon that information through a catalog ingestion feed plus a runtime skill.
Done right, the user lands on your playback screen with the title already playing - no menu navigation. This is the gold standard for CTV UX and Amazon weighs it heavily in recommendations and home-shelf placement.
Step 1 - Register your Fire TV app for VSK
Go to the Amazon Developer Console, open your Fire TV app, and enable the Video Skills capability. You will receive a Skill ID and a catalog endpoint configuration. You also need to set up an Alexa-linked OAuth flow if your content is gated.
Step 2 - Deliver your catalog feed
Amazon's Catalog Ingestion expects a normalized JSON feed listing every title in your app - movies, TV series, seasons, and episodes - with their IDs, titles, descriptions, runtime, genre, rating, and most importantly your in-app deep-link URI.
Update the feed at least daily. Stale catalogs hurt your voice match quality. For most publishers a nightly cron job that exports from your CMS into the VSK schema is sufficient.
Step 3 - Handle PlayVideo and SearchAndPlay intents
Your app must register an Android intent filter that responds to the VSK PlayVideo broadcast. When Alexa fires the intent, your app receives the contentId and an optional offset and is expected to begin playback within 3 seconds - or Alexa will fall back to a different result.
- Pre-warm your player on app launch so PlayVideo intents start instantly.
- Handle the SearchAndDisplayResults intent for queries that match more than one title.
- Always honour the offset parameter for resume-playback queries.
Step 4 - Authentication and entitlements
If a user asks for a title behind your paywall, Alexa needs to know whether they are entitled. Implement the Alexa account-linking flow once at install (OAuth 2.0) and respond to the GetPlayableItems request with entitlement state per title.
If the user is not entitled, return an appropriate error - Alexa will route them to your upsell flow instead of failing silently.
What you get in return
Apps that fully implement VSK see 25–40% lift in monthly active sessions on Fire TV within 90 days. They also appear in the Universal Search results on the Fire TV home screen, which is real estate you cannot buy any other way.
The bottom line
Voice is the most under-utilized discovery channel in CTV. If your Fire TV app does not handle Alexa deep linking, your competitors are catching the queries you are missing. OTT Engine generates the catalog feed, intent handlers, and entitlement responses automatically when you launch on Fire TV. Want a walkthrough? Book a demo.
Frequently Asked Questions
Is Video Skills Kit required to publish a Fire TV app?
No, but Amazon strongly prefers apps that implement VSK and will preferentially surface them in search, recommendations, and the Universal Catalog.
How often should I update my VSK catalog feed?
At least daily. Apps with stale catalogs see lower voice-match accuracy and may be deprioritized in search results.
Can VSK deep-link into paid content?
Yes. Implement Alexa account linking and return entitlement state per title. Unentitled users are routed to your upsell flow.
Does VSK work for live and FAST channels?
Yes. The schema supports linear channels and live events alongside on-demand titles.
How long does VSK certification take?
Plan for 2–4 weeks from catalog submission to certification, plus another 1–2 weeks for the runtime skill review.