> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/cmp/developer-resources/guides/testing/on-demand-updates.md).

# On-Demand Updates

## On-Demand Updates API - Testing <a href="#on-demand-updates-api---testing" id="on-demand-updates-api---testing"></a>

On-Demand Updates API performs a **one-time lookup** for the most recent Account Updater status without enrolling the card for ongoing updates.

* Real-time updates are supported only for Visa and Mastercard.
* American Express and Discover are not supported for real-time Account Updater lookups.
* This mock does not track future updates and does not enroll the card in Account Updater.

The On-Demand Updates API mock allows you to test real-time card update scenarios for **Visa and Mastercard** cards.

### Testing Steps <a href="#testing-steps" id="testing-steps"></a>

1. **Account Enrollment Type:** Manual Enrollment
2. **Register Cards**: Use the **Create Card API** to register the test cards listed in the table below.
3. **Invoke On-Demand Updates API**: Call the **Card Check API** with the cardIDs obtained in step 2 to simulate a card update check.

**Note:** To test On-Demand Account Updater correctly, set your account to **manual enrollment**. Then, create cards using the test cards listed below and call the On-Demand endpoint individually using each card’s generated `cardID`.

The On-Demand endpoint returns the card’s current status in the synchronous response. An **`updated` result does not trigger an async webhook**. Use **`GET /cards/{id}`** to retrieve the updated card information.

If your account uses **on-create enrollment** with Account Updater enabled, the card update may already have been applied and sent to the webhook URL configured in your VGS dashboard before you call On-Demand. In that case, On-Demand will indicate that the card is valid because the update has already been applied; it will not trigger another webhook.

#### Test Cards and Expected Responses <a href="#test-cards-and-expected-responses" id="test-cards-and-expected-responses"></a>

| Test Cards        | Expiry Date | Expected Account Updater Event |
| ----------------- | ----------- | ------------------------------ |
| 4680056031099387  | 8/26        | Expired                        |
| 4403933787254356  | 9/26        | Closed                         |
| 4000220720915104  | 1/25        | Contact cardholder advice      |
| 4327390068355738  | 12/23       | Updated                        |
| 4549612182636736  | 3/23        | Account non-participating      |
| 5100260000099240  | 9/26        | Updated                        |
| 5100260000059244  | 6/26        | Closed                         |
| 51223511000004505 | 7/25        | Expired                        |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verygoodsecurity.com/cmp/developer-resources/guides/testing/on-demand-updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
