GRgrepr
Datadog Integration

Preview authorization scopes for keys not yet saved to any integration

Probes Datadog with the supplied site and keys and reports each authorization scope. For the create form, where there is no integration to take keys from, so every field is required. Nothing is written and nothing is stored.

post/v1/integrations/datadog/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)

Request body

apiKeystring required

API key to authenticate the probes with

appKeystring required

Application key to check

sitestring required

The Datadog site to probe

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.