All endpoints on Disguise Cloud are protected by authentication. To authenticate your requests, you will need an API token. You can generate an API token in the Cloud Dashboard.
Please Note: The API is available to all users on an organisation that are either an admin or an owner on that organisation. If you are not an admin or owner, you will need to request access from an admin or owner before you can use the API.
API tokens are scoped to an organisation and the user that generated it. This means that an API token can only be used to access resources within the organisation that it was generated for. This by extension gives access to all resources that the organisation has access to (e.g. drives, the content inside those drives, etc.).
If you need to access resources in multiple organisations, you will need to generate a separate API token for each organisation.
To generate an API token, follow these steps:
There may be cases where you need to revoke an API token. Revoking a token will immediately invalidate it, please ensure any services or applications using the token are updated with a new token before revoking it if they are still required.
If you need to revoke an API token, follow these steps:
To use the API token in your requests, you will need to include it in the Authorization
header of your HTTP requests. The header should be in the following format:
Authorization: Token YOUR_API_TOKEN
Replace YOUR_API_TOKEN
with the API token you generated in the Cloud Dashboard.
An example of how to use the API token in a cURL request is shown below:
curl -X GET https://api.disguise.cloud/v1/self \
-H "Authorization: Token YOUR_API_TOKEN"