GRgrepr
Datadog Integration

Preview authorization scopes for unsaved changes to an integration

Probes Datadog with the integration's stored keys, overridden by whatever the body supplies, and reports each authorization scope. Nothing is written. An omitted field means "use what is stored", so an empty body reports what the stored key can do right now. A scope whose probe does not complete is reported UNKNOWN rather than as a permission the user has to grant.

post/v1/integrations/datadog/{id}/app-key/scopes/preview

Request

  • Base URL
    https://docs.grepr.ai (the document declares no server; this is the origin it was published from)
  • Auth
    • API key in header GREPR-API-KEY
    • or OpenID Connect (https://grepr-prod.us.auth0.com/.well-known/openid-configuration)

Path parameters

idstring required

Request body

apiKeystring

API key to probe with instead of the stored one

appKeystring

Application key to check instead of the stored one

sitestring

Site to probe instead of the stored one

Example request

{
  "site": "datadoghq.com"
}

Response

Scopes checked successfully

requiredboolean

Whether Grepr rejects an application key without this scope

scopestring

The Datadog authorization scope identifier

status'GRANTED' | 'DENIED' | 'UNKNOWN'

Whether the application key was found to hold a scope, or could not be checked

Example response

[
  {
    "scope": "monitors_read"
  }
]

Changes

No recorded changes to this operation across all 1 revision of this API.