# Get a callback configuration by project id.

Returns the callback configuration for the specified project. The HMAC secret is masked —
only the last 6 characters are visible. To retrieve the full secret, rotate it using
POST /v1/projects/{projectId}/callbackConfig/rotate or set a new one via PATCH.

Endpoint: GET /v1/projects/{projectId}/callbackConfig
Version: 1.0.0
Security: OAuth2

## Path parameters:

  - `projectId` (string, required)
    Customer's project id

## Response 200 fields (application/json):

  - `projectId` (string)
    Project ID this callback configuration belongs to.

  - `hmacSecretMask` (string)
    Masked representation of the HMAC secret. Only the last 6 characters are visible
(e.g. ••••••1b11ee). To see the full secret, rotate it via
POST /v1/projects/{projectId}/callbackConfig/rotate or set a new one via PATCH.

## Response 401 fields (application/problem+json):

  - `type` (string, required)
    A URI reference that identifies the problem type. This URI reference should provide a human-readable explanation of the problem type when dereferenced.

  - `title` (string, required)
    A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for localization purposes.

  - `body` (object) — one of:
    - variant 1:
      - `errors` (array)
        Detailed information about the error. This field can contain multiple error details to provide more context about the error that occurred.
      - `errors.pointer` (string)
        JSON pointer to the field that caused the error, following RFC 6901.
      - `errors.detail` (string)
        A human-readable explanation specific to this occurrence of the problem. Like title, this field is not intended for end users, but rather for developers to understand the details of the error that occurred.
    - variant 2:
      - `detail` (string)
        A human-readable explanation of the error that occurred.