Brex Integration
Connect your Brex account to enable expense management, card controls, and financial workflows.
Prerequisites
Before setting up the Brex integration, you’ll need:
- A Brex account with admin access
- Account admin or card admin permissions to generate API tokens
Getting Your API Token
Brex uses user tokens to authenticate API requests. Tokens are passed as Bearer tokens in the Authorization header.
Creating a User Token
- Sign in to your Brex Dashboard
- Navigate to Settings → Developer
- Click Create Token
- Enter a descriptive name for the token (e.g., “Serval Integration”)
- Select the required permissions (scopes) for your use case:
- Users: Read access for user management
- Cards: Read access for card information
- Transactions: Read access for transaction history
- Departments: Read access for department data
- Click Allow Access
- Important: Copy and save the token immediately — it won’t be shown again
For detailed instructions, see the Brex Authentication Documentation.
Available Scopes
When creating a token, you’ll see all available permission scopes organized by category:
Brex API token creation showing available scopes
Read vs Write Permissions
Read-only scopes are required for the Serval integration to function. If you want to perform actions (such as creating users, managing cards, or processing payments), you will need to grant Write or Read/Write scopes for the relevant resources.
| Permission Level | Description |
|---|
| None | No access to the resource |
| Read | View-only access (required for healthchecks and data sync) |
| Read/Write | Full access to view and modify the resource |
Recommended Scopes
At minimum, grant Read access to these scopes for the integration to work:
| Category | Scope | Permission | Description |
|---|
| Team | Users | Read | View user information |
| Team | Departments | Read | View department data |
| Team | Cards | Read | View card details |
| Transactions | Card Accounts | Read | View card account information |
Connecting Brex
- In Serval, navigate to Applications and select your application
- Go to the API Integration tab
- Search for and select Brex
- Enter your Brex API Token
- Click Save
Token Management
Token Expiration
User tokens expire automatically if not used for 90 days. To avoid disruption:
- Monitor token usage in the Brex Developer settings
- Regenerate tokens before they expire
- Set up reminders to rotate tokens periodically
Revoking Tokens
If you suspect a token has been compromised:
- Go to Settings → Developer in the Brex Dashboard
- Find the token you want to revoke
- Click Revoke to immediately disable the token
- Generate a new token and update your integration
Security Best Practices
- Protect your token: Treat API tokens like passwords — never expose them in client-side code or public repositories
- Use minimal permissions: Only grant the scopes your integration actually needs
- Monitor usage: Regularly review API activity in the Brex Developer dashboard
- Rotate tokens: Periodically regenerate tokens to limit exposure from potential breaches
Healthchecks
After connecting, the following healthchecks verify your integration:
| Check | Description | Required Scope |
|---|
| List Users | Verifies access to user data | users.read |
| List Cards | Confirms access to card information | cards.read |
| List Card Accounts | Confirms access to card accounts | accounts.card.read |
| List Departments | Confirms access to department data | departments.read |
Troubleshooting
Invalid Token
- Ensure you’re using a valid user token
- Verify the token hasn’t expired (90 days of inactivity)
- Check that the token hasn’t been revoked
Permission Denied
- Verify your token has the required scopes for the operation
- Check that your Brex account has access to the requested resources
- Some features may require specific Brex plan tiers
Token Expired
- Tokens expire after 90 days of inactivity
- Generate a new token from the Brex Developer settings
- Update your integration with the new token
API Base URL
Brex API requests are made to:
- Standard API:
https://platform.brexapis.com
- Secure API (PCI compliant):
https://secure-platform.brexapis.com
Additional Resources
