Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Brex API Update

Answered
Sam D'Arcy User

We received an update from Brex letting us know that they have updated their API - could we get our FT connector updated for this new API release?

What has been sent to me:

Brex team has updated that they have updated the api for getting the missing columns which are required for a report and they shared the new api for that.

https://developer.brex.com/openapi/expenses_api/#operation/getExpense

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Sanjeevv Maniram T Fivetranner

    Hi Sam,

    Thank you for reaching out and for bringing this important feature request to our attention. We appreciate your proactive communication about the recent Brex API update concerning the additional columns necessary for your reports.

    I want to let you know that we've added your request to our product backlog. We will prioritize this update based on overall demand and other factors. Rest assured, we understand the significance of having the most up-to-date connectors for our users.

    We are committed to keeping you informed about any developments regarding this feature. I will make sure to share any updates as soon as they become available.

    Thank you once again for your valuable feedback and support.

    Best regards,  
    Sanjeevv Maniram T

  • Daniel Moskowitz User

    to back this up, we are missing receipts from our expenses

     

    Fivetran is hitting /v1/expenses/card (deprecated endpoint) without expand[]=receipts, so receipts are never included. The correct endpoint per the current Brex API docs is /v1/expenses, and receipts are an opt-in expand field — they're omitted from the response unless explicitly requested with ?expand[]=receipts.

    Evidence:

    • /v1/expenses?expand[]=receipts&status[]=APPROVED → receipts come back populated (5 APPROVED expenses, all have receipt IDs)
    • /v1/expenses/card?expand[]=receipts (what Fivetran appears to use) → receipts always null
    • raw_brex.expense.receipts in BQ → 100% NULL across 12,471 rows

    Next steps: This is a Fivetran connector bug — file a ticket pointing to:

    1. They need to use GET /v1/expenses instead of /v1/expenses/card
    2. They need to pass expand[]=receipts (and optionally expand[]=receipts.download_uris for presigned S3 download links)

    Sources: