Authorizations
API Keys can be issued in the Orb's web application.
Path Parameters
Body
increment
The number of credits to effect. Note that this is required for increment, decrement, void, or undo operations.
User-specified key/value pairs for the resource. Individual keys can be removed by setting the value to null
, and the entire metadata mapping can be cleared by setting metadata
to null
.
The currency or custom pricing unit to use for this ledger entry. If this is a real-world currency, it must match the customer's invoicing currency.
Optional metadata that can be specified when adding ledger results via the API. For example, this can be used to note an increment refers to trial credits, or for noting corrections as a result of an incident, etc.
An ISO 8601 format date that denotes when this credit balance should expire.
An ISO 8601 format date that denotes when this credit balance should become available for use.
Can only be specified when entry_type=increment. How much, in the customer's currency, a customer paid for a single credit in this block
Passing invoice_settings
automatically generates an invoice for the newly added credits. If invoice_settings
is passed, you must specify per_unit_cost_basis, as the calculation of the invoice total is done on that basis.
Response
Created
The Credit Ledger Entry resource models prepaid credits within Orb.
User specified key-value pairs for the resource. If not present, this defaults to an empty dictionary. Individual keys can be removed by setting the value to null
, and the entire metadata mapping can be cleared by setting metadata
to null
.
committed
, pending
increment
If the increment resulted in invoice creation, the list of created invoices