> ## Documentation Index
> Fetch the complete documentation index at: https://direct-api.reap.global/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> New endpoints, new scopes and behavior changes in the Business Account API, newest first.

Every change here is backwards compatible unless an entry says otherwise.
Breaking changes ship under a new dated version, described in
[Versioning](https://direct-api.reap.global/api-reference/versioning.md).

## November 4, 2026

### Card list filters and sorting

[List cards](https://direct-api.reap.global/api-reference/cards/list-cards.md) now supports comma-separated public
status filters, creation and last update ranges, and sorting by `id`, `createdAt`
or `updatedAt`. Use `createdAt[gte]` / `createdAt[lt]` or `updatedAt[gte]` /
`updatedAt[lt]` with UTC dates or timezone-qualified timestamps. Lower bounds are
inclusive and upper bounds are exclusive. Timestamp sorts use card ID to break
ties; requests without `sort` keep their existing ordering.

### Restrict cards to transaction categories

`PUT /cards/{cardId}/restriction` now accepts `category`, so a card can only be
used for charges in the transaction categories you list. Use the `code` that
`GET /cards/transaction-categories` now returns for each category. Card
responses include `restriction.category`. A `PUT` that leaves out `category`
removes the card's category restriction. Category restrictions must be enabled
for your business.

The request body of `PUT /cards/{cardId}/restriction` now accepts only `time`
and `category`. Any other field returns a 400 validation error. Reap ignored
these fields before, so a misspelled field such as `tiem` was treated as
missing and removed the card's time window. Such a request now fails and
changes nothing.

The [MCP server](https://direct-api.reap.global/getting-started/mcp-server.md) has a new `update_card_restriction`
tool, and `preview_card_changes` has a new `update_restriction` action. MCP tools
that change a card's usage hours or categories now read the card first, so they
keep the part you leave out. They now need the `cards:read` scope as well as
`cards:write`. This includes `update_card_usage_hours` and the
`update_usage_hours` action, so a key with only `cards:write` can no longer
change usage hours until you add `cards:read`.

* [Spend controls](https://direct-api.reap.global/concepts/spend-controls.md) explains the restriction rules
* [Update restriction](https://direct-api.reap.global/api-reference/cards/update-card-usage-restriction.md)

### Card category is checked when you create a card

`POST /cards` now checks `category`. A `category` that is not a UUID returns a
400 validation error. A UUID that is not the `id` of a card category from
`GET /cards/categories` returns 422 `CARD_CATEGORY_NOT_FOUND`, and so does the
`id` of a transaction category from `GET /cards/transaction-categories`. Reap
accepted these requests before, so a request that worked until now can fail.

* [Create card](https://direct-api.reap.global/api-reference/cards/create-card.md)
* [List card categories](https://direct-api.reap.global/api-reference/cards/list-card-categories.md)
* [Error codes](https://direct-api.reap.global/api-reference/error-codes.md)

### Terminate a card without a request body

`DELETE /cards/{cardId}` now works without a request body. Before, a request
with no body returned 400. The body and its `reason` stay optional.

* [Terminate card](https://direct-api.reap.global/api-reference/cards/terminate-card.md)

### USDC deposits on Ink, Arbitrum and Base

USDC funding on Ink, Arbitrum (Arbitrum One) and Base becomes available once
Reap enables it for your business. Funding options then lists these networks
for the eligible `CARD`, `PAYMENTS` and `GENERAL` products it returns. They take
native USDC only. `CARD` is card collateral funding, so businesses on the card
top-up model don't get it.

`method.network` in Treasury transactions can return `INK`, `ARBITRUM` and
`BASE`, whether or not funding on that network is currently enabled for your
business. If your client validates `method.network` or the funding
`network` against a fixed list, accept unknown values.

* [Funding](https://direct-api.reap.global/concepts/treasury/funding.md) lists the networks and currencies
* [Retrieve funding instructions and Treasury history](https://direct-api.reap.global/guides/retrieve-funding-instructions-and-treasury-history.md)

## October 14, 2026

### Treasury funding and history

Treasury is live. Get the funding information for your card account by bank
transfer or crypto, confirm transfers programmatically, and read the full
transaction history from your own systems. The new endpoints sit behind three new scopes:
`treasury_funding:read`, `treasury_funding:write` and
`treasury_transactions:read`.

* [Treasury overview](https://direct-api.reap.global/concepts/treasury/overview.md) explains products, methods and eligibility
* [Funding](https://direct-api.reap.global/concepts/treasury/funding.md) covers instructions and confirmation rules
* [Treasury transactions](https://direct-api.reap.global/concepts/treasury/transactions.md) lists statuses, types and filters

## October 13, 2026

### Higher card creation limit

The card creation limit, shared with the dashboard, has been raised.

* [Rate limits](https://direct-api.reap.global/api-reference/rate-limits.md) explains how limiting works

## September 23, 2026

### Categories endpoints and new guides

`GET /cards/categories` and `GET /cards/transaction-categories` are live:
card categories label what a card is for, and transaction categories classify
each charge. Two new use-case guides landed alongside them.

* [List card categories](https://direct-api.reap.global/api-reference/cards/list-card-categories.md)
* [List transaction categories](https://direct-api.reap.global/api-reference/cards/list-transaction-categories.md)
* [Issue cards to your team](https://direct-api.reap.global/guides/issue-cards-to-your-team.md)
* [Cards for advertising at scale](https://direct-api.reap.global/guides/issue-cards-for-advertising.md)

## September 22, 2026

### Reveal flow, decline reasons and team member fields

* `POST /cards/{cardId}/reveal` now returns a short-lived `accessUrl` to a
  Reap-hosted card-details view. See [Card details](https://direct-api.reap.global/concepts/card-details.md).
* Card activities expose `declineReason` on `DECLINED` items.
* Team members now return `teamGroupName` and `inviteStatus`.

## September 17, 2026

### Card account activities and balances

`GET /cards/activities` and `GET /cards/balances` are live: track every card
movement and your credit position from the API.

* [Card activities](https://direct-api.reap.global/concepts/activities.md) lists types, statuses and decline reasons
* [Card account balances](https://direct-api.reap.global/concepts/card-account.md) explains the six balance figures

## September 11, 2026

### Higher card creation limit

The card creation limit, shared with the dashboard, has been raised.

## August 10, 2026

### Early access

The Business Account API opens in early access: team members, virtual cards,
spend controls and card details, behind a versioned `2026-07-13` base URL and
scoped API keys.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.