The Rebilly API is built on HTTP and is RESTful. It has predictable resource URLs and returns HTTP response codes to indicate errors. It also accepts and returns JSON in the HTTP body. Use your favorite HTTP/REST library in your programming language when using this API, or use one of the Rebilly SDKs, which are available in PHP and JavaScript.
Every action in the Rebilly UI is supported by an API which is documented and available for use, so that you may automate any necessary workflows or processes. This API reference documentation contains the most commonly integrated resources.
Authentication
This topic describes the different forms of authentication that are available in the Rebilly API, and how to use them.
Rebilly offers four forms of authentication: secret key, publishable key, JSON Web Tokens, and public signature key.
Secret API key: Use to make requests from the server side. Never share these keys. Keep them guarded and secure.
Publishable API key: Use in your client-side code to tokenize payment information.
JWT: Use to make short-life tokens that expire after a set period of time.
Manage API keys
To create or manage API keys, select one of the following:
Rebilly follows the error response format proposed in RFC 9457, which is also known as Problem Details for HTTP APIs. As with any API responses, your client must be prepared to gracefully handle additional members of the response.
SDKs
Rebilly provides a JavaScript SDK and a PHP SDK to help interact with the Rebilly API. However, no SDK is required to use the API.
Rebilly also provides FramePay, a client-side iFrame-based solution, to help create payment tokens while minimizing PCI DSS compliance burdens and maximizing your customization ability. FramePay interacts with the payment tokens creation operation.
JavaScript SDK
For installation and usage instructions, see SDKs. All JavaScript SDK code examples are included in the API reference documentation.
PHP SDK
For installation and usage instructions, see SDKs. All SDK code examples are included in the API reference documentation. To use them, you must configure the $client as follows:
$client = new Rebilly\Client([ 'apiKey' => 'YourApiKeyHere', 'baseUrl' => 'https://api.rebilly.com',]);
Get started
The full Rebilly API has over 500 operations. This is likely more than you may need to implement your use cases. If you would like to implement a particular use case, contact Rebilly for guidance and feedback on the best API operations to use for the task.
To integrate Rebilly, and learn about related resources and concepts, see Get started.
Rebilly enforces rate limits on the API to ensure that no single organization consumes too many resources. Rate limits are applied to the organization, and not to the API key. In sandbox environment, rate limits are enforced for non-GET endpoints and are set at 3000 requests per 10 minutes. You can find the exact number of consumed requests in the X-RateLimit-Limit and X-RateLimit-Remaining headers in the response. If the rate limit is exceeded, the API returns a 429 Too Many Requests response and a X-RateLimit-Retry-After header that includes a UTC timestamp of when the rate limit resets.
Use these operations to manage customers. A customer is an entity that purchases goods or services from you (a merchant), and is the payee in any transaction that is credited to you. Customers are associated with payment instruments, subscriptions, invoices, and other related resources.
In other systems, customers may be referred to as accounts, clients, members, patrons, or players. For information on the customer resource, see Resources.
Operations
Customer authentication
Use these operations to validate the identity of users and manage authentication credentials.
Operations
Tags
Use tags to organize and categorize customers or KYC documents based on keywords.
Operations
Customers timeline
Use customer timelines to maintain an audit trail of changes and activity for each customer.
Operations
Payment instruments
Use these operations to manage payment instruments. Payment instrument is a term which describes any means of making a digital payment, such as: credit cards, debit cards, direct debits, payment service providers, and digital wallets.
A payment token can be made using a different authentication scheme (public key authentication), which enables you to create a payment token directly from the browser. This bypasses the need to send sensitive cardholder info to your servers. We recommend using this with the FramePay library, which helps you integrate a form into this API resource and create payment tokens.
Operations
Transactions
Use these operations to:
set up payment instruments for payments
authorize and hold funds
capture funds
make payments
make payouts
refund transactions.
Operations
Disputes
Use these operations to manage disputes. A dispute occurs when a customer contests a charge to their account. The dispute and related information is made available to the merchant by the bank or credit card company. The merchant then has the option to represent the charge and win the case. This process is called dispute resolution. If the merchant is unable to represent the charge, the card issuer typically reverses the sale and adds fees on top of the charge. This process is called a chargeback.
OperationsWebhooks
Fees
Use fees to reconcile transactions with applicable fees and discount rates. Fees are not applied directly to transaction amounts, they do not modify the transaction amount. Fees help to describe each part of the transaction amount.
Important: These operations are experimental and may change.
Operations
Transactions timeline
Use transaction timelines to maintain an audit trail of changes and activity for each transaction.
Operations
Orders
Use these operations to manage customer orders. An order is a customer's request to purchase items. It can contain subscription and one-time sale items. When an order contains one or more subscription items, it is a subscription order.
An order generates an invoice. A subscription order generates an invoice for each service period. For more information, see Orders.
Operations
Invoices
Use invoices to bill for the goods or services that you provide. If your invoice includes subscription items, it also includes the corresponding service periods and prices.
Operations
Usage
Use these operations to manage the product usage of a subscription item for metered billing purposes.
Use metered billing when product quantity is unknown to the customer at the moment of creating a subscription. Metered billing is based on reported usage records. Every reported usage updates the quantity of an upcoming invoice item for a specified subscription and a plan. To create a metered billing plan, see Plans.
Operations
Credit memos
Use credit memos to provide a customer with store credit. A common use case for using a credit memo is to provide a customer with store credit, rather than a refund, if the customer pays more than they owe or returns a product. For information on the credit memo resource, see Resources.
OperationsWebhooks
Plans
Use pricing plans to describe how the customer must pay for products.
Rebilly provides the following plan types:
Trial only: Use this plan to create and offer a free or discounted trial period for your product. For example, a free 2 week trial of an internet service. After the trial, the customer can choose to sign up for a paid subscription, or stop using the service.
Recurring: Use this plan to create and offer a subscription for your product. For example, a monthly subscription to an internet service that is charged at 20 USD per month.
One time sale: Use this plan to create and offer a one-off sale for your products. For example, a one time purchase of two bags of coffee.
Use products to describe the goods and services that your business sells. A product also describes sales items on invoices and receipts. Product pricing is defined in plans. A product may have one or many plans.
For information on the product resource, see Product.
Operations
Coupons
Use coupons to reward customers, generate sales, or to test new pricing strategies. Coupons enable you to apply different types of discounts to invoices, subscriptions, and pricing plans.
Redeemed coupons are attached to a customer's account. Depending on the coupon restrictions, the redeemed coupons are then applied from the customer's account to subsequent invoices or subscriptions. Redeemed coupons can only be applied to invoices of the same currency.
Once a coupon is redeemed it cannot be modified. You may deactivate a coupon or create a new coupon, but you cannot reuse the same coupon code. If you have a use case where you must reuse the same code, contact Rebilly.
Operations
Quotes
Use quote operations to create and manage quotations. Quotations describe the cost of goods or services to potential customers before they commit to a purchase. A quote contains an initial invoice preview that can be accepted to become an order.
A quote can contain subscription and one-time sale items. When a quote contains one or more subscription items, it is a subscription order quote.
Operations
Retrieve quotesExperimental
Request
Retrieves a list of quotes.
Query
filterstring
Filters the collection items. This field requires a special format. Use , for multiple allowed values. Use ; for multiple fields.
Mock server https://www.rebilly.com/_mock/docs/dev-docs/api/quotes
Sandbox server https://api-sandbox.rebilly.com/organizations/{organizationId}/quotes
Live server https://api.rebilly.com/organizations/{organizationId}/quotes
curl
JavaScript
Node.js
Python
Java
C#
PHP
Go
Ruby
R
Payload
curl -i -X GET \ 'https://www.rebilly.com/_mock/docs/dev-docs/api/quotes?expand=string&filter=string&limit=1000&offset=1000&sort=string' \ -H 'REB-APIKEY: YOUR_API_KEY_HERE'
Responses
List of quotes retrieved.
Headers
Pagination-Totalinteger
Total number of items.
Example: 332
Pagination-Limitinteger
Maximum number of items per page.
Example: 100
Pagination-Offsetinteger
Specifies the starting point within the collection of resource results. For example, a request with limit=20 retrieves and displays the first 20 results on a page. A following request with limit=20 and offset=20, retrieves the next page of 20 results.
Example: 2
Bodyapplication/jsonArray [
idstring<= 50 charactersread-only
ID of the quote.
Example: "qt_01HXBZMEGPETPHJZH6V4RHBMA8"
typestringread-only
Specifies the type of the quote. A quote can be a subscription or a one-time purchase.
Enum"subscription-order""one-time-order"
actionstringrequired
Action of the quote. When a quote is accepted, a new order is created. The subscriptionId value is filled with a new generated value from the order.
Value"create"
Example: "create"
Discriminator
acceptanceFulfillmentArray of objectsread-only
List of acceptanceConditions with fulfillment status.
subscriptionIdstring or null<= 50 charactersread-only
ID of the related subscription or one-time purchase.
invoiceIdstring<= 50 charactersread-only
ID of the payment invoice.
Example: "in_0YVF9605RKC62BP14NE2R7V2XT"
statusstringread-only
Status of the quote.
Enum Value
Description
draft
Quote can be edited. This quote cannot be sent to a customer.
issued
Quote cannot be edited. This quote can be sent to a customer.
accepted
Customer accepted the quote and created an order.
rejected
Customer rejected the quote.
canceled
Organization canceled the quote.
expired
Expired before customer or organization interaction.
Date and time which updates automatically when the resource is updated.
items[].​_embeddedobjectread-only
Embedded objects that are requested by the expand query parameter.
deliveryAddressContactObject (object) or null
Delivery address of the order.
One of:
Delivery address of the order.
billingAddressContactObject (object) or null
Billing address of the order.
One of:
Billing address of the order.
invoicePreviewobjectread-only
Preview of the quote invoice.
autopayboolean
Specifies if payment attempts for the related subscription are made automatically. If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at paymentInstrumentId, or the default payment instrument on the subscription.
Default false
paymentTermsstring
Payment terms for the customer which are displayed on the quote.
expirationTimestring or null(date-time)
Date and time when the quote expires. The default expiration time is one month from the time the quote is issued. In a draft state, this field may be null.
Price description of the quote item. This value is only used for metered billing items.
Default ""
Example: "50% of the markup for approved transactions"
items[].​usageLimitsobject or null
Specifies the soft and hard usage limit thresholds for an item with a metered billing plan. This value is ignored when the plan is not metered.
Default null
deliveryAddressContactObject (object) or null
Delivery address of the order.
One of:
Delivery address of the order.
billingAddressContactObject (object) or null
Billing address of the order.
One of:
Billing address of the order.
autopayboolean
Specifies if payment attempts for the related subscription are made automatically. If autopay is enabled, the payment is retrieved from the customer on the renewal date using the payment instrument that is set at paymentInstrumentId, or the default payment instrument on the subscription.
Default false
paymentTermsstring
Payment terms for the customer which are displayed on the quote.
expirationTimestring or null(date-time)
Date and time when the quote expires. The default expiration time is one month from the time the quote is issued. In a draft state, this field may be null.
redirectUrlstring(uri)
URL to redirect the customer to when a quote is rejected. The default value is the website URL.
signatureobject
Written signature and printed organization name.
shippingobject(Shipping)
Shipping settings.
taxobject(Taxes)
Taxes.
couponIdsArray of strings or null
List of coupons to redeem on the customer and apply to the related invoice.