API Authentication
To securely access the API, the system supports two types of authentication methods: CookieAuth and BearerAuth. These methods ensure that only authorized users can interact with the API endpoints.
1. CookieAuth
CookieAuth is a simple method of authentication that requires a fixed token. This token is passed in the API request to authenticate the client. The fixed token for CookieAuth is as follows:
client.id=Q5VZ97naQhyLIH0Vz4MSXvzbMyCYTjPwz+1hVJ643pA=
When making requests, this token should be included in the cookies section of the request header. This method is static and does not change over time.
2. BearerAuth
BearerAuth uses a Personal Access Token (PAT) for authentication. This token is dynamic and must be generated by the user via the Motadata AIOps UI.
Once generated, the token is used in the Authorization header as a Bearer token.
This API provides endpoints for retrieving various types of monitor information, including details, instances, status, severity, and last poll information. It also offers performance metrics data based on widget IDs.
Authentication
| Security Scheme Type: | apiKey |
|---|---|
| Header parameter name: | cookie |
| Security Scheme Type: | http |
|---|---|
| HTTP Authorization Scheme: | bearer |
| Bearer format: | JWT |