> 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/delete-card.md).

# Delete Card

## Delete Card API - Mock Testing <a href="#delete-card-api---mock-testing" id="delete-card-api---mock-testing"></a>

For the Delete Card API, the testing process is dependent on the card objects created using the Create Card API mock.

* **Valid Card IDs:**
  * When a card object is successfully created using the Create Card API mock using the static BIN method (i.e., the static BIN followed by any random numbers as the PAN), a cardID is returned in the response.
  * When the Delete Card API mock is triggered using a valid cardID a success response is returned.
* **Invalid Card IDs:**
  * Using an invalid cardID will return a 404 error response.
* **Other Error Responses:**
  * Depending on the credentials used and the syntax of the request URL, other error messages (e.g., 4XX errors) can be triggered.

Note: 5XX errors cannot be triggered using the Delete Card API mock.


---

# 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/delete-card.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.