Introduction

Welcome to the Frisbii Billing and Pay API documentation.

Frisbii offers a powerful REST-based API designed with predictable, resource-oriented URLs and standard HTTP response codes for clear error signaling. Our platform enables seamless integration of subscription billing, payments, and customer lifecycle automation.

As part of our rebranding from Reepay to Frisbii, the API is now available at both api.reepay.com and api.frisbii.com. Learn more about our API domains
We recommend migrating to api.frisbii.com. Learn more in our Rebranding Overview.

About the API Specification

The Frisbii Billing and Pay API is formally defined using the OpenAPI 3.0 Specification (Learn more), a widely adopted standard that supports a rich ecosystem of tools including:

• Interactive user interfaces
• Code generation libraries
• Automated testing and documentation

We provide the OpenAPI specification as a reference tool, but caution against directly generating client code from it. Automatically generated clients often:

• Include excessive operations and unused fields
• Create complex, rigid code that is hard to test or maintain
• May break when new optional fields or enums are introduced

Instead, we encourage developers to write custom integrations based on actual business needs and selectively implement required endpoints.

Frisbii Billing and Pay OpenAPI Resources

• API Specification (YAML/JSON) – The raw OpenAPI schema for developers
• API Explorer – Interactive UI for testing endpoints using your private API key - or use the API tools inside this documentation

Usage Examples

Practical examples for integrating with the API can be found in our Examples section,e.g.

• Simple subscription handling
• On-demand billing

If you need help getting started, visit our practical guides like

• New webshop
• New subscription business
  or reach out via [email protected].