---
title: "Retrieve a card request"
method: GET
path: "/v2/card-requests/{cardRequestId}"
---

# Retrieve a card request

`GET /v2/card-requests/{cardRequestId}`

## Request

- Base URL: `https://api.slash.com`
- URL: `https://api.slash.com/v2/card-requests/{cardRequestId}`
- Auth: API key in header `X-API-Key`

## Path parameters

- `cardRequestId` string, required

## Response `200`

The card request.

- CardRequest: A request for a card that an approver decides on in Slash.
  - `id` string, required: Card request id with the `card_request_` prefix.
  - `status` 'pending' | 'approved' | 'rejected' | 'canceled' | 'expired', required: `approved` requests issue their card shortly after; `cardId` is set once it exists.
  - `type` 'virtual' | 'physical', required
  - `name` string, required
  - `accountId` string, required
  - `virtualAccountId` string
  - `cardGroupId` string
  - `requesterUserId` string, required
  - `requestedLimit` CardRequestLimit
    - `amount` UsdMoney, required: A positive USD amount expressed in cents.
      - `amount` integer, required: Amount in cents. For example, `1250` represents USD 12.50.
      - `currency` 'USD', required
    - `period` 'daily' | 'weekly' | 'monthly' | 'yearly' | 'lifetime', required
  - `memo` string
  - `cardId` string: The card issued for the request.
  - `createdAt` string, date-time, required
  - `resolvedAt` string, date-time

## Other responses

- `400`: - `invalid_request (request shape)` — The body, query, or headers failed validation, or a required header is missing. `details` has one entry per failing location, keyed by JSON pointer or header name.
- `401`: - `unauthorized` — API key authentication is missing or invalid.
- `403`: - `forbidden (legal entity)` — The credential is not permitted to act for the selected legal entity. - `not_available` — Public API v2 is not yet available. Use [Public API v1](https://docs.slash.com/introduction) in the meantime. - `user_api_key_required` — The API key is scoped to a legal entity rather than a user. Every v2 request needs a user API key, created under Settings → API keys in the Slash dashboard, together with the `x-legal-entity` header.
- `404`: - `not_found` — No resource matches the identifier. When the identifier is a field of the request, `details` names that `field` and the `id` it received.
- `429`: The request exceeded the applicable rate limit. The response body is plain text, not the error object; clients must not depend on its wording.
- `500`: - `internal` — Slash could not complete the request. Quote `referenceId` when contacting Slash support.

## Changes

- **2026-10-16** `8b5d371ffeea`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/slashfi/apis/slash-public-api/changes/v2/card-requests/:cardRequestId/get.md)

---

[API](https://skmtc.dev/slashfi/apis/slash-public-api.md) - [All operations](https://skmtc.dev/slashfi/apis/slash-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/slashfi/apis/slash-public-api/revisions/eaed2d63c9e2?raw)