Create a wallet funding invoice
const url = 'https://api.trueproxies.com/v1/wallet/topups';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"amount_cents":1}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.trueproxies.com/v1/wallet/topups \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "amount_cents": 1 }'Resellers need reseller:purchase; other customers need billing:write and can top up while can_top_up from GET /v1/wallet is true. Creates an unpaid invoice; does not add funds until the payment settles. No on-behalf access. Uses normal provider checkout. API keys must send an Idempotency-Key header.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Required for API-key requests; optional for dashboard sessions. Makes a retry safe. The first request carrying a given key is executed and its response recorded; repeating the same request with the same key replays that response, with Idempotency-Replayed: true, rather than buying or paying a second time. Reusing a key for a different request is refused with 409, as is a repeat that arrives while the first is still running. Keys are scoped to your account and to the endpoint. Successful and uncertain invoice commands are retained so that an old retry cannot create another invoice. Completed definite rejections are kept for at least 24 hours; after that, the same key may be evaluated again.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Amount in USD cents: at least topup_min_cents returned by GET /v1/wallet ($50.00 for a reseller, $10.00 for other customers). Also limited by daily_remaining_cents; unpaid funding invoices count toward that rolling limit.
Examplegenerated
{ "amount_cents": 1}Responses
Section titled “Responses”Success
object
When this invoice’s service activation, top-up, renewal, or charge-only processing committed. Payment receipt and an already-active service do not establish this outcome.
Automatic fulfillment stopped and needs operator attention. Payment remains received; this does not mean a refund completed or previously purchased service was revoked.
Who the invoice is issued to, copied from the account’s billing details when the invoice was created. Absent when the account had no billing details then; saving details later does not change it.
object
True when a cancelled invoice closed because it was not paid by due_at. Invoices cancelled before this field existed report false.
Internal API identifier. Use reference for customer-facing display.
object
GB for top-ups; taken from the offer otherwise
IPs for isp_dedicated
object
Present only while the invoice is payable and the pending checkout has not reached its known expiry
Staff views only. Why the checkout ended unpaid, as the provider reports it: not_attempted (no payment submitted), not_completed (started, never confirmed), or the card issuer’s code such as card_declined/insufficient_funds.
A provider refund was reported without a trustworthy amount. Reconciliation is required before any additional refund.
The recorded request can be retried unchanged within the provider idempotency window.
Refund request recorded at; not proof of completion
What this applied payment added to the wallet: the rest of a minimum payment ($10 by card, $3 by crypto) above the invoice amount, or crypto sent above it. Absent when nothing was added.
Stable, unique customer-facing reference.
Plan upgrades only. Credit for unused time on the previous plan.
Plan upgrades only. The new plan’s price; amount_cents is this minus upgrade_credit_cents.
Example
{ "kind": "wallet_topup", "payments": [ { "provider": "manual", "refund_status": "processing", "status": "pending" } ], "reference": "INV-001001", "status": "open"}Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}default
Section titled “default”Error
object
What a client needs to act on the error (ids, flags), never display text.
object
Example
{ "code": "BAD_REQUEST"}