Skip to content
Payments

rebilly.com

Rebilly REST sandbox and mock 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 Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
184
Collections
-
Event types
-
Start this simulation
example request
curl https://your-rebilly.slurry.io/3dsecure \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 184.

  • GET/3dsecure
  • POST/3dsecure
  • GET/3dsecure/{id}
  • GET/aml
  • GET/attachments
  • POST/attachments
  • GET/attachments/{id}
  • PUT/attachments/{id}
  • DELETE/attachments/{id}
  • GET/authentication-options
  • PUT/authentication-options
  • GET/authentication-tokens