Pre-1.0 · one maintainer · Stripe and cards only · no SDKs (client libraries) yet · no production users yet. Docs describe v0.9.1 (29 Oct 2026) · What’s new →

Resend the payment-method setup link

POST

/v1/invoices/{id}/resend-setup-link

const url = 'http://localhost:8080/v1/invoices/example/resend-setup-link';
const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request POST \
  --url http://localhost:8080/v1/invoices/example/resend-setup-link \
  --header 'Authorization: Bearer <token>'

Emails the customer the link to add a payment method again. It is the same email Hardcount sends when an invoice is finalized and the customer has no card on file. Once a card is added, Hardcount charges the invoice automatically.

Works on unpaid invoices that are finalized or uncollectible. This is different from POST /v1/invoices/{id}/send, which emails the invoice itself with a link to pay it.

Authorizations

BearerAuth

Parameters

Path Parameters

required

string

Header Parameters

Idempotency-Key

string

Makes the call safe to retry. Send a unique value (a UUID works) and the same value on every retry. For 24 hours, a repeat with the same key, method, path and body gets the first response again, with an Idempotent-Replayed: true header, instead of running again. The error cases are in docs/api-surface.md. The usage routes do not take it: each usage event carries its own idempotency_key.

Responses

200

Email queued.

application/json

object

status

required

string

Allowed values: sent

Example

{
  "status": "sent"
}

404

Invoice not found.

application/json

object

error

object

type

One of invalid_request_error, authentication_error, rate_limit_error or api_error. Every error the API answers has this shape, including an unknown path (404, code route_not_found) and a method the path does not take (405, code method_not_allowed, with an Allow header). The few exceptions are listed in docs/api-surface.md.

string

code

string

message

string

request_id

string

param

The request field the error is about. Sent only when the error names one. A request body may hold only the fields its operation lists, spelled and cased as listed: any other field, or one the server sets (such as id), is refused with 422 and param naming it. An operation with no request body lists no fields: send no body, {} or null. The Stripe and Postmark webhooks and the LiteLLM callback take their sender’s body as it comes.

string

Example

{
  "error": {
    "type": "invalid_request_error"
  }
}

409

Nothing was sent. Codes: invoice_not_collectible (the invoice is draft, voided or paid), payment_in_flight or payment_unidentifiable (a charge is unresolved), email_not_configured (this server has no SMTP set up), or no_email_on_file (the customer has no email address).

application/json

object

error

object

type

string

code

string

message

string

request_id

string

param

string

Example

{
  "error": {
    "type": "invalid_request_error"
  }
}