fix: add basePath to config
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# Authentication
|
||||
# Authentication {% #authentication %}
|
||||
|
||||
The Onpsring API uses API keys to authenticate requests. You can view and manage your API keys from within your instance.
|
||||
|
||||
The API key needs to be provided in every request. This is done by adding the `X-ApiKey` header to the request. 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.
|
||||
An API key needs to be provided with every request. This is done by adding the `X-ApiKey` header to the request. The API key provided should be in an `Enabled` status and it should be assigned a role that has the proper permissions for the request made by the API key. The role assigned should also be in an `Active` status.
|
||||
|
||||
If the role assigned to the API key does not have sufficient permissions to perform the requested action or is in n `Inactive` status, 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,4 +1,4 @@
|
||||
# Introduction {% .articleTitle %}
|
||||
# Introduction {% #introduction %}
|
||||
|
||||
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).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user