From Bright Pattern Documentation
Jump to: navigation, search
(Redirected page to Api)
m (Reverted edits by Elizabeth (talk) to last revision by Tracy)
 
Line 1: Line 1:
#REDIRECT [[Api]]
+
<translate>= General Information=
 +
RESTful-style API is used. The HTTP POST method is used for all requests to insert or update information, while the HTTP GET method is used to retrieve information. Request and Response bodies are encoded using JSON.
 +
 
 +
This specification describes only additional or different meanings of standard HTTP response codes. For more information, see  [http://www.ietf.org/rfc/rfc2616.txt RFC 2616, Section 10].
 +
 
 +
== URLs ==
 +
The request URL contains information about the required action and the object name. The base part of the URL is '''http[s]://<host>:<port>/configapi/v2'''
 +
 
 +
== Request Body ==
 +
The request body carries the object to be inserted or unique ID fields of the object to be queried.
 +
 
 +
== Tenant ID ==
 +
In a multi-tenant deployment, the tenant ID is derived from authentication login information. For more information, see the [[list-management-api-specification/SecurityandAuthentication|Security and Authentication]] section of this specification.
 +
 
 +
 
 +
 
 +
 
 +
 
 +
</translate>

Latest revision as of 16:33, 29 July 2020

• 5.19 • 5.2 • 5.3 • 5.8

General Information

RESTful-style API is used. The HTTP POST method is used for all requests to insert or update information, while the HTTP GET method is used to retrieve information. Request and Response bodies are encoded using JSON.

This specification describes only additional or different meanings of standard HTTP response codes. For more information, see RFC 2616, Section 10.

URLs

The request URL contains information about the required action and the object name. The base part of the URL is http[s]://<host>:<port>/configapi/v2

Request Body

The request body carries the object to be inserted or unique ID fields of the object to be queried.

Tenant ID

In a multi-tenant deployment, the tenant ID is derived from authentication login information. For more information, see the Security and Authentication section of this specification.



< Previous | Next >