Rebilly REST API

api:rebilly.com · v2.1 · source: apis.guru

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 client side. For now can only be used to create a Payment Token and a File token. - JWT: short lifetime tokens that can be assigned a specific expiration time. Never share your secret keys. Keep them guarded and secure. <!-- ReDoc-Inject: <security-definitions> --> Errors Rebilly follow's th

[![Connect-MCP](https://clawy.uk/mcp/badge/api%3Arebilly.com.svg)](https://clawy.uk/mcp/s/api%3Arebilly.com)