Acast+ Access is our B2B private listening service. With Acast+ Access you keep full control of the relationship with your audience, but with the ability to manage access to premium podcast content from within our platform.

The following concepts are useful for understanding how Acast+ Access works and how to integrate it with your systems.

RSS is the basis for modern podcasting and is what allows podcasts to be available for listening in whichever app you choose. At Acast we use individual, private RSS feeds for each listener to enable private listening. This gives Subscribers the flexibility to listen in whichever app they choose, while allowing us to ensure that your premium content is only available to them. This is also the mechanism for removing access to content if the subscription ends.

The key steps to integrating with Access are:

The subscription lifetime for a particular listener looks something like this:

With either of the above endpoints:

The request body is these two parameters as JSON

When a user's subscription lapses or is canceled, their tokens can be deactivated with a HTTP PUT to https://access.acast.com/api/v1/users/{userId}/disable (swagger docs). This will prevent them from accessing subscriber benefits, while keeping their feed url unchanged. If they resubscribe they can be reactivated without needing to update their podcast app.

Integrating with the Acast CMS is outside the scope for this document. More information can be found in the Acast CMS API documentation, or can be provided on request.

Using the CMS api to get links to podcast audio is not recommended. These should be taken from the appropriate RSS feed. Either the public feed or the individual feed for the listener. This allows us to make sure that the audio can be tailored to the user's needs.