Akamai: IoT Token Access Control API
Akamai: IoT Token Access Control API endpoints from Akamai
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Akamai: IoT Token Access Control API endpoints from Akamai
Endpoints 7
Activations
- GETList activations
/activations?collectionId={{collectionId}}&accountSwitchKey={{accountSwitchKey}}Returns a list of activations for the key collection. If you don't already have the collectionId, run the Get key collections operation and use the… - POSTActivate a key collection version
/activations?accountSwitchKey={{accountSwitchKey}}Deploys the version of a key collection in the staging or production environment. Note that a key collection uses the public keys from its active version to…
Key collections
- GETList key collections
/key-collections?accountSwitchKey={{accountSwitchKey}}Returns a list of key collections for the associated account. Also, for each returned collection, it specifies if any key collection versions are active in… - POSTCreate a key collection
/key-collections?accountSwitchKey={{accountSwitchKey}}Creates an empty key collection. To upload public keys to a newly created collection, run the Create a key collection version operation. Also, store the id of… - GETView a key collection
/key-collections/:collectionId?accountSwitchKey={{accountSwitchKey}}Returns details about the key collection, listing all created versions and specifying the ones active in the production and staging environments. If you don't…
Versions
- POSTCreate a key collection version
/key-collections/:collectionId/versions?accountSwitchKey={{accountSwitchKey}}Creates a version of the key collection. This lets you provide primary and secondary public keys to verify JWTs passed in client requests. If you don't… - GETView a key collection version
/key-collections/:collectionId/versions/:versionId?accountSwitchKey={{accountSwitchKey}}Returns details about the key collection version. It returns the public keys the version uses to verify JWTs and reports on whether they're are active in the…
API details
- Base URL
https://{hostname}/jwt-api/v1- Authentication
- None declared in the description
- Operations
- 7 operations on 5 pathsGET 4POST 3
- Main resources
- Key collections 3Activations 2Versions 2
- Response formats
application/json*/*- Description format
- OpenAPI 3.0.0, API version
1 - Links
- Documentation · OpenAPI document
- Listed from
- Akamai's published OpenAPI description (akamai/akamai-apis) (Apache-2.0)
How to test the Akamai: IoT Token Access Control API in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Akamai: IoT Token Access Control API collection, without the publisher's secrets.
- Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
- Send a requestPick an endpoint, for example “List activations” (GET /activations?collectionId={{collectionId}}&accountSwitchKey={{accountSwitchKey}}), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Akamai: IoT Token Access Control API?
Akamai: IoT Token Access Control API endpoints from Akamai It is listed under Developer tools and has 7 endpoints.
Who publishes the Akamai: IoT Token Access Control API?
It is listed from Akamai's public API description (an OpenAPI document), not published by Akamai on Swastik Codes. Anyone who controls akamai.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Akamai: IoT Token Access Control API?
Requests go to https://{hostname}/jwt-api/v1. Endpoint paths are added to this base URL.
How do I authenticate with the Akamai: IoT Token Access Control API?
Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.
How many endpoints does the Akamai: IoT Token Access Control API have?
7 operations on 5 paths (4 GET, 3 POST). The largest groups are Key collections, Activations, Versions.
Is forking the Akamai: IoT Token Access Control API free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.