# List TMS credentials for an operator

Retrieve all TMS credentials associated with a specific operator.

Endpoint: GET /operators/{operatorId}/tms-credentials
Version: 1.0.0
Security: Live

## Path parameters:

  - `operatorId` (integer, required)
    The unique identifier of the operator
    Example: 1

## Response 200 fields (application/json):

  - `operatorId` (integer, required)
    The unique identifier of the operator
    Example: 1

  - `tmsId` (integer, required)
    The unique identifier of the TMS
    Example: 1

  - `tmsName` (string, required)
    The name of the TMS
    Example: "Collins"

  - `tmsSlug` (string, required)
    The slug identifier of the TMS
    Example: "CO"

  - `active` (boolean, required)
    Whether this TMS credentials is currently active
    Example: true

  - `createdAt` (string)
    Timestamp when the connection was created
    Example: "2025-01-15T10:30:00Z"

  - `updatedAt` (string)
    Timestamp when the connection was last updated
    Example: "2025-02-10T14:20:00Z"

## Response 404 fields (application/json):

  - `type` (string)
    A URI reference [rfc9457] that identifies the problem type. This specification encourages that, when dereferenced, it provides human-readable documentation for the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member is not present, its value is assumed to be "about:blank".

  - `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 purposes of localization.

  - `status` (integer, required)
    The HTTP status code [rfc9457, Section 3.1.12] generated by the origin server for this occurrence of the problem.

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.

  - `code` (string, required)
    Error code in the format RESOURCE-X-NNN where X is R (retryable) or N (non-retryable). See ErrorCatalog.md for all error codes.
    Example: "VALID-N-001"

  - `isRetryable` (boolean, required)
    Indicates whether the error is retryable. If true, the request may succeed if retried. If false, the request will fail again with the same input.

  - `traceId` (string)
    Request trace identifier for debugging and correlation purposes.
    Example: "0HNJ2BG2TU3BU:00000001"

  - `errors` (object,null)
    Validation errors dictionary mapping field names to arrays of error messages. Only present for validation errors (VALID-N-001).
    Example: {"Date":["Availability date cannot be in the past."],"EndTime":["EndTime must be after StartTime."]}

## Response 429 fields (application/json):

  - `type` (string)
    A URI reference [rfc9457] that identifies the problem type. This specification encourages that, when dereferenced, it provides human-readable documentation for the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member is not present, its value is assumed to be "about:blank".

  - `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 purposes of localization.

  - `status` (integer, required)
    The HTTP status code [rfc9457, Section 3.1.12] generated by the origin server for this occurrence of the problem.

  - `detail` (string)
    A human-readable explanation specific to this occurrence of the problem.

  - `code` (string, required)
    Error code in the format RESOURCE-X-NNN where X is R (retryable) or N (non-retryable). See ErrorCatalog.md for all error codes.
    Example: "VALID-N-001"

  - `isRetryable` (boolean, required)
    Indicates whether the error is retryable. If true, the request may succeed if retried. If false, the request will fail again with the same input.

  - `traceId` (string)
    Request trace identifier for debugging and correlation purposes.
    Example: "0HNJ2BG2TU3BU:00000001"

  - `errors` (object,null)
    Validation errors dictionary mapping field names to arrays of error messages. Only present for validation errors (VALID-N-001).
    Example: {"Date":["Availability date cannot be in the past."],"EndTime":["EndTime must be after StartTime."]}