canonical: https://jentic.com/apis/rebilly.com/rebilly-rest-api

# Rebilly REST API

Introduction The Rebilly API is built on HTTP. Our API is RESTful. It has predictable resource URLs. It returns HTTP response codes to indicate errors. It also accepts and returns JSON in the HTTP body. You can use your favorite HTTP/REST library for your programming language to use Rebilly's API, or you can use one of our SDKs (currently available in [PHP](https://github.com/Rebilly/rebilly-php) . The API exposes 184 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically create a threedsecure entry, retrieve a list of threedsecure entries. Covers 184 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- Create a ThreeDSecure entry
- Retrieve a list of ThreeDSecure entries
- Search PEP/Sanctions/Adverse Media lists
- Access Rebilly REST API ai ml resources via REST API

## Use cases

### AI and Machine Learning Operations

Use the Rebilly REST API to perform ai ml operations programmatically. The API provides 184 endpoints covering core functionality including create a threedsecure entry, retrieve a list of threedsecure entries, retrieve a threedsecure entry.

Example prompt: Call POST /3dsecure to create a threedsecure entry

### Automated 3D Secure Management

Automate 3d secure operations by combining multiple Rebilly REST API endpoints. Agents can retrieve a list of threedsecure entries and then retrieve a threedsecure entry in a single workflow.

Example prompt: Call GET /3dsecure to retrieve a list of threedsecure entries, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rebilly REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, bearer tokens manually.

Example prompt: Search Jentic for 'create a threedsecure entry', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/3dsecure` | Create a ThreeDSecure entry |
| GET | `/3dsecure` | Retrieve a list of ThreeDSecure entries |
| GET | `/3dsecure/{id}` | Retrieve a ThreeDSecure entry |
| GET | `/aml` | Search PEP/Sanctions/Adverse Media lists |
| POST | `/attachments` | Create an Attachment |
| GET | `/attachments` | Retrieve a list of Attachments |
| GET | `/attachments/{id}` | Retrieve an Attachment |
| PUT | `/attachments/{id}` | Update the Attachment with predefined ID |

## Key resources

- **3D Secure** — 3D Secure is a way to authenticate and protect transactions.  Typically,
it's only possible to prote
- **AML** — AML, also known as Anti-Money-Laundering is an endpoint that searches multiple
PEP, Sanctions, and A
- **Bank Accounts** — Bank Accounts are a type of payment instrument used to collect
ACH (echeck) payments, similar to how
- **Blocklists** — Your blocklists contains values of customerIds, email addresses,
ipAddresses, bank identification nu
- **Coupons** — Coupons allows to apply different types of discounts to Invoices, Orders and Plans. Redeemed Coupons

## Why Jentic

- **Setup:** Wiring the Rebilly REST API by hand means handling its two credential styles (a REB-APIKEY header secret key and JWT bearer tokens), choosing between the sandbox and production hosts, and managing auth yourself. Through Jentic you install once, import the Rebilly REST API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Rebilly puts resource ids in the URL path (for example `/attachments/{id}` and `/3dsecure/{id}`), so a rule can pin your agent to the specific resources it works with. You choose the operations it may call, so writes like creating attachments or 3D Secure entries are only included if you add them.
- **Credential handling:** Your Rebilly API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a 3D Secure entry' or 'upload an attachment', and Jentic returns the matching Rebilly operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the Rebilly REST API use?

The Rebilly REST API uses apiKey, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a threedsecure entry with the Rebilly REST API?

Yes. Use the POST /3dsecure endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Rebilly REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a threedsecure entry through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a threedsecure entry'. Jentic returns the matching Rebilly REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Rebilly REST API have?

The Rebilly REST API exposes 184 endpoints covering 3d secure, aml, bank accounts operations.

### Can I limit what my agent is allowed to do with the Rebilly REST API?

Yes. Because you run Jentic One yourself, your own rules decide which Rebilly operations and credentials the agent can use, so read-only calls like GET /3dsecure or GET /attachments can be enabled while write operations such as POST /3dsecure or POST /attachments are left out unless you add them. Since Rebilly places resource ids in the URL path, for example `/attachments/{id}` and `/3dsecure/{id}`, you can also pin the agent to the specific resources it is meant to touch. Your stored Rebilly API key is injected only at execution time and never reaches the agent's prompt or logs.