Skip to main content
POST
Get datasource detail

Restrictions

Credential fields

The info / create / update responses never return credentials in cleartext. password, basic_auth_password, api_key, service_token, access_key_secret, tls_key, tls_key_pwd and their siblings come back as the placeholder ******; a field that was never configured still comes back as an empty string. sls.access_key_id is an identifier rather than a credential and is returned as-is. On update, submitting ****** unchanged means keep the stored value, and an empty string is treated the same way. To rotate a credential, submit the new value directly. On create there is no stored value to keep — submitting a ****** copied from another response stores the literal string ******, and the data source will fail to connect.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Request with a single numeric ID.

id
integer<uint64>
required

Resource ID.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

A monitoring datasource.