Skip to main content

Go-Live Checklist

Here is the criteria that we will use to test a customer's implementation before approving them to go live in production using the API.

User Identification

  • Unique users are properly tracked across multiple devices as client_id.
  • Users are tracked according to their correct business model.

Basic Content Viewer Flow

The following will be tested across all applicable web and mobile platforms.

  • Invokes /v2/app/start when app starts.
  • Invokes GET /v2/clips/rights before playback or GET /v2/clips before streaming.
  • Invokes POST /v2/clips/{id}/play when playback begins.
  • Invokes /v2/app/close when app closes.
  • Correctly handles tracks that have been taken down.
  • Client ID follows user across devices.
  • Offline playback is handled correctly by one of the following patterns:
    • streaming is prevented when POST /v2/clips/{id}/play fails due to networking.
    • streaming continues and POST /v2/clips/{id}/play is invoked in the future with a back-dated timestamp and offline play method.

Content Creator Flow

The following will be tested across all applicable web and mobile platforms.

  • Previewing clips invokes POST /v2/clips/{id}/preview.
  • Create a custom clip:
    • User may not listen to the full track uninterrupted.
    • Custom clips cannot exceed 60s in length.
  • Previewing a track while making a custom clip invokes POST /v2/tracks/{id}/play.
  • Apps in non-US + territory markets: graceful UX blocking access to the API.
  • Adding a clip to content:
    • POST /v2/clips/{id}/add is invoked when a clip is added to content.
    • No more than one clip is able to be added to media.
    • Ensure it plays after being posted (if applicable).
  • If looping is applicable, a POST /v2/clips/{id}/play event fires each time the audio loops.
  • Sharing to a 3rd party works as expected, invoking POST /v2/clips/{id}/share.
  • If downloading is permitted, invokes POST /v2/clips/{id}/download.

Licensing Requirements

  • Artist, album, track appears during playback.
  • End User Licensing Agreement is Updated with Feed Terms.
  • Feed Clips are not accessible outside the US & its territories.
  • If applicable, test that Content ID passes and fails as expected.
    • Track in the background is in our catalog: pass.
    • Track in the background and we can't match it to anything: pass.
    • Track in the background isn't in our catalog: blocked.

Post-Launch Confirmation of Prod Credentials

  • Ensure production API credentials (not development) are used after going live.