Token-based Access Revocation & AMD

Token-based Access Revocation lets you generate a "revocation list" of specific Token Authentication tokens to block access requests that include them. This helps to prevent token sharing between end users.

Before you begin

You set up Access Revocation with the Segmented Media Protection behavior in your AMD property. You also need to use the Access Revocation API for configuration. Both require the following:

  • You need to have it added to your contract. Work with your ​Akamai​ account representative to ensure your contract includes the AdaptiveMediaDelivery::AccessRevocation product.

  • Meet the API's prerequisites. Before you use the Access Revocation API v2 for any operation, you need to meet all of the requirements covered in the Get started section of the API's documentation.


You can't use basic Access Revocation if you have a custom Token Authentication scenario. A custom scenario doesn't use the default scenarios you can define using settings in the Segmented Media Protection behavior. It's typically set up by your account representative. Talk to your account representative to see if you can use Access Revocation.

First, create a token and set its "session ID"

Access Revocation uses a specific value included in a token: its session identifier ("session ID"). A session ID lets you control the level used to revoke the token. Here are a few example cases:

  1. You can use a unique session ID for each session to revoke that playback session. The stream thief will have to log back in to restart playback, and then re-share the URL with the unauthorized users all over again. This isn't a complete deterrent, but it makes it inconvenient to pirate content.

  2. You can use the specific user ID as the session ID. This blocks the specific user from accessing all content that's served through your AMD property for 24 hours.

  3. You can use a composite session ID for a specific user ID and content combination. For example, if the stream thief is sharing a live event link, he wouldn't be able to access the live event for playback himself during its duration or for 24 hours, whichever is earlier.

Generate a token to define the token and extract its session_id value for use later in this process.

Next, create a revocation list

You create a revocation list using the Access Revocation API.

  1. If necessary, work with your account representative to obtain the ​Akamai​ contractId assigned to your instance of Access Revocation.

  2. Build a new revocation list object. Include a unique name for the revocation list. It can contain alphanumeric and dash characters. Also, include your applicable contractId.

  3. POST the object to /taas/v2/revocation-lists.

    POST /taas/v2/revocation-list
        "name": "Baseball-ws-2019",
        "contractId": "1-ABCDE"
  4. The operation responds with a revocation list object. Make note of the id value from the response. This is its revocationListId.

        "id": 1,
        "name": "Baseball-ws-2019",
        "contractId": "1-ABCDE"


You can only have one revocation list.

Now, enable the revocation list in Property Manager

You need to enable and configure the Token Authentication behavior as normal. But, ensure that you set the following, to enable Access Revocation and add your revocation list:

  • Enable Session-Id. Set Advanced Options to On and ensure that the Session-Id slider in the Field Carry-Over options is set to Yes. This ensures that the session_idin the token in a request from an end user is reviewed against what you've set in your revocation list, to determine access.

  • Set Token Based Access Revocation options. Set these options as follows:

    • Token Revocation. Set this slider to On.
    • Revocation List Name. Use this drop-down to select the revocation list you created using the API.

Disable token revocation

This is relatively simple.

  1. Create a new version of your property

  2. Set Token Revocation to "Off" in the Segmented Media Protection behavior in the new version.

  3. Save the new version, test it, and go live.

You can delete a revocation list using the Access Revocation API. Be sure to disable token revocation before you delete your revocation list. Deleting before disabling could negatively affect the delivery of your content and create unwanted errors for your end users.

Finally, revoke tokens

Once your AMD property is live on the ​Akamai​ production network and it's delivering your content, use the Access Revocation API to revoke offending tokens. You add individual "identifier" objects to the revocation list that contain the unique session_idset in the offending token.

  1. Ensure you have the following:

    • revocationListId. This is the id that was generated for your revocation list after you created it.

    • session_id. Get this from the access token that you've configured to support Token Authentication. This value serves as the token identifier id.

  2. Build a new identifier array. Add an object for each token you want to be revoked. Include the identifier id for each, and optionally include the durationSecondsmember to set a time to live for the revocation. After this period, tokens are "unrevoked" and can be used again to access content.

  3. POST the object to /taas/v2/revocation-lists/{revocationListId}/identifiers/add.

    POST /taas/v2/revocation-lists/{revocationListId}/identifiers/add
            "id": "<session_id of a token to be blocked>",
            "durationSeconds": 18000
            "id": "<session_id of a token to be blocked>",
            "durationSeconds": 3600

The operation responds with the metadata object that shows the current count of token identifiers in the revocation list and the maximum number of identifiers it can house.

    "count": 500,
    "limit": 25000


You can have a maximum of 25,000 identifiers in a single revocation list.

Use the bulk update method (recommended)

When setting up your workflow to revoke tokens via the API, try to include as many identifier objects as possible, up to a maximum of 5,000 in a single call to the API. Anything more than that in a single call can create performance degradation and may result in errors and retries. If you need to set up multiple operations, issue them individually over some interval of time. For example, you could set up one every 30 seconds.


You're limited to a total of 60 operations per minute with the Access Revocation API v2. See the Access Revocation API documentation for details on how rate limiting is applied.




How long does it take to revoke?

Revocation time is five minutes from the time an offending token is discovered until ​Akamai​ begins the durationSeconds time to live (TTL).

Are there other API operations?


What's above is just the basic workflow to add Access Revocation. The Access Revocation API offers several more operations you can use. For example, you can review your revocation list stats and even "unrevoke" a token that you've previously revoked. See the Access Revocation API v2 docs for details.

Can it be used with Watermarking?


When a valid user requests content, watermarking distributes segments of content based on a pattern that's unique to that user. This is called a "watermarking token (WMT)." If your content is pirated or redistributed, you can analyze the content and extract the user's WMT to identify the user that originally leaked the content.

You can also use Access Revocation to deny access to requests that include a WMT that's been flagged. See Watermarking with Access Revocation.

Did this page help you?