> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/soap-api-reference/soap-api-6.0/api-requests/invoices/resend-an-invoice.md).

# Resend an invoice

Use the **resendInvoice** method via JSON-RPC API 6.0 to resend the shopper invoice of an order by email. By default, the invoice is sent to the shopper’s email address on file. You can also send it to a different recipient.

## Request parameters <a href="#parameters" id="parameters"></a>

<table><thead><tr><th width="124.4000244140625">Parameter</th><th>Type / Description</th></tr></thead><tbody><tr><td><code>sessionID</code></td><td><strong>Required (string)</strong><br>Session identifier, the output of the <strong>Login</strong> method. Include <code>sessionID</code> into all your requests. 2Checkout throws an exception if the values are incorrect.  The <code>sessionID</code> expires in <strong>10 minutes</strong>.</td></tr><tr><td><code>refNo</code></td><td><strong>Required (string)</strong><br>The reference number of an approved/paid order.</td></tr><tr><td><code>email</code></td><td><p><strong>Optional (string)</strong></p><p>The recipient of the invoice email, for this send only. 2Checkout does not save it as the contact email of the order or of your account. If you omit it, or send an empty string, the invoice is sent to the shopper’s email address on file.</p></td></tr></tbody></table>

### Request sample

```php
<?php
require ('PATH_TO_AUTH');
$refNo = 'YOUR_ORDER_REFERENCE';
$email = 'jonathan.smith@mail.com';
try {
    $queued = $client->resendInvoice($sessionID, $refNo, $email);
}
catch (SoapFault $e) {
    echo "resendInvoice: " . $e->getMessage();
    exit;
}
var_dump("queued", $queued);
?>
```

## Response parameters <a href="#response" id="response"></a>

<table><thead><tr><th width="242.800048828125">Parameter</th><th>Type / Description</th></tr></thead><tbody><tr><td><code>Response</code></td><td><p><strong>Boolean</strong></p><p>Returns true when the resend was queued. </p></td></tr></tbody></table>

## Error codes

| Error code               | Description                                                                                                                                                  |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **BAD\_REQUEST**         | The email value is not a valid email address.                                                                                                                |
| **RESOURCE\_NOT\_FOUND** | The order reference does not exist or does not belong to your account, or the order has no shopper invoice yet because the invoice is still being generated. |
| **QUEUE\_ERROR**         | The resend could not be queued. Try again later.                                                                                                             |


---

# 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.2checkout.com/soap-api-reference/soap-api-6.0/api-requests/invoices/resend-an-invoice.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.