# List Tax Guard Identifier Qualification Configurations.

BETAList all Tax Guard Identifier Qualification configurations of the current user.

Endpoint: GET /configurations/qualification
Version: 3
Security: apiKey

## Query parameters:

  - `limit` (integer)
    Maximum number of configurations to return. Used for pagination.
    Example: "100"

  - `startAfter` (string)
    ID of the last configuration returned in the previous request. Used for pagination.
    Example: "5712566172571652"

  - `defaultConfiguration` (boolean)
    Limit search to configurations with provided default flag value. If left empty, all configurations will be returned.
    Example: true

  - `clientId` (string)
    API Key ID or Client ID. When present returns only configurations assigned to the given API key.
    Example: "12345678-1234-5678-1234-567812345678"

## Response 200 fields (application/json):

  - `startAfter` (string)
    The ID which is used to read the page.
    Example: "5712566172571652"

  - `nextStartAfter` (string)
    Provides a value to be used as a startAfter in next page request.
    Example: "5712566172571652"

  - `total` (integer)
    Total number of items which can be paged.
    Example: "67"

  - `values` (array)
    List of configurations.

  - `values.name` (string)
    Display name for a configuration.
    Example: "Client configuration."

  - `values.id` (string)
    Uniquely identifies a configuration.
    Example: "c074b9f3-abf0-4f8e-9a20-74deb6cfa2a4"

  - `values.createdAt` (string)
    Date of creation (ISO 8601-compliant).
    Example: "2025-10-07T05:40:33Z"

  - `values.modifiedAt` (string)
    Date of modification (ISO 8601-compliant).
    Example: "2025-10-07T05:40:33Z"

  - `values.createdBy` (string)
    Creator of a resource.
    Example: "76248934691294444"

## Response 400 fields (application/json):

  - `status` (object)
    Details about status or error of a service

  - `status.code` (integer, required)
    RFC 7231 status code for this error.
    Example: "400"

  - `status.technicalKey` (string, required)
    Technical key describing the status or error
    Example: "OK"

  - `status.details` (array)

  - `status.details.id` (integer)
    9-digit code which is uniquely identifying a message
    Example: 200000004

  - `status.details.message` (string)
    Human-readable message which may also be presented in user interface.
    Example: "Business Partner Name is mandatory."

  - `status.details.technicalKey` (string)
    Technical key for the HTTP status code
    Example: "OK"

  - `status.path` (string)
    Requested path which caused this error.
    Example: "/v2/businesspartners/lookup"

  - `status.timestamp` (string)
    ISO 8601 representation of the timestamp.
    Example: "2025-10-07T05:40:33Z"

## Response 401 fields (application/json):

  - `status` (object)
    Details about status or error of a service

  - `status.code` (integer, required)
    RFC 7231 status code for this error.
    Example: "400"

  - `status.technicalKey` (string, required)
    Technical key describing the status or error
    Example: "OK"

  - `status.details` (array)

  - `status.details.id` (integer)
    9-digit code which is uniquely identifying a message
    Example: 200000004

  - `status.details.message` (string)
    Human-readable message which may also be presented in user interface.
    Example: "Business Partner Name is mandatory."

  - `status.details.technicalKey` (string)
    Technical key for the HTTP status code
    Example: "OK"

  - `status.path` (string)
    Requested path which caused this error.
    Example: "/v2/businesspartners/lookup"

  - `status.timestamp` (string)
    ISO 8601 representation of the timestamp.
    Example: "2025-10-07T05:40:33Z"

## Response 403 fields (application/json):

  - `status` (object)
    Details about status or error of a service

  - `status.code` (integer, required)
    RFC 7231 status code for this error.
    Example: "400"

  - `status.technicalKey` (string, required)
    Technical key describing the status or error
    Example: "OK"

  - `status.details` (array)

  - `status.details.id` (integer)
    9-digit code which is uniquely identifying a message
    Example: 200000004

  - `status.details.message` (string)
    Human-readable message which may also be presented in user interface.
    Example: "Business Partner Name is mandatory."

  - `status.details.technicalKey` (string)
    Technical key for the HTTP status code
    Example: "OK"

  - `status.path` (string)
    Requested path which caused this error.
    Example: "/v2/businesspartners/lookup"

  - `status.timestamp` (string)
    ISO 8601 representation of the timestamp.
    Example: "2025-10-07T05:40:33Z"

## Response 500 fields (application/json):

  - `status` (object)
    Details about status or error of a service

  - `status.code` (integer, required)
    RFC 7231 status code for this error.
    Example: "400"

  - `status.technicalKey` (string, required)
    Technical key describing the status or error
    Example: "OK"

  - `status.details` (array)

  - `status.details.id` (integer)
    9-digit code which is uniquely identifying a message
    Example: 200000004

  - `status.details.message` (string)
    Human-readable message which may also be presented in user interface.
    Example: "Business Partner Name is mandatory."

  - `status.details.technicalKey` (string)
    Technical key for the HTTP status code
    Example: "OK"

  - `status.path` (string)
    Requested path which caused this error.
    Example: "/v2/businesspartners/lookup"

  - `status.timestamp` (string)
    ISO 8601 representation of the timestamp.
    Example: "2025-10-07T05:40:33Z"