---
title: "Get token information"
method: GET
path: "/v1/cards/{cardId}/network-tokens/{tokenId}"
tags: ["Token lifecycle"]
---

# Get token information

`GET /v1/cards/{cardId}/network-tokens/{tokenId}`

Gets token information given a card ID and token ID in the path.

**Notes**: 
  * This is a PCI endpoint, use the https://gw-pci.pismolabs.io/cards-tokenization environment.
  * This endpoint takes an account token - an access token encoded with a Pismo account ID.

## Response `200`

- TokenInfoCardTokenResponse
  - `token` TokenObject
    - `key` object
      - `token_ref` string — Identifies the token on the network.
      - `pan_ref` string — PAN reference - identifies the card on the network.
      - `payment_network` 'vts' | 'mdes' — Payment network - `vts` (VISA) or `mdes` (Mastercard)
  - `token_id` string — Pismo token ID
  - `card_id` integer — Enrolled card ID
  - `wallet_id` string — Wallet ID. Identifies the wallet (Samsung Pay, Google Pay, and so on) on the network.
  - `account_id` integer — Account ID
  - `program_id` number — Pismo program ID.
  - `org_id` string — Organization ID
  - `payment_app_instance_id` string — Payment app instance ID
  - `tracking_id` string — Customer created tracking ID. Must consist of alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and colons (:), with a length from 1 to 128. The Pismo platform uses this field to implement idempotency and prevent duplicates.
  - `status` 'ACTIVE' | 'SUSPENDED' | 'DEACTIVATED' | 'INACTIVE' — Token status
  - `network_data` NetworkDetails — Dynamic data that varies according to network

## Other responses

- `400` — Bad request
- `401` — Access token is missing or invalid
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)