Notifications endpoints

Generated from the central API contract. Availability and permissions are checked by the connected service.

GET /v1/notifications

Notifications

Authorization: jobs:read Current resource access and role checks also apply.

MCP: No dedicated tool in the current catalogue; use REST with the required permissions.

HTTP request pattern: replace path/query placeholders and prepare any body from the linked model. Run mutations only for your intended action; session-only endpoints need their application authentication context.

curl --fail-with-body --silent --show-error -X GET \
  -H "Authorization: Bearer $GD_API_KEY" \
  "$GD_API_BASE/v1/notifications"

These are the response shapes declared by OpenAPI. Permission, validation, budget and service errors can also occur; see errors and recovery. An unconstrained JSON response is not a guarantee of undocumented fields.

PUT /v1/notifications/preferences

Preferences

Authorization: jobs:read Current resource access and role checks also apply.

MCP: No dedicated tool in the current catalogue; use REST with the required permissions.

Request body: application/json — Preferences. Required.

HTTP request pattern: replace path/query placeholders and prepare any body from the linked model. Run mutations only for your intended action; session-only endpoints need their application authentication context.

curl --fail-with-body --silent --show-error -X PUT \
  -H "Authorization: Bearer $GD_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @request.json \
  "$GD_API_BASE/v1/notifications/preferences"

These are the response shapes declared by OpenAPI. Permission, validation, budget and service errors can also occur; see errors and recovery. An unconstrained JSON response is not a guarantee of undocumented fields.

POST /v1/notifications/read

Mark Read

Authorization: jobs:read Current resource access and role checks also apply.

MCP: No dedicated tool in the current catalogue; use REST with the required permissions.

Request body: application/json — ReadThrough. Required.

HTTP request pattern: replace path/query placeholders and prepare any body from the linked model. Run mutations only for your intended action; session-only endpoints need their application authentication context.

curl --fail-with-body --silent --show-error -X POST \
  -H "Authorization: Bearer $GD_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @request.json \
  "$GD_API_BASE/v1/notifications/read"

These are the response shapes declared by OpenAPI. Permission, validation, budget and service errors can also occur; see errors and recovery. An unconstrained JSON response is not a guarantee of undocumented fields.