Updates a transaction using its ID.
You can update transactions that are draft or ready. billed and completed transactions are considered records for tax and legal purposes, so they can’t be changed. You can either:
billed transaction by sending a PATCH request to set status to canceled.The transaction status may only be set to billed or canceled. Other statuses are set automatically by Paddle. Set a manually-collected transaction to billed to mark it as finalized. This is essentially issuing an invoice. At this point, it becomes a legal record so you can’t make changes to it. Paddle automatically assigns an invoice number, creates a related subscription, and sends it to your customer.
When making changes to items on a transaction, send the complete list of items that you’d like to be on a transaction — including existing items. For each item, send an object containing price_id and quantity. Paddle responds with the full price object for each item. See: Work with lists
If successful, your response includes a copy of the updated transaction entity.
Requests are authenticated with API keys. Provide your API key as a Bearer token in the Authorization header.
API keys are assigned permissions, granting them access to entities and operations.
Each endpoint may require one or more permissions, defined with the x-permissions extension.
Values for include parameters may require specific permissions as defined in the x-enum-permissions extension.
See all available permissions in the permission schema or documentation.
Get an API key and select the permissions you need from the Paddle dashboard under Paddle > Developer Tools > Authentication.
Paddle ID of the transaction entity to work with.
"txn_01gw225vv6tjbb5gnt062a3k5v"
Include related entities in the response. Use a comma-separated list to specify multiple entities.
address, adjustments, adjustments_totals, available_payment_methods, business, customer, discount Represents a transaction entity when updating transactions.
Status of this transaction. You may set a transaction to billed or canceled. Billed transactions cannot be changed.
For manually-collected transactions, marking as billed is essentially issuing an invoice.
draft, ready, billed, paid, completed, canceled, past_due Paddle ID of the customer that this transaction is for, prefixed with ctm_.
"ctm_01grnn4zta5a1mf02jjze7y2ys"
Paddle ID of the address that this transaction is for, prefixed with add_.
"add_01gm302t81w94gyjpjpqypkzkf"
Paddle ID of the business that this transaction is for, prefixed with biz_.
"biz_01grrebrzaee2qj2fqqhmcyzaj"
Your own structured key-value data.
{ "customer_reference_id": "abcd1234" }Supported three-letter ISO 4217 currency code. Must be USD, EUR, or GBP if collection_mode is manual.
USD, EUR, GBP, JPY, AUD, CAD, CHF, HKD, SGD, SEK, ARS, BRL, CNY, COP, CZK, DKK, HUF, ILS, INR, KRW, MXN, NOK, NZD, PLN, RUB, THB, TRY, TWD, UAH, VND, ZAR 3How payment is collected for this transaction. automatic for checkout, manual for invoices.
automatic, manual Paddle ID of the discount applied to this transaction, prefixed with dsc_.
"dsc_01gv5kpg05xp104ek2fmgjwttf"
Details for invoicing. Required if collection_mode is manual.
Time period that this transaction is for. Set automatically by Paddle for subscription renewals to describe the period that charges are for.
List of items on this transaction.
When making a request, each object must contain either a price_id or a price object, and a quantity.
Include a price_id to charge for an existing catalog item, or a price object to charge for a non-catalog item.
1 - 100 elementsAdd a catalog item to a transaction. In this case, the product and price that you're billing for exist in your product catalog in Paddle.
Paddle Checkout details for this transaction. You may pass a URL when creating or updating an automatically-collected transaction, or when creating or updating a manually-collected transaction where billing_details.enable_checkout is true.