API archive entry · source-reported

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 and Javascript). We have other APIs that are also available. Every action from our app is supported by an API which is documented and available for use so that you may automate any workflows necessary. This document contains the most commonly integrated resources. # Authentication When you sign up for an account, you are given your first secret API key. You can generate additional API keys, and delete API keys (as you may need to rotate your keys in the future). You authenticate to the Rebilly API by providing your secret key in the request header. Rebilly offers three forms of authentication: secret key, publishable key, JSON Web Tokens, and public signature key. - Secret API key: used for requests made from the server side. Never share these keys. Keep them guarded and secure. - Publishable API key: used for requests from the

Provider / source website

Documentation & source

Use the provider’s reference for current endpoints, setup, limits and terms.

No separate documentation URL has been confirmed for this record.

Open provider / source ↗

Provider content retains its own terms. This listing does not grant reuse or training rights.

Where these facts came from

AltAPIs imported it from APIs.guru OpenAPI Directory. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Sep 20, 2026
  2. Last directory-field change: Sep 20, 2026
  3. Current source observation: Sep 20, 2026

Submit a source-backed correction

Source reference

APIs.guru OpenAPI Directory

This page separates source-reported facts from questions that need live provider verification.