Kape Client SDK API Interfaces
Authentication
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- HTTP: Bearer Auth
- API Key: X-Server-2-Server-Secret
- API Key: X-CLP-Token
- API Key: X-Consumer-Id
There is no authentication required
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
An XV_Access Token which is enabled for 2FA by having the mec value in the amr claim listed
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
An OpenID Access Token
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
An OpenID Access Token which is enabled for 2FA
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
An XV_Access Token
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
A Stargate API Access Token obtained from the /verify-token endpoint
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
Uses the Connection Authorization Token
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | jwt |
CLP Token a which is usually present in the xvnv389t Cookie, in that case also an S2S Token needs to be provided
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
Uses the Dedicated IP Access Token
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | jwt |
Uses the JWT Subscription Receipt Token
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
An S2S Token for communication between internal services provides as an Authorization Bearer token
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
An S2S Token for communication between internal services provided as a header param
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-S2S |
A CLP Token which is usually present in the xvnv389t Cookie and is considered to have 2FA enabled as well
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-CLP-Token |
Unique ID of the Backend Consumer
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-Consumer-Id |
License
No license is granted