Unfortunately, this feature is not supported on mobile devices. For the best experience, please use a computer.
Developer docs
/
Rebilly API
/
Fees
/
Delete a fee entry

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
openapi.json
openapi.yaml
Overview
URL https://www.rebilly.com/contact/
Rebilly API Support integrations@rebilly.com
License Rebilly
 Terms of Service
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

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.

For more information on payment instruments, see Payment instruments.

OperationsWebhooks

Payment tokens

Use payment tokens to reduce the scope of PCI DSS compliance.

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

Retrieve fee entriesExperimental

Request

Retrieves a list of fee entries.

Important: This operation is experimental and may not be backward compatible.

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 ,.

curl -i -X GET \
  'https://www.rebilly.com/_mock/docs/dev-docs/api/fees?filter=string&limit=1000&offset=1000&sort=string' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE'

Responses

List of fee entries 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 fee.

Example: "fee_01GQT145JX3XBRJ8K812Y3GRE9"
typestringrequired

Type of fee.

Enum"buy""sell"
namestring[ 1 .. 255 ] charactersrequired

Name of the fee.

Example: "A gateway fee"
filterstring or null[ 1 .. 255 ] characters

Filter that is based on the properties of the transaction and used to determine when to apply the fee.

Example: "type:sale,capture;result:approved"
formulaobject(FeeFormula)required

Formula that is used to calculate the fee.

formula.​typestringrequired

Type of fee.

Value"fixed-fee"
Discriminator
formula.​currencystring(CurrencyCode)= 3 charactersrequired

Currency code in ISO 4217 format.

formula.​amountnumber(double)required

Amount of the fee.

Example: 10
settlementSettingsSettlementSettings (object) or null

Fee settlement settings. This value overrides the gateway account financial settings of the transaction.

One of:

Fee settlement settings. This value overrides the gateway account financial settings of the transaction.

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": "fee_01GQT145JX3XBRJ8K812Y3GRE9",
    "type": "buy",
    "name": "A gateway fee",
    "filter": "type:sale,capture;result:approved",
    "formula": { … },
    "settlementSettings": { … },
    "createdTime": "2019-08-24T14:15:22Z",
    "updatedTime": "2019-08-24T14:15:22Z",
    "_links": [ … ]
  }
]

Create a fee entryExperimental

Request

Creates a fee entry.

Important: This operation is experimental and may not be backward compatible.

Bodyapplication/jsonrequired
typestringrequired

Type of fee.

Enum"buy""sell"
namestring[ 1 .. 255 ] charactersrequired

Name of the fee.

Example: "A gateway fee"
filterstring or null[ 1 .. 255 ] characters

Filter that is based on the properties of the transaction and used to determine when to apply the fee.

Example: "type:sale,capture;result:approved"
formulaobject(FeeFormula)required

Formula that is used to calculate the fee.

formula.​typestringrequired

Type of fee.

Value"fixed-fee"
Discriminator
formula.​currencystring(CurrencyCode)= 3 charactersrequired

Currency code in ISO 4217 format.

formula.​amountnumber(double)required

Amount of the fee.

Example: 10
settlementSettingsSettlementSettings (object) or null

Fee settlement settings. This value overrides the gateway account financial settings of the transaction.

One of:

Fee settlement settings. This value overrides the gateway account financial settings of the transaction.

curl -i -X POST \
  https://www.rebilly.com/_mock/docs/dev-docs/api/fees \
  -H 'Content-Type: application/json' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE' \
  -d '{
    "type": "buy",
    "name": "Stripe transaction fees",
    "filter": "type:sale,capture;result:approved;gatewayAccountId:stripe",
    "formula": {
      "type": "fixed-fee",
      "currency": "USD",
      "amount": 0.3
    }
  }'

Responses

Fee entry 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 fee.

Example: "fee_01GQT145JX3XBRJ8K812Y3GRE9"
typestringrequired

Type of fee.

Enum"buy""sell"
namestring[ 1 .. 255 ] charactersrequired

Name of the fee.

Example: "A gateway fee"
filterstring or null[ 1 .. 255 ] characters

Filter that is based on the properties of the transaction and used to determine when to apply the fee.

Example: "type:sale,capture;result:approved"
formulaobject(FeeFormula)required

Formula that is used to calculate the fee.

formula.​typestringrequired

Type of fee.

Value"fixed-fee"
Discriminator
formula.​currencystring(CurrencyCode)= 3 charactersrequired

Currency code in ISO 4217 format.

formula.​amountnumber(double)required

Amount of the fee.

Example: 10
settlementSettingsSettlementSettings (object) or null

Fee settlement settings. This value overrides the gateway account financial settings of the transaction.

One of:

Fee settlement settings. This value overrides the gateway account financial settings of the transaction.

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

Stripe transaction fees. Discount rate fees are a separate record.

{
  "id": "fee_01GQT145JX3XBRJ8K812Y3GRE9",
  "type": "buy",
  "name": "Stripe transaction fees",
  "filter": "type:sale,capture;result:approved;gatewayAccountId:stripe",
  "formula": {
    "type": "fixed-fee",
    "currency": "USD",
    "amount": 0.3
  },
  "createdTime": "2021-12-15T14:15:22Z",
  "updatedTime": "2021-12-15T14:15:22Z",
  "_links": [
    { … }
  ]
}

Retrieve a fee entryExperimental

Request

Retrieves a fee entry.

Important: This operation is experimental and may not be backward compatible.

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

ID of the resource.

curl -i -X GET \
  'https://www.rebilly.com/_mock/docs/dev-docs/api/fees/{id}' \
  -H 'REB-APIKEY: YOUR_API_KEY_HERE'

Responses

Fee retrieved.

Bodyapplication/json
idstring<= 50 charactersread-only

ID of the fee.

Example: "fee_01GQT145JX3XBRJ8K812Y3GRE9"
typestringrequired

Type of fee.

Enum"buy""sell"
namestring[ 1 .. 255 ] charactersrequired

Name of the fee.

Example: "A gateway fee"
filterstring or null[ 1 .. 255 ] characters

Filter that is based on the properties of the transaction and used to determine when to apply the fee.

Example: "type:sale,capture;result:approved"
formulaobject(FeeFormula)required

Formula that is used to calculate the fee.

formula.​typestringrequired

Type of fee.

Value"fixed-fee"
Discriminator
formula.​currencystring(CurrencyCode)= 3 charactersrequired

Currency code in ISO 4217 format.

formula.​amountnumber(double)required

Amount of the fee.

Example: 10
settlementSettingsSettlementSettings (object) or null

Fee settlement settings. This value overrides the gateway account financial settings of the transaction.

One of:

Fee settlement settings. This value overrides the gateway account financial settings of the transaction.

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

Stripe transaction fees. Discount rate fees are a separate record.

{
  "id": "fee_01GQT145JX3XBRJ8K812Y3GRE9",
  "type": "buy",
  "name": "Stripe transaction fees",
  "filter": "type:sale,capture;result:approved;gatewayAccountId:stripe",
  "formula": {
    "type": "fixed-fee",
    "currency": "USD",
    "amount": 0.3
  },
  "createdTime": "2021-12-15T14:15:22Z",
  "updatedTime": "2021-12-15T14:15:22Z",
  "_links": [
    { … }
  ]
}