Thanks for your feedback!
EDIT
Access Tokens
An access token is an object that includes authorisation data that enables an application to access an API.
For the API Platform, an access token is always used alongside an app and it is only obligatory in a request if the API it accesses is configured so as to require Access Token Validation.
| As one app can be linked to more than one API, through different plans, a given access token can be used to access different APIS. |
List of access tokens
The Access Tokens page, which displays existing tokens and allows registering new ones, is accessed via the main menu, as shown below.
On this page, existing tokens can be seen on a list that contains these details: access token code, the token’s owner, the app linked to the token, its status and creation date. It is also possible to use the action icons to edit a token or visualise more information (associated APIs and plans).
The page also contains a search field, with enables tokens to be filtered by code, owner, status, date of creation, associated API and/or APP.
The search fields for API and APP allow multiple selection. This means that you can perform a search by entering more than one API and/or APP at the same time.
Within the same field, the OR operator is used: any of the conditions must be met for a record to be selected. Thus, if you search, for example, for two APIs (API1 and API2), the result will show all Access Tokens of API1 and API2. The same applies to searches for more than one APP.
Between fields, the operator used is AND: all conditions must be met for a record to be selected. For example, if you search for API1 and API2 and APP1, the result will show all Access Tokens associated to APP1, whether they are from API1 or API2. If you search for API1 and API2 and APP1 and APP2, the result will show all Access Tokens associated to APP1 or APP2, whether they are from API1 or API2.
Share your suggestions with us!
Click here and then [+ Submit idea]