Brex integration: operations for AI agents
Brex connects to Type.com as an integration. This page lists the 115 operations documented for Claude and Codex in Type.com: 60 read, 45 write, 10 destructive.
About Brex
Brex reference qualified by managed OAuth grants, documented legacy-host compatibility, partner-only onboarding, financial permissions and upload restrictions.
Categories: Finance & Accounting
How to connect Brex to Type.com
- Connect
- Managed OAuth through Pipedream when enabled for your workspace
- Access
- Organization connection: one shared account for the workspace.
- MCP
- Selected payment-processing operations are not available through Type’s MCP server. Other operations remain available through MCP, subject to your connection’s permissions. These MCP restrictions do not apply within Type.
To add the connection, follow the steps in Space connections.
Documented operations
115 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
115 operations listed.
Accounting Integrations
- Write
Create accounting integration
Create a new accounting integration. The behavior depends on the existing active integration: - If no active integration exists: Creates and returns new integration - If active integration exists with same vendor and vendor_account_id: Returns the existing active integration - If active integration exists with same vendor but different vendor_account_id: Returns 409 error - If active integration exists with different vendor: Returns 409 error This ensures only one active integration exists per account.
POST /v3/accounting/integration - Write
Reactivate accounting integration
Reactivate a disconnected accounting integration. - If integration is DISABLED: Reactivates and returns success - If integration ID doesn't exist: Returns 404 error - If an active integration already exists: Returns 409 error
POST /v3/accounting/integration/{integration_id}/reactivate - Destructive
Disconnect accounting integration
Disconnect an active accounting integration. - If integration is ACTIVE: Disconnects and returns success - If integration ID doesn't exist: Returns 404 error - If integration is not currently active: Returns 409 error
POST /v3/accounting/integration/{integration_id}/disconnect
Accounting Records
- Read
Get accounting record by ID
Retrieve a single accounting record by its unique identifier
GET /v3/accounting/records/{record_id} - Read
Query accounting records
Query accounting records by IDs or with filters for polling. When building integrations with Brex accounting workflow, use filter-based polling as a fallback mechanism. Suggested cadence is 1 hour. **For card and reimbursement records:** Use `review_status` to filter by accounting workflow stage (e.g., READY_FOR_EXPORT, EXPORTED). **For bill records:** Use `source_type=BILL` with `updated_at[gt]` to poll for updated bill records. **Filter Constraints:** - `review_status` is only supported with CARD and REIMBURSEMENT source types
GET /v3/accounting/records - Write
Report accounting export results
Report export success or failure for accounting records.
POST /v3/accounting/records/export-results
Budget Programs
- Read
List Budget Programs
Lists Budget Programs belonging to this account
GET /v1/budget_programs - Read
Get Budget Program
Retrieves a Budget Program by ID
GET /v1/budget_programs/{id}
Spend Limits (v1)
- Read
List Spend Limits
Lists Spend Limits belonging to this account
GET /v1/budgets - Read
Get Spend Limit
Retrieves a Spend Limit by ID
GET /v1/budgets/{id} - Write
Create Spend Limit
Creates a Spend Limit
POST /v1/budgets - Write
Update Spend Limit
Updates a Spend Limit
PUT /v1/budgets/{id} - Write
Archive a Spend Limit
Archives a Spend Limit, making it unusable for future expenses and removing it from the UI
POST /v1/budgets/{id}/archive
Budgets
- Read
List Budgets
Retrieves a list of Budgets
GET /v2/budgets - Read
Get Budget
Retrieves a Budget by ID
GET /v2/budgets/{id} - Write
Create Budget
Creates a Budget
POST /v2/budgets - Write
Update Budget
Updates a Budget
PUT /v2/budgets/{id} - Write
Archive a Budget
Archives a Budget, making any Spend Limits beneath it unusable for future expenses and removing it from the UI
POST /v2/budgets/{id}/archive
Spend Limits (v2)
- Read
List Spend Limits
Retrieves a list of Spend Limits
GET /v2/spend_limits - Read
Get Spend Limit
Retrieves a Spend Limit by ID
GET /v2/spend_limits/{id} - Write
Create Spend Limit
Creates a Spend Limit
POST /v2/spend_limits - Write
Update Spend Limit
Updates a Spend Limit
PUT /v2/spend_limits/{id} - Write
Archive a Spend Limit
Archives a Spend Limit, making it unusable for future expenses and removing it from the UI
POST /v2/spend_limits/{id}/archive
Expenses
- Read
List expenses
List expenses under the same account. Admin and bookkeeper have access to any expense, and regular users can only access their own.
GET /v1/expenses - Read
Get an expense
Get an expense by its ID.
GET /v1/expenses/{id}
Receipt Match
- Write
Create a new receipt match
The `uri` will be a pre-signed S3 URL allowing you to upload the receipt securely. This URL can only be used for a `PUT` operation and expires 30 minutes after its creation. Once your upload is complete, we will try to match the receipt with existing expenses. Refer to these [docs](https://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlUploadObject.html) on how to upload to this pre-signed S3 URL. We highly recommend using one of AWS SDKs if they're available for your language to upload these files.
POST /v1/expenses/card/receipt_match
Card Expenses
- Read
List card expenses (deprecated)
This endpoint is deprecated. Use the "List expenses" (`GET /v1/expenses`) endpoint instead.
GET /v1/expenses/card - Read
Get a card expense (deprecated)
This endpoint is deprecated. Use the "Get an expense" (`GET /v1/expenses/{id}`) endpoint instead.
GET /v1/expenses/card/{expense_id} - Write
Update an expense
Update an expense. Admin and bookkeeper have access to any expense, and regular users can only access their own.
PUT /v1/expenses/card/{expense_id}
Receipt Upload
- Write
Create a new receipt upload
The `uri` will be a pre-signed S3 URL allowing you to upload the receipt securely. This URL can only be used for a `PUT` operation and expires 30 minutes after its creation. Once your upload is complete, we will try to match the receipt with existing expenses. Refer to these [docs](https://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlUploadObject.html) on how to upload to this pre-signed S3 URL. We highly recommend using one of AWS SDKs if they're available for your language to upload these files.
POST /v1/expenses/card/{expense_id}/receipt_upload
Fields
- Read
List custom fields
List custom fields under the same account
GET /v1/fields - Read
Get custom field
Get a custom field by Brex ID
GET /v1/fields/{id} - Write
Create a custom field
Create a custom field
POST /v1/fields - Write
Update a custom field
Update a field by ID
PUT /v1/fields/{id} - Destructive
Delete a custom field
Delete a custom field by Brex ID
DELETE /v1/fields/{id}
Field Values
- Read
List custom field values
List values under the same custom field
GET /v1/fields/{field_id}/values - Read
Get a field value
Get a field value by field ID and field value ID
GET /v1/fields/{field_id}/values/{brex_id} - Write
Create custom field values
Create custom field values (up to 1000 values at once) for a specific field
POST /v1/fields/{field_id}/values - Write
Update custom field values
Update custom field values (up to 1000 values at once) for a specific field
PUT /v1/fields/{field_id}/values - Destructive
Delete custom field values
Delete custom field values (up to 1000 values at once) for a specific field
DELETE /v1/fields/{field_id}/values
Referrals
- Read
List referrals
Returns referrals created. *Note*: This doesn't include referrals that have expired.
GET /v1/referrals - Read
Gets a referral by ID
Returns a referral object by ID if it exists.
GET /v1/referrals/{id} - Write
Creates a referral
This creates new referrals. The response will contain an identifier and a unique personalized link to an application flow. Many fields are optional and when they're provided they'll prefill the application flow for Brex. You should handle and store these references securely as they contain sensitive information about the referral.
POST /v1/referrals - Write
Create a new document upload
The `uri` will be a presigned S3 URL allowing you to upload the referral doc securely. This URL can only be used for a `PUT` operation and expires 30 minutes after its creation. Once your upload is complete, we will use this to prefill the application. Refer to these [docs](https://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrlUploadObject.html) on how to upload to this presigned S3 URL. We highly recommend using one of AWS SDKs if they're available for your language to upload these files.
POST /v1/referrals/{id}/document_upload - Write
Process a delayed EIN document after upload
Processes a delayed EIN document after it has been uploaded. This endpoint should be called after successfully uploading an IRS EIN Confirmation document (CP-575, CP-575 fax sheet, or 147C) using the standard document upload flow (`/v1/referrals/{id}/document_upload` with `type: IRS_EIN_CONFIRMATION`). The `document_id` should be the `id` returned from the document upload request.
POST /v1/referrals/{id}/process_ein_document
Transfers
- Read
Lists transfers
This endpoint lists existing transfers for an account. Currently, the API can only return transfers for the following payment rails: - ACH - DOMESTIC_WIRE - CHEQUE - INTERNATIONAL_WIRE
GET /v1/transfers - Read
Get transfer
This endpoint gets a transfer by ID. Currently, the API can only return transfers for the following payment rails: - ACH - DOMESTIC_WIRE - CHEQUE - INTERNATIONAL_WIRE
GET /v1/transfers/{id} - Write
Create incoming transfer
This endpoint creates a new incoming transfer. You may use use any eligible bank account connection to fund (ACH Debit) any active Brex business account. **Reminder**: You may not use the Brex API for any activity that requires a license or registration from any governmental authority without Brex's prior review and approval. This includes but is not limited to any money services business or money transmission activity. Please review the <a href="https://www.brex.com/legal/developer-portal/">Brex Access Agreement</a> and contact us if you have any questions.
POST /v1/incoming_transfers - Write
Create transfer
This endpoint creates a new transfer. Currently, the API can only create transfers for the following payment rails: - ACH - DOMESTIC_WIRE - CHEQUE - INTERNATIONAL_WIRES **Transaction Descriptions** * For outgoing check payments, a successful transfer will return a response containing a description value with a format of `Check #<check number> to <recipient_name> - <external_memo>`. * For book transfers (from one Brex Business account to another), the recipient value will have a format of `<customer_account.dba_name> - <external_memo>` and the sender will have a format of `<target customer account's dba name> - <external_memo>`. * For other payment rails, the format will be `<counterparty_name> - <external_memo>`, where Counterparty name is `payment_instrument.beneficiary_name` or `contact.name` For vendors created from the Payments API, the `counterparty_name` will be the `company_name` [field](/openapi/payments_api/#operation/createVendor!path=company_name&t=request). **Reminder**: You may not use the Brex API for any activity that requires a license or registration from any governmental authority without Brex's prior review and approval. This includes but is not limited to any money services business or money transmission activity. Please review the <a href="https://www.brex.com/legal/developer-portal/">Brex Access Agreement</a> and contact us if you have any questions.
POST /v1/transfers
Linked Accounts
- Read
Lists linked accounts
This endpoint lists all bank connections that are eligible to make ACH transfers to Brex business account
GET /v1/linked_accounts
Vendors
- Read
Lists vendors
This endpoint lists all existing vendors for an account. Takes an optional parameter to match by vendor name.
GET /v1/vendors - Read
Get vendor
This endpoint gets a vendor by ID.
GET /v1/vendors/{id} - Write
Create vendor
This endpoint creates a new vendor.
POST /v1/vendors - Write
Update vendor
Updates an existing vendor by ID.
PUT /v1/vendors/{id} - Destructive
Delete vendor.
This endpoint deletes a vendor by ID.
DELETE /v1/vendors/{id}
Cards
- Read
List cards
Lists all cards by a `user_id`. Only cards with `limit_type = CARD` have `spend_controls`
GET /v2/cards - Read
Get card
Retrieves a card by ID. Only cards with `limit_type = CARD` have `spend_controls`
GET /v2/cards/{id} - Read
Get card number
Retrieves card number, CVV, and expiration date of a card by ID.
GET /v2/cards/{id}/pan - Write
Create card
Creates a new card. The `spend_controls` field is required when `limit_type` = `CARD`. The `mailing_address` field is required for physical cards and is the shipping address used to send the card; it is not the same as the billing and mailing address used for online purchases. The first 2 lines of this address must be under 60 characters long. Each user can only have up to 10 active physical cards. For Empower accounts, this endpoint requires budget management. If your account does not have access to budget management features, a 403 response status will be returned. If this is the case and you want to gain access to this endpoint, please contact Brex support.
POST /v2/cards - Write
Update card
Update an existing vendor card
PUT /v2/cards/{id} - Write
Lock card
Locks an existing, unlocked card. And the card owner will receive a notification about it.
POST /v2/cards/{id}/lock - Write
Create secure email to send card number
Creates a secure email to send card number, CVV, and expiration date of a card by ID to the specified email. This endpoint is currently gated. If you would like to request access, please reach out to developer-support@brex.com
POST /v2/cards/{id}/secure_email - Write
Unlock card
Unlocks an existing card.
POST /v2/cards/{id}/unlock - Destructive
Terminate card
Terminates an existing card. The card owner will receive a notification about it.
POST /v2/cards/{id}/terminate
Companies
- Read
Get company
This endpoint returns the company associated with the OAuth2 access token.
GET /v2/company
Cost Centers
- Read
List cost centers
This endpoint lists all cost centers.
GET /v2/cost_centers - Read
Get cost center
This endpoint gets a cost center by ID.
GET /v2/cost_centers/{id}
Departments
- Read
List departments
This endpoint lists all departments.
GET /v2/departments - Read
Get department
This endpoint gets a department by ID.
GET /v2/departments/{id} - Write
Create department
This endpoint creates a new department
POST /v2/departments - Write
Update department
This endpoint updates a department by ID. Only the fields present in the request body are changed.
PUT /v2/departments/{id} - Destructive
Delete department
This endpoint deletes a department by ID. A department cannot be deleted while users are still assigned to it or while it is used as a filter on an active group.
DELETE /v2/departments/{id}
Legal Entities
- Read
List legal entities
List legal entities for the account.
GET /v2/legal_entities - Read
Get legal entity
Get a legal entity by its ID.
GET /v2/legal_entities/{id}
Locations
- Read
List locations
This endpoint lists all locations.
GET /v2/locations - Read
Get location
This endpoint gets a location by ID.
GET /v2/locations/{id} - Write
Create location
This endpoint creates a new location.
POST /v2/locations - Write
Update location
This endpoint updates a location by ID. Only the fields present in the request body are changed.
PUT /v2/locations/{id} - Destructive
Delete location
This endpoint deletes a location by ID. A location cannot be deleted while users are still assigned to it or while it is used as a filter on an active group.
DELETE /v2/locations/{id}
Titles
- Read
List titles
This endpoint lists all titles.
GET /v2/titles - Read
Get title
This endpoint gets a title by ID.
GET /v2/titles/{id} - Write
Create title
This endpoint creates a new title
POST /v2/titles - Write
Update title
This endpoint updates a title by ID. Only the fields present in the request body are changed. The request must contain at least one field to update.
PUT /v2/titles/{id} - Destructive
Delete title
This endpoint deletes a title by ID. A title cannot be deleted while users are still assigned to it or while it is used as a filter on an active group.
DELETE /v2/titles/{id}
Users
- Read
List users
This endpoint lists all users. Results can be narrowed with the filter query parameters below. Values within a single filter are OR-ed, and separate filters are AND-ed together. Filters that accept multiple values take them either as a comma-separated list or as a repeated parameter: `?status[]=ACTIVE,INVITED` and `?status[]=ACTIVE&status[]=INVITED` are equivalent. The legacy singular `email` and `remote_display_id` parameters perform an exact lookup that returns at most one user, and cannot be combined with the filters above.
GET /v2/users - Read
Get current user
This endpoint returns the user associated with the OAuth2 access token.
GET /v2/users/me - Read
Get user
This endpoint gets a user by ID.
GET /v2/users/{id} - Write
Invite user
This endpoint invites a new user as an employee. To update user's role, check out [this article](https://support.brex.com/how-do-i-change-another-user-s-role/).
POST /v2/users - Write
Create user
This endpoint creates a new user as an employee without inviting them, leaving the user `INACTIVE`. Use it to load your team into Brex ahead of time; invite them later with [Invite user](#tag/Users/operation/createUser), on the Dashboard, or by using auto-invite rules. The user is assigned to `legal_entity_id` when provided, and to your account's default legal entity otherwise.
POST /v2/users/create - Write
Update user
This endpoint updates a user. Any parameters not provided will be left unchanged.
PUT /v2/users/{id}
Accounts
- Read
List card accounts
This endpoint lists all accounts of card type.
GET /v2/accounts/card - Read
List primary card account statements.
This endpoint lists all finalized statements for the primary card account.
GET /v2/accounts/card/primary/statements - Read
List cash accounts
This endpoint lists all the existing cash accounts with their status.
GET /v2/accounts/cash - Read
Get primary cash account
This endpoint returns the primary cash account with its status. There will always be only one primary account.
GET /v2/accounts/cash/primary - Read
Get cash account by ID
This endpoint returns the cash account associated with the provided ID with its status.
GET /v2/accounts/cash/{id} - Read
List cash account statements.
This endpoint lists all finalized statements for the cash account by ID.
GET /v2/accounts/cash/{id}/statements
Transactions
- Read
List transactions for all card accounts.
This endpoint lists all settled transactions for all card accounts. Regular users may only fetch their own "PURCHASE","REFUND" and "CHARGEBACK" settled transactions. Note: there may be a small lag when fetching transactions with cursor and time ranges. It is important to have at least a 1+ day lookback when syncing transactions to ensure the delayed transactions are properly handled.
GET /v2/transactions/card/primary - Read
List transactions for the selected cash account.
This endpoint lists all transactions for the cash account with the selected ID.
GET /v2/transactions/cash/{id}
Trips
- Read
List trips
Lists trips according to the filters passed in the query string.
GET /v1/trips - Read
Get trip
Retrieves a trip by ID.
GET /v1/trips/{trip_id} - Read
List trip bookings
Lists the bookings within a trip.
GET /v1/trips/{trip_id}/bookings - Read
Get booking
Retrieves a booking by trip and booking ID.
GET /v1/trips/{trip_id}/bookings/{booking_id}
Webhook Subscriptions
- Read
List Webhooks
List the webhooks you have registered
GET /v1/webhooks - Read
List Webhook Secrets
This endpoint returns a set of webhook signing secrets used to validate the webhook. Usually only one key will be returned in the response. After key rotation, this endpoint will return two keys: the new key, and the key that will be revoked soon. There will also be two signatures in the 'Webhook-Signature' request header. Your application should use all keys available to validate the webhook request. If validation passes for any of the keys returned, the webhook payload is valid.
GET /v1/webhooks/secrets - Read
Get Webhook
Get details of a webhook
GET /v1/webhooks/{id} - Write
Register Webhook
Register an endpoint to start receiving selected webhook events
POST /v1/webhooks - Write
Update Webhook
Update a webhook. You can update the endpoint url, event types that the endpoint receives, or temporarily deactivate the webhook.
PUT /v1/webhooks/{id} - Destructive
Unregister Webhook
Unregister a webhook if you want to stop receiving webhook events
DELETE /v1/webhooks/{id}
Webhook Groups
- Read
List Webhook Groups
Lists webhook groups.
GET /v1/webhooks/groups - Read
Get Webhook Group
Gets a webhook group.
GET /v1/webhooks/groups/{id} - Read
List Webhook Group Members
Lists the members currently in the specified webhook group.
GET /v1/webhooks/groups/{id}/members - Write
Create Webhook Group
Creates a webhook group.
POST /v1/webhooks/groups - Write
Add Webhook Group Members
Adds members to webhook groups.
POST /v1/webhooks/groups/{id}/add_members - Write
Remove Webhook Group Members
Removes members from webhook groups.
POST /v1/webhooks/groups/{id}/remove_members - Destructive
Delete Webhook Group
Deletes a webhook group and all its members.
DELETE /v1/webhooks/groups/{id}
No operations match.
Get started
- Open Space settings → Connections and search for Brex.
- Connect your account and add the connection to the Space.
- Ask for what you need in any thread in that Space.
See How connections work for access and permissions, or browse all integrations.