---
title: "Get a token request result"
method: GET
path: "/token-requests/{tokenRequestId}/result"
tags: ["Requests - for Payments v1 or AIS"]
---

# Get a token request result

`GET /token-requests/{tokenRequestId}/result`

The `GET /token-requests/{tokenRequestId}/result` endpoint checks whether a token request result is available. This endpoint will return a `PENDING` status while the result is not available. The status will become `PROCESSED` once the result is available. If the request is rejected by the bank, the status will become `REJECTED`. The status will become `EXPIRED` if the request is not processed or rejected before the token request expiration.

## Path parameters

- `tokenRequestId` string, required

## Response `200`

Successful response

- union
  - object — Contains the details of the transfer response.
    - `transferId` string — The id of the transfer sent in the `POST /transfers` response and/or included in a respective `GET /transfers` response. This is populated for transfer token requests only, it is present if a transfer resource is created.
    - `tokenId` string — Identifies a unique authorization token for a transfer, standing order or account information access.
    - `signature` Signature — Contains information about the signing party. This is only present if a `tokenId` is present. It can be used to validate that the provided `tokenId` corresponds to the token request (this is needed for the Hosted Pages flows only).
      - `keyId` string — The id of the public key used to verify the signature. This is only present if a `tokenId` is present. It can be used to validate that the provided `tokenId` corresponds to the token request (this is needed for Hosted Pages flows only).
      - `memberId` string — The Token.io member id of the signing member.
      - `signature` string — The Base64url-encoded ciphertext signature.
    - `status` 'PENDING' | 'PROCESSED' | 'REJECTED' | 'EXPIRED', required — The current result of the token request. This field is always populated. <ul><li><b>PENDING</b> - consent is not authorized by the user.</li> <li><b>PROCESSED</b> - consent was successfully authorized by the user.</li><li><b>REJECTED</b> - consent has been rejected (the reason usually can be found in the `statusReasonInformation` field).</li><li><b>EXPIRED</b> - the token request has expired and cannot be used anymore (consent can be in any state - authorized/not authorized yet/rejected - at this point).</li></ul>
    - `statusReasonInformation` string — A human-readable description of the reason for the reported status, which may include a message from the bank, This value should not exceed 256 characters in length.
    - `bankId` string — The bank identifier, identical to the `id` in the repsonse to `GET /banks`.
  - object — Contains the details of the standing order response.
    - `standingOrderSubmissionId` string — The unique id of the standing order submission. This is populated for standing order token requests only, it is present if a standing order submission resource is created
    - `tokenId` string — Identifies a unique authorization token for a transfer, standing order or account information access.
    - `signature` Signature — Contains information about the signing party. This is only present if a `tokenId` is present. It can be used to validate that the provided `tokenId` corresponds to the token request (this is needed for the Hosted Pages flows only).
      - `keyId` string — The id of the public key used to verify the signature. This is only present if a `tokenId` is present. It can be used to validate that the provided `tokenId` corresponds to the token request (this is needed for Hosted Pages flows only).
      - `memberId` string — The Token.io member id of the signing member.
      - `signature` string — The Base64url-encoded ciphertext signature.
    - `status` 'PENDING' | 'PROCESSED' | 'REJECTED' | 'EXPIRED', required — The current result of the token request. This field is always populated. <ul><li><b>PENDING</b> - consent is not authorized by the user.</li> <li><b>PROCESSED</b> - consent was successfully authorized by the user.</li><li><b>REJECTED</b> - consent has been rejected (the reason usually can be found in the `statusReasonInformation` field).</li><li><b>EXPIRED</b> - the token request has expired and cannot be used anymore (consent can be in any state - authorized/not authorized yet/rejected - at this point).</li></ul>
    - `statusReasonInformation` string — A human-readable description of the reason for the reported status, which may include a message from the bank, This value should not exceed 256 characters in length.
    - `bankId` string — The bank identifier, identical to the `id` in the repsonse to `GET /banks`.
  - object — Contains the details of the access request response.
    - `tokenId` string — Identifies a unique authorization token for a transfer, standing order or account information access.
    - `signature` Signature — Contains information about the signing party. This is only present if a `tokenId` is present. It can be used to validate that the provided `tokenId` corresponds to the token request (this is needed for the Hosted Pages flows only).
      - `keyId` string — The id of the public key used to verify the signature. This is only present if a `tokenId` is present. It can be used to validate that the provided `tokenId` corresponds to the token request (this is needed for Hosted Pages flows only).
      - `memberId` string — The Token.io member id of the signing member.
      - `signature` string — The Base64url-encoded ciphertext signature.
    - `status` 'PENDING' | 'PROCESSED' | 'REJECTED' | 'EXPIRED', required — The current result of the token request. This field is always populated. <ul><li><b>PENDING</b> - consent is not authorized by the user.</li> <li><b>PROCESSED</b> - consent was successfully authorized by the user.</li><li><b>REJECTED</b> - consent has been rejected (the reason usually can be found in the `statusReasonInformation` field).</li><li><b>EXPIRED</b> - the token request has expired and cannot be used anymore (consent can be in any state - authorized/not authorized yet/rejected - at this point).</li></ul>
    - `statusReasonInformation` string — A human-readable description of the reason for the reported status, which may include a message from the bank, This value should not exceed 256 characters in length.
    - `bankId` string — The bank identifier, identical to the `id` in the repsonse to `GET /banks`.

## Other responses

- `400` — The client specified an invalid argument
- `401` — The authorization information is missing or invalid
- `403` — Permission to access this endpoint is denied
- `404` — The requested entity, such as a token request, was not found
- `429` — Too many requests
- `500` — An unexpected or internal server error
- `501` — The operation was not implemented
- `503` — Service is unavailable
- `504` — Gateway has timed out

---

[API](https://skmtc.net/token/apis/token-io-s-open-banking-api-for-tpps.md) · [All operations](https://skmtc.net/token/apis/token-io-s-open-banking-api-for-tpps/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/token/token-io-s-open-banking-api-for-tpps/versions/5e8d6d2c24a1/schema)
