> For the complete documentation index, see [llms.txt](https://docs.zebec.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zebec.io/developer-docs/partner-api/cards.md).

# Cards

The Cards endpoints let a partner read card metadata and transaction history for users under their partner scope.

## Endpoints

### Get card metadata

```http
GET /partner/v1/cards
Authorization: Bearer <accessToken>
```

Returns card summary metadata. PAN and CVV are **not** included in the response.

### List card transactions

```http
GET /partner/v1/cards/transactions
Authorization: Bearer <accessToken>
```

Returns a list of card transactions.

## Required scope

Both endpoints require the `cards:read` scope on your partner API key.

## User resolution

The user is derived from the Bearer token returned by `POST /partner/v1/auth/otp/verify`. Do not supply a user identifier in the request path or body.

## Common use cases

* Display a user's card status and balance inside your app.
* Show recent card activity.
* Poll whether a top-up has landed before showing updated balances.

For full schemas and example responses, see the [Swagger UI](https://dev-super.api.zebec.io/api/partner).