API Launch Stages
At Brex, we are continuously building and improving our APIs to provide developers with powerful tools to integrate with our platform. To ensure transparency and manage expectations throughout the development lifecycle, we categorize our APIs into three distinct launch stages: Alpha, Beta, and General Availability (GA).
Understanding these stages helps you know what to expect in terms of stability, support, and access as you build with Brex APIs.
Overview of Launch Stages
- Alpha: These are early-stage APIs focused on exploration, feedback gathering, and co-design with a select group of partners. APIs in Alpha are subject to significant changes.
- Beta: These APIs are released more broadly for wider testing and feedback before full release. They are functional but may still undergo backward-incompatible changes as we refine them based on user input.
- General Availability (GA): These are stable, fully supported, and production-ready APIs intended for widespread use. GA APIs adhere to stricter stability commitments.
Launch Stage Details
| Feature | Alpha | Beta | General Availability (GA) |
|---|---|---|---|
| Purpose | Validate concepts, gather early feedback, co-design with partners. | Gather broader feedback, test scalability, prepare for stabilization. | Provide stable, reliable, and fully supported APIs for all customers. |
| Target Audience | Select early design partners & customers. | All interested Brex customers (opt-in required). | All Brex customers. |
| Access | Invitation-based, see "Requesting Access" below. | Self-serve opt-in required, see "Requesting Access" below. | Available by default to all Brex customers. |
| API Documentation | Publicly available on developers.brex.com. Version numbers will include an "-alpha" suffix (e.g., 1.0.0-alpha). |
Publicly available on developers.brex.com. Version numbers will include a "-beta" suffix (e.g., 1.0.0-beta). |
Publicly available on developers.brex.com. |
| Stability | Unstable: Expect frequent and potentially backward-incompatible changes. | Moderately Stable: Functionally usable, but backward-incompatible changes are possible before GA. | Stable: Reliable for production use. Committed to backward compatibility via versioning. |
| Change Management | Breaking changes may occur. We provide at least 15 days' notice via email and documentation updates. | Breaking changes may occur. We provide at least 60 days' notice via email and documentation updates. | Breaking changes are handled by releasing new API versions alongside clear deprecation timelines for older versions. |
| Support | Direct collaboration with Brex product and engineering teams. | Standard Brex support channels. | Standard Brex support channels. |
| Intended Use | Testing, evaluation, and feedback. Limited production use only for designated co-design partners. | Suitable for production use, but developers should be aware of potential changes and plan accordingly. | Recommended for all production use cases. |
Requesting Access to Alpha and Beta APIs
- Alpha APIs: Access to Alpha APIs is typically by invitation as we work closely with a small group of design partners. If you are interested in participating in an Alpha program, please email developer-support@brex.com to express your interest. Please note that participation is determined by Brex based on program needs.
-
Beta APIs:
To use a Beta API, you must explicitly opt-in. This can be done via the
Beta Features
page within the
Company Settings
section of your Brex dashboard.
Opting in confirms your acknowledgment that the API is still under development and may change.
Why Opt-in for Beta?
Requiring customers to explicitly opt-in to use Beta APIs ensures awareness. By opting in, you acknowledge that the API is still under development and may change before its General Availability release. This helps you make informed decisions about integrating Beta APIs into your workflows.
Our Commitment
These launch stages allow us to innovate rapidly while providing clear expectations to our developer community. We aim to move APIs through these stages efficiently, incorporating your valuable feedback to build robust and reliable tools. All APIs, regardless of stage, will have their specifications published on https://developers.brex.com, clearly indicating their current status via versioning suffixes or GA status.