Authentication
Authentication for Setten projects
Each of your projects has its endpoint and key for authentication. This design gives the user a granular approach to security. If necessary, it is effortless to remove or cycle a project key without affecting other projects.
If you are searching for a way to authenticate in a client that only accepts an URL, like Terrain for example, please see Basic auth
Authentication process
When receiving requests, we will always verify their authenticity via these simple steps:
Get the
project_id
from the first segment of the URL's pathRetrieve the
key
from the locations described in Project key locationsIf
key
is the key registered for the project with idproject_id
the request is proxied
Project key locations
Those are the locations we'll check for your project key in order. Only the first matched key will be used for authentication.
1. Header
Using the standard Authorization: Bearer
header
2. Query string
A query string named key
.
Last updated