Unfortunately, this feature is not supported on mobile devices. For the best experience, please use a computer.

Core APIs (latest)

Introduction

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:

For more information on API keys, see API keys.

Errors

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.

Rate limits

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.

Download OpenAPI description
Languages
Servers
Mock server
https://www.rebilly.com/_mock/docs/dev-docs/api/
Sandbox server
https://api-sandbox.rebilly.com/organizations/{organizationId}/
Live server
https://api.rebilly.com/organizations/{organizationId}/

Customers

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

Retrieve customer timeline custom event types

Request

Retrieves a list of customer timeline custom event types.

Query
limitinteger[ 0 .. 1000 ]

Limits the number of collection items to be returned.

offsetinteger[ 0 .. 1000 ]

Specifies the starting point within the collection of items to be returned.

filterstring

Filters the collection items. This field requires a special format. Use , for multiple allowed values. Use ; for multiple fields.

For more information, see Using filter with collections.

curl -i -X GET \
  'https://www.rebilly.com/_mock/docs/dev-docs/api/customer-timeline-custom-events?filter=string&limit=1000&offset=1000' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE'
Experience it firsthand in the API Explorer!

Responses

List of customer timeline custom event types 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 customer timeline custom event.

Example:

"tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC"

namestring[ 1 .. 255 ] charactersrequired

Name of the customer timeline custom event type. This value must not conflict with any system event name.

createdTimestring(date-time)(CreatedTime)read-only

Date and time which is set automatically when the resource is created.

updatedTimestring(date-time)(UpdatedTime)read-only

Date and time which updates automatically when the resource is updated.

_linksArray of objects(SelfLink)read-only

Related links.

]
Response
application/json
[ { "id": "tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC", "name": "string", "createdTime": "2019-08-24T14:15:22Z", "updatedTime": "2019-08-24T14:15:22Z", "_links": [] } ]

Create customer timeline custom event type

Request

Creates a customer timeline custom event type.

Bodyapplication/jsonrequired

Customer timeline custom event type resource.

namestring[ 1 .. 255 ] charactersrequired

Name of the customer timeline custom event type. This value must not conflict with any system event name.

curl -i -X POST \
  https://www.rebilly.com/_mock/docs/dev-docs/api/customer-timeline-custom-events \
  -H 'Content-Type: application/json' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE' \
  -d '{
    "name": "string"
  }'
Experience it firsthand in the API Explorer!

Responses

Customer timeline custom event type created.

Headers
Locationstring(uri)

Location of the related resource.

Example:

"https://api.rebilly.com/example"

X-RateLimit-Limitinteger

Total number of rate limit tokens for this request within a rate limit period. For more information, see Rate limits.

Example:

3600

X-RateLimit-Remaininginteger

Remaining number of rate limit tokens for this request within the rate limit period. For example, in the sandbox environment, rate limits for non-GET endpoints are set at 3000 requests per 10 minutes.

Example:

3600

Bodyapplication/json
idstring<= 50 charactersread-only

ID of the customer timeline custom event.

Example:

"tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC"

namestring[ 1 .. 255 ] charactersrequired

Name of the customer timeline custom event type. This value must not conflict with any system event name.

createdTimestring(date-time)(CreatedTime)read-only

Date and time which is set automatically when the resource is created.

updatedTimestring(date-time)(UpdatedTime)read-only

Date and time which updates automatically when the resource is updated.

_linksArray of objects(SelfLink)read-only

Related links.

Response
application/json
{ "id": "tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC", "name": "string", "createdTime": "2019-08-24T14:15:22Z", "updatedTime": "2019-08-24T14:15:22Z", "_links": [ {} ] }

Retrieve customer timeline custom event type

Request

Retrieves a customer timeline custom event type with a specified ID.

Path
idstring<= 50 characters^[@~\-\.\w]+$required

ID of the resource.

curl -i -X GET \
  'https://www.rebilly.com/_mock/docs/dev-docs/api/customer-timeline-custom-events/{id}' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE'
Experience it firsthand in the API Explorer!

Responses

Customer timeline custom event type 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/json
idstring<= 50 charactersread-only

ID of the customer timeline custom event.

Example:

"tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC"

namestring[ 1 .. 255 ] charactersrequired

Name of the customer timeline custom event type. This value must not conflict with any system event name.

createdTimestring(date-time)(CreatedTime)read-only

Date and time which is set automatically when the resource is created.

updatedTimestring(date-time)(UpdatedTime)read-only

Date and time which updates automatically when the resource is updated.

_linksArray of objects(SelfLink)read-only

Related links.

Response
application/json
{ "id": "tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC", "name": "string", "createdTime": "2019-08-24T14:15:22Z", "updatedTime": "2019-08-24T14:15:22Z", "_links": [ {} ] }

Retrieve customer timeline messages

Request

Retrieves customer timeline messages.

Path
idstring<= 50 characters^[@~\-\.\w]+$required

ID of the resource.

Query
limitinteger[ 0 .. 1000 ]

Limits the number of collection items to be returned.

offsetinteger[ 0 .. 1000 ]

Specifies the starting point within the collection of items to be returned.

filterstring

Filters the collection items. This field requires a special format. Use , for multiple allowed values. Use ; for multiple fields.

For more information, see Using filter with collections.

sortArray of strings

Sorts and orders the collection of items. To sort in descending order, prefix with -. Multiple fields can be sorted by separating each with ,.

qstring

Use this field to perform a partial search of text fields.

curl -i -X GET \
  'https://www.rebilly.com/_mock/docs/dev-docs/api/customers/{id}/timeline?filter=string&limit=1000&offset=1000&q=string&sort=string' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE'
Experience it firsthand in the API Explorer!

Responses

List of customer timeline messages 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 customer timeline custom event.

Example:

"tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC"

typestring

Type of timeline message.

Enum"account-password-reset-requested""account-verification-requested""aml-list-was-possibly-matched""deposit-request-completed""deposit-request-created""deposit-request-expired""deposit-request-started""coupon-applied""coupon-redeemed""coupon-redemption-canceled"
customEventTypestring or null[ 1 .. 255 ] characters
triggeredBystringread-only

Specifies who, or what, triggered the timeline event.

Enum"rebilly""app""direct-api"
messagestring

Detailed message description.

extraDataobject(TimelineExtraData)read-only

Additional data.

occurredTimestring(date-time)(ServerTimestamp)read-only

Read-only timestamp in ISO 8601 date-time format.

_linksArray of objects(SelfLink)read-only

Related links.

]
Response
application/json
[ { "id": "tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC", "type": "account-password-reset-requested", "customEventType": "string", "triggeredBy": "rebilly", "message": "string", "extraData": {}, "occurredTime": "2019-08-24T14:15:22Z", "_links": [] } ]

Create a customer timeline comment

Request

Creates a customer timeline comment or custom defined event.

Path
idstring<= 50 characters^[@~\-\.\w]+$required

ID of the resource.

Bodyapplication/jsonrequired

Customer timeline resource.

typestring

Type of timeline message.

Enum"account-password-reset-requested""account-verification-requested""aml-list-was-possibly-matched""deposit-request-completed""deposit-request-created""deposit-request-expired""deposit-request-started""coupon-applied""coupon-redeemed""coupon-redemption-canceled"
customEventTypestring or null[ 1 .. 255 ] characters
customDataobjectwrite-only

Timeline custom event data. Used with custom-event type. Transforms to extraData two-column table in response.

Example:

{"customAttribute":"customValue","otherAttribute":"otherValue"}

messagestring

Detailed message description.

curl -i -X POST \
  'https://www.rebilly.com/_mock/docs/dev-docs/api/customers/{id}/timeline' \
  -H 'Content-Type: application/json' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE' \
  -d '{
    "type": "account-password-reset-requested",
    "customEventType": "string",
    "customData": {
      "customAttribute": "customValue",
      "otherAttribute": "otherValue"
    },
    "message": "string"
  }'
Experience it firsthand in the API Explorer!

Responses

Customer timeline comment or custom defined event created.

Headers
Locationstring(uri)

Location of the related resource.

Example:

"https://api.rebilly.com/example"

X-RateLimit-Limitinteger

Total number of rate limit tokens for this request within a rate limit period. For more information, see Rate limits.

Example:

3600

X-RateLimit-Remaininginteger

Remaining number of rate limit tokens for this request within the rate limit period. For example, in the sandbox environment, rate limits for non-GET endpoints are set at 3000 requests per 10 minutes.

Example:

3600

Bodyapplication/json
idstring<= 50 charactersread-only

ID of the customer timeline custom event.

Example:

"tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC"

typestring

Type of timeline message.

Enum"account-password-reset-requested""account-verification-requested""aml-list-was-possibly-matched""deposit-request-completed""deposit-request-created""deposit-request-expired""deposit-request-started""coupon-applied""coupon-redeemed""coupon-redemption-canceled"
customEventTypestring or null[ 1 .. 255 ] characters
triggeredBystringread-only

Specifies who, or what, triggered the timeline event.

Enum"rebilly""app""direct-api"
messagestring

Detailed message description.

extraDataobject(TimelineExtraData)read-only

Additional data.

occurredTimestring(date-time)(ServerTimestamp)read-only

Read-only timestamp in ISO 8601 date-time format.

_linksArray of objects(SelfLink)read-only

Related links.

Response
application/json
{ "id": "tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC", "type": "account-password-reset-requested", "customEventType": "string", "triggeredBy": "rebilly", "message": "string", "extraData": { "actions": [], "tables": [], "author": {}, "mentions": {}, "links": [] }, "occurredTime": "2019-08-24T14:15:22Z", "_links": [ {} ] }

Retrieve a customer timeline message

Request

Retrieves a customer message with a specified ID.

Path
idstring<= 50 characters^[@~\-\.\w]+$required

ID of the resource.

messageIdstringrequired

ID of the customer timeline message.

curl -i -X GET \
  'https://www.rebilly.com/_mock/docs/dev-docs/api/customers/{id}/timeline/{messageId}' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE'
Experience it firsthand in the API Explorer!

Responses

Customer message retrieved.

Bodyapplication/json
idstring<= 50 charactersread-only

ID of the customer timeline custom event.

Example:

"tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC"

typestring

Type of timeline message.

Enum"account-password-reset-requested""account-verification-requested""aml-list-was-possibly-matched""deposit-request-completed""deposit-request-created""deposit-request-expired""deposit-request-started""coupon-applied""coupon-redeemed""coupon-redemption-canceled"
customEventTypestring or null[ 1 .. 255 ] characters
triggeredBystringread-only

Specifies who, or what, triggered the timeline event.

Enum"rebilly""app""direct-api"
messagestring

Detailed message description.

extraDataobject(TimelineExtraData)read-only

Additional data.

occurredTimestring(date-time)(ServerTimestamp)read-only

Read-only timestamp in ISO 8601 date-time format.

_linksArray of objects(SelfLink)read-only

Related links.

Response
application/json
{ "id": "tmln_0YV8Q9WEF5DTA8HFXS27D1G6GC", "type": "account-password-reset-requested", "customEventType": "string", "triggeredBy": "rebilly", "message": "string", "extraData": { "actions": [], "tables": [], "author": {}, "mentions": {}, "links": [] }, "occurredTime": "2019-08-24T14:15:22Z", "_links": [ {} ] }