> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/connect-and-verify-apple-podcasts-delivery.md). # Connect and verify Apple Podcasts delivery Connect Apple Podcasts video to the existing RSS episode, verify HLS and interstitial behavior, and keep the audio recovery path safe. Apple Podcasts uses the normal RSS episode as the content identity. The HLS video presentation is associated with that episode through Apple Podcasts Connect. The HLS association does not replace the RSS feed, and Apple controls final playback on its platform. Podigee prepares and hosts the HLS media, resolves dynamic interstitials, and records delivery evidence. Apple decides when to fetch the media, which variant to play, and how platform playback and platform advertising behave. ## Before you start * The RSS episode has a stable canonical GUID. * The audio and video masters are ready for the selected episode. * You have a valid HLS Primary Playlist URL that Apple can reach. * The Apple Podcasts account and show association are available to the workspace. * You have current Apple provider authorization or a named owner who can complete it. * Your ad breaks and fallback policy are already approved. Keep the existing RSS audio route available until the HLS asset and its recovery path are verified. A connected Apple show does not prove that an episode is ready for video delivery. ![The One Podigee Add flight form shows the delivery destination and the choice between Podigee delivery and a connected demand provider.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5fc4e4d261a5d8c83f52f4569ec7dfeb55c32a06%2Fdoc-monetization-034-add-flight.jpg?alt=media) *Choose a connected provider only when its connection has passed the required checks.* ## Prepare the HLS presentation 1. Open **Monetization > Integrations**. 2. Select **Certify an integration**. 3. Choose **Apple Podcasts** as the delivery capability. 4. Select the episode scope and the audio and video media kinds. 5. Prepare a Multivariant Playlist with an audio-only variant, 720p video, 1080p video, and an I-frame stream. 6. Add the subtitle or caption renditions that the episode needs. 7. Use stable URLs for the Primary Playlist, Media Playlists, segments, captions, and interstitial assets. 8. Set the required CORS headers and exact media MIME types. 9. Submit the HLS presentation for validation. Apple may request video after it has already downloaded audio. Keep the Primary Playlist and all referenced media reachable and consistent for later replay. ## Configure dynamic interstitials Use an HLS interstitial marker at each approved ad break. Select one of these delivery methods: * **Direct asset:** use `X-ASSET-URI` when the interstitial playlist is already known. * **Dynamic asset list:** use `X-ASSET-LIST` when Podigee must select the interstitial at playback or download time. The dynamic asset response must contain an `ASSETS` array. Each asset needs a Media Playlist URL and an exact duration. An empty `ASSETS` array is valid when no ad is available. Do not treat a valid no-fill response as a delivery error. Align the interstitial with a valid segment boundary when possible. Keep the planned and exact duration values consistent with the ad media. Use the approved fallback when the decision has no eligible ad. ## Associate HLS with the RSS episode For a new episode: 1. Create and validate the HLS presentation before the RSS episode is public. 2. Submit the Primary Playlist URL to the Apple Podcasts Connect staging operation with the future RSS canonical GUID. 3. Keep the URL reachable while Apple processes the staged asset. 4. Publish the RSS episode. 5. Check that Apple associates the staged HLS asset with the published episode. For an existing episode: 1. Wait until Apple has discovered the RSS episode. 2. Add the Primary Playlist URL through the Apple episode asset operation. 3. Read the resulting association and processing state. 4. Use the same episode operation for later updates or removal. The exact Podcasts Connect endpoint, authentication, limits, and error contract must come from the current Apple API documentation. If the workspace does not have that contract or authorization, Podigee keeps the operation blocked instead of pretending that a local HLS check is Apple certification. ## Verify the presentation 1. Run Apple's Media Stream Validator against the Primary Playlist. 2. Review index, variant, segment, caption, CORS, and interstitial findings. 3. Correct every error and every issue that can affect playback or ad timing. 4. Run the Podigee delivery check for audio-only playback. 5. Run the check for video playback and delayed companion-video retrieval. 6. Request a dynamic asset list at each test break. 7. Confirm that the decision, selected asset, exact duration, and measurement evidence agree. 8. Save the validator output and the Podigee verification result. A valid playlist is not enough. The media must remain replayable, the interstitial must fit the timeline, and the evidence must show which asset the listener or viewer received. ## Activate Apple delivery 1. Open the Apple connector state in **Monetization > Integrations**. 2. Confirm the RSS episode, HLS asset, provider association, and validator evidence. 3. Confirm that the Apple authorization and production certification are current. 4. Select the activation action. 5. Choose the effective time and confirm the exact episode scope. 6. Monitor the first Apple processing and delivery results in **Operations** and **Evidence & Money**. Apple remains the authority for streaming and final playback. Podigee must label Apple outcomes as Apple-controlled and must not count an Apple platform result as a Podigee delivery event without the required evidence. ## Recover safely Keep the existing RSS audio delivery available while Apple processing, HLS, or interstitial validation is incomplete. If an HLS check fails, repair the exact version and run validation again. If Apple is unavailable, pause the Apple capability and continue the approved RSS audio route. Do not replace the RSS episode URL to repair an Apple HLS association. Keep the RSS identity stable and repair the HLS association through the declared Apple operation. ## Expected result The RSS episode remains the stable content identity. Apple has a reachable HLS presentation with valid audio, video, captions, and interstitial behavior, and the Podigee Ad Server has current evidence for the exact episode and capability. If Apple delivery is not ready, listeners still have the existing RSS audio path. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/connect-and-verify-apple-podcasts-delivery.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.