POST /v1/oauth/clients
Creates a new OAuth clientId and clientSecret.
Servers
- https://api.au.sumologic.com/api/
- https://api.ca.sumologic.com/api/
- https://api.ch.sumologic.com/api/
- https://api.de.sumologic.com/api/
- https://api.eu.sumologic.com/api/
- https://api.fed.sumologic.com/api/
- https://api.jp.sumologic.com/api/
- https://api.kr.sumologic.com/api/
- https://api.in.sumologic.com/api/
- https://api.sumologic.com/api/
- https://api.us2.sumologic.com/api/
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
scopes[] |
Array | Yes |
Scopes assigned to the client. MCP Server Required Scopes: For full access to all MCP Server tools, the following scopes are required. Each tool lists the scopes it needs.
Alerting
Audit Event Management
Cloud SIEM
Cloud SOAR
Dashboards
Data Management
Data Masking
Entity Management
Logs
Macros
Metrics
Open Analytics
Organizations
Reliability Management
Security
Threat Intelligence
Usage Management
User Management
|
type |
String | Yes |
Type of the object model. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.