---
title: "Get ThreeDS Operations by ThreeDS ID"
method: GET
path: "/payment/threeds/{threeDSId}/operations"
tags: ["ThreeDS"]
---

# Get ThreeDS Operations by ThreeDS ID

`GET /payment/threeds/{threeDSId}/operations`

Find ThreeDS operations from a given `threeDSId`.

## Path parameters

- `threeDSId` string, uuid, required

## Query parameters

- `includeLogs` boolean

## Response `200`

Success.

- object
  - `results` object[]
    - `id` string, uuid, required — Unique identifier of the ThreeDS Operation in Payrails.
    - `threeDSId` string, uuid — Unique identifier of the ThreeDS authentication that this Operation belongs to in Payrails.
    - `createdAt` string, date-time, required — Exact date and time when the ThreeDS Operation was created in Payrails. Possibly differs slightly from the date in the ThreeDS provider.
    - `updatedAt` string, date-time, required — Exact date and time when the ThreeDS Operation was updated in Payrails. Possibly differs slightly from the date in the ThreeDS provider.
    - `result` 'Successful' | 'ChallengeRequired' | 'Pending' | 'Failed' | 'Unknown' | 'Timeout' | 'ProviderTimeout' | 'UnexpectedProviderResponse' | 'ProviderUnknownError' | 'ProviderConnectionError' | 'DuplicateOperation' | 'ValidationError' | 'ParamsError' | 'ProviderConfigError' | 'InvalidSignature' | 'InternalServerError' | 'AuthenticationError' | 'LimitExceeded', required — Operation Result that was executed in the Provider.
    - `providerReference` string — Unique identifier of the ThreeDS Operation in an external system. Some PSPs provide a specific ID for each update in the ThreeDS, but most of them use the same as the original ThreeDS.
    - `reason` string — Reason why the operation was done.
    - `errorDetails` string — Error details from the Payrails or the provider in case of error.
    - `providerExecutedAt` string, date-time — Exact date and time when the ThreeDS Operation was executed in the ThreeDS provider.
    - `resultProviderDetails` object — Specific details of the provider response that mapped to the specific Payrails result.
      - `message` string — Message from the provider response.
      - `additionalData` object — Additional data sent in the provider response.
    - `actionId` string, uuid — Identifier of the action in the Workflow that led to this ThreeDS authentication.
    - `workspaceId` string, uuid, required — Workspace ID that the workflow configuration belongs to.
    - `operationLogs` object[] — List of operation logs associated with this operation.
      - `id` string, uuid, required — Unique identifier of the Operation Log in Payrails.
      - `createdAt` string, date-time, required — Exact date and time when the Operation Log was created in Payrails. Possibly differs slightly from the date in the provider.
      - `operationId` string, uuid, required — Unique identifier of the Operation that this Log belongs to in Payrails.
      - `input` string, required — Original request object sent to the Provider.
      - `output` string, required — Original response object received from the Provider.
      - `workspaceId` string, uuid — Workspace ID that the workflow configuration belongs to.
      - `providerLatency` string — Latency of the operation on the provider side.
      - `totalLatency` string — Total latency of the operation.
    - `providerLatency` string — Latency of the operation on the provider side.
    - `totalLatency` string — Total latency of the operation.

## Other responses

- `400` — Bad Request.
- `401` — Unauthorized.
- `403` — Insufficient Scope.
- `404` — Not Found.
- `429` — Too Many Requests.

---

[API](https://skmtc.net/payrails/apis/payrails-api-reference.md) · [All operations](https://skmtc.net/payrails/apis/payrails-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/payrails/payrails-api-reference/versions/9dd2f0158582/schema)