Guide
Fibery API uses token-based authentication. That means you need to pass your API token with every request. This token should be the same for all requests, there is no need to generate a new one each time. Your API token carries the same privileges as your user, so be sure to keep it secret.
# To authenticate set the Authorization header in this way:
curl -X POST "https://YOUR_ACCOUNT.fibery.io/api/commands" \
-H "Authorization: Token YOUR_TOKEN" \
-H "Content-Type: application/json" \
...
# JavaScript
const Fibery = require('fibery-unofficial');
const fibery = new Fibery({host: "YOUR_ACCOUNT.fibery.io", token: YOUR_TOKEN});
Make sure to replace your account name and token with the actual values
Managing tokens
The number of tokens is limited to 3 per user.
You can generate, list and delete tokens on the "API Tokens" page available from the workspace menu.
You can also manage the tokens directly using the API. The following endpoints are available to manage access tokens:
GET /api/tokens — lists all access tokens that were given to current user
POST /api/tokens — creates new token for current user
DELETE /api/tokens/:token_id — deletes token by id
You need to be authenticated with a browser cookie or with an already existing token when accessing these endpoints.
Request limits
To ensure system stability and consistent user experience, our API is rate-limited.
Rate-limited requests will return a "Too Many Requests" error (HTTP response status 429). The rate limit for incoming requests is 3 requests per second per token. Additionally the entire workspace is limited to 7 requests per second.
Rate limits may change. In the future we may adjust rate limits to balance for demand and reliability.