Retrieve an endpoint by ID
GEThttps://api.logz.io/v1/endpoints/:id
Returns a JSON object representing a notification endpoint configured in the account. Please ensure to change the region in the URL to match your account's region.
Request
Path Parameters
id int32required
ID of the notification endpoint
Responses
- 200
successful operation
- application/json
- Schema
- Example (from schema)
Schema
endpointType string
Possible values: [BigPanda
, Slack
, Datadog
, Custom
, PagerDuty
, VictorOps
, Opsgenie
, ServiceNow
, Microsoft Teams
]
The notification endpoint type that will receive alert messages
id int32
ID of the notification endpoint
title string
Name of the endpoint
description string
Detailed description of the endpoint
{
"endpointType": "Slack",
"id": 88,
"title": "Slack",
"description": "Endpoint for sending alerts to Slack"
}
Authorization: X-API-TOKEN
name: X-API-TOKENtype: apiKeydescription: You can manage your API tokens from the [Logz.io API tokens](https://app.logz.io/#/dashboard/settings/manage-tokens/api) page. API tokens are account-specific. You will need to be logged into the relevant Log Management or SIEM account to view the API tokens associated with it. To manage your API tokens, log into the relevant account in your Logz.io platform, click the gear in the top-right menu, and select [**Tools > Manage tokens > API tokens**](https://app.logz.io/#/dashboard/settings/manage-tokens/api). It's important to keep your tokens secure. API tokens carry privileges to make changes to users and accounts, so if you believe an API token has been compromised, delete it, and replace it with a new token in your integrations.in: header
- curl
- python
- go
- nodejs
- ruby
- csharp
- php
- java
- powershell
- CURL
curl -L -X GET 'https://api.logz.io/v1/endpoints/:id' \
-H 'Accept: application/json' \
-H 'X-API-TOKEN: <API_KEY_VALUE>'