API credentials allow secure access to the appbase.io APIs. They offer a variety of rules to granularly control access to the APIs.
When creating an app in appbase.io, you have access to two types of API Credentials.
Read-only API key offers access to read based endpoints of the API (you can get a document, search for documents, but not create or update a document) while an
Admin API key offers access to both read an write based endpoints (you can create, update and even delete documents).
How are the credentials authenticated?
An appbase.io credential consists of a
username:password format and are authenticated using the HTTP Basic Authentication method.
When making the API request, the credentials are passed using the
Authorization header with a base64 encoded value of the actual credentials.
If you are using the
ReactiveSearch libraries, you don’t have to worry about the base64 conversion, these libraries do that for you. If you are using a server-side language, then you will have to add the
Authorization header with the correct base64 encoded value of the API key. You can read more about it in the REST API Reference.
Adding and Updating Credentials
You can also create a new credentials or modify the existing defaults. When doing so, you can set one or more of the following restrictions.
Let’s go over each kind of authorization constraint you can apply to a key:
Key Type determines the main type of operations this key will be responsible for. There are three key types:
- Read-only key,
- Write-only key,
- Admin key (aka read + write).
ACLs determine granularly what type of actions are allowed for the API key in addition to the broad Key Type.
- Index (index) allows indexing and update actions.
- Get (get) allows retrieving documents and data mappings.
- Search (search) allows searching for documents in an app.
- Settings (settings) allow access to the settings endpoints.
- Stream (stream) allows access to the streaming endpoints for realtime data updates.
- Bulk (bulk) allows access to the bulk endpoints.
- Delete (delete) allows access to all the deletion related endpoints.
- Analytics (analytics) allows access to the Analytics APIs programmatically. [only available for
Security constraints allow authorizing API access based on the selected HTTP Referers and IP Source values.
- HTTP Referers allow adding one or more URIs that are whitelisted for accessing the API endpoints. By default, all referers are allowed access to the APIs.
HTTP Referers are passed by the browsers using the
Refererheader by the browsers. They are a good mechanism to prevent unauthorized access from browser environments but can be easily spoofed by a HTTP client running outside of a browser environment.
We recommend using HTTP Referers as an additional safeguard to your security model, but not as the only safeguard.
- IP Sources allow specifying whitelisted IP ranges (in CIDR format) that can access the APIs. By default, all IPs are allowed access to the APIs.
We don’t support specifying a blacklist of IP ranges. You can specify a maximum of
100HTTP Referers and a maximum of
Fields filtering allows setting restrictions on fields that are returned when performing a search action.
Include fields offers a dropdown view to select one or more fields that should be included in the response.
Exclude fields offers a dropdown view to remove one or more fields that should be excluded from the response.
Rate Limit by IP allows setting a per hour rate-limit for every unique IP that is used for making an API call with this API credential. By default, no rate limits are set. Setting a rate-limit prevents abuse of data for scraping or denial of service purposes.
- Time to Live (TTL) allows setting an optional expiration time till this API credential should be effective. You can create ephemeral keys that are only effective for minutes, hours, days or weeks to limit the surface area of keys being compromised. By default, an API credential lives forever.