Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Developer reference
- Overview of the REST API
- Connect to the REST API
- Authentication endpoint service
- Single record APIs
- Record bulk update and collection APIs
- REST API queries
- REST API collection query protocol
- Analytics REST API
- Manage Persons API
- BI Integration API
- Case Exchange REST API
- Encryption domain API
- Comments API
- REST API use-case scenario - import REST API
How to connect to the REST API
To connect and use the REST API, you must do all of the following:
-
Establish a user (logon) session.
Using SSO, each session must start with a call to the authentication endpoint:
-
Send a POST request to
/auth/authentication-endpoint/authenticate/login
if you are using an integration user.Send a POST request to
/auth/authentication-endpoint/authenticate/login?TENANTID=XXX
if you are using an account user.Note Only integration users and account users with DB authentication type can use this API.
-
The body of the request should be:
{ "Login":"%user login name%", "Password": "%user login password%" }
-
From the response, note the value of the authentication token.
-
Ensure each subsequent request includes a cookie header:
LWSSO_COOKIE_KEY=%token%
In the header, replace
%token%
with the value of the authentication token.
For more information, see Authentication endpoint service.
-
-
Include in each request, the tenant ID.
In addition to the basic URL and record parameters, you must append the tenant ID.
For example:
-
Basic URL format: https://../incidents?filter=...
-
With tenant ID appended: https://../incidents?filter=...&TENANTID=123
-
-
Exclude from each request, the XSRF token.
The best practice is to delete or ignore the XSRF token. If you do not do this, you must do either of the following:
-
Provide a
User-Agent HTTP
header with the valueApache-HttpClient/<version>
. The value must contain a version number, for exampleApache-HttpClient/4.1
. -
Send a token as an HTTP header named X-XSRF-TOKEN with the value taken from the latest XSRF-TOKEN cookie. (This is normal browser behavior.)
-
Related topics