feat: continue to work on site
This commit is contained in:
@@ -1,3 +1,9 @@
|
||||
# Authentication
|
||||
|
||||
This is the copy for the authentication page.
|
||||
The Onpsring API uses API keys to authenticate requests. You can view and manage your API keys your instance.
|
||||
|
||||
The API key needs to be provided in every request. This is done by adding the `X-ApiKey` header to the request.
|
||||
|
||||
API Keys are specific to an instance. If you are using the API to access data from multiple instances, you will need to create an API key for each instance. The API key must be in an `Enabled` status and it must be assigned a role that will control the permissions for requests made by the API key. The role assigned should be in an `Active` status.
|
||||
|
||||
If the role assigned to the API key does not have sufficient permissions to perform the requested action, an error will be returned. Onspring administrators may configure roles for API keys just as they would any other role in Onspring. However each API key can have only one assigned role.
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
# Example
|
||||
# X-ApiKey Header
|
||||
|
||||
This is an example for the authentication page.
|
||||
{% code heading="X-API KEY" language="text" %}
|
||||
|
||||
```text
|
||||
X-ApiKey: 000000ffffff000000ffffff/00000000-ffff-0000-ffff-000000000000
|
||||
```
|
||||
|
||||
{% /code %}
|
||||
|
||||
@@ -2,4 +2,4 @@
|
||||
|
||||
The Onspring API is organized around REST. It enables external programs to retrieve, save, and delete data within your Onspring instance. The Onspring API implements version 3 of the Open API Specification (OAS).
|
||||
|
||||
The Onspring API does support bulk operation for some, but not all endpoints. Bulk operations are not supported for endpoints that create, update, or delete data. The one exception is the bulk delete endpoint, which is used to delete multiple records at once.
|
||||
The Onspring API does support bulk operation for some, but not all endpoints. Bulk operations are not supported for endpoints that create, update, or delete resources. The one exception is the batch delete endpoint for records, which is used to delete multiple records at once.
|
||||
|
||||
Reference in New Issue
Block a user