The Seelab API uses API keys to authenticate requests. While the Seelab Dashboard for generating your own keys is currently in development, you can request API keys by contacting [email protected]. Similarly, key revocation requests can also be addressed via email until the dashboard is deployed. To access the Seelab API, you must have an active account on the Seelab application
Your API keys grant significant access to your account, so it is important to keep them secure. Do not share your secret API keys in publicly accessible locations, such as GitHub repositories, client-side code, or any other public-facing areas.
All API requests must be made over HTTPS. Requests made over plain HTTP will fail. Additionally, any requests made without proper authentication will be rejected.
Example Authorization Header
To authenticate your API requests, include the Authorization
header with your API key:
Authorization: Token <apiKey>
For example, if your API key is sl_5d44e40eac2ee46ba2abedcfa384a68c
, the header would look like:
Authorization: Token sl_5d44e40eac2ee46ba2abedcfa384a68c
If authentication fails, the API will respond with a 401 status code. Below is an example of the response:
{
"error": 1006,
"message": "Authentication failed",
"data": []
}