Brex

App

Brex

Summary:

Brex linked_accounts returns 403 after reconnect; suspected missing OAuth scope

Details:

Hi Pipedream team,

We use Pipedream Connect for Town’s Brex integration (workspace: town). A customer reports a 403 when accessing linked_accounts. They have already reconnected Brex, but the issue persists; they report that the needed linked-account permission is not offered on the consent screen.

Our initial investigation points to a possible scope gap in the shared Pipedream Brex OAuth client. This is a hypothesis for your team to confirm, not a verified diagnosis of the granted token scopes.

Could you please:

1. Confirm whether your Brex OAuth integration requests/supports linked_accounts.readonly, and whether its absence explains this 403.
2. If missing, advise whether you can add support, any Brex approval needed, and the expected timeline.
3. Confirm the exact OAuth scope and any other prerequisites for POST /v1/incoming_transfers (inbound ACH debit from a linked account), and whether the shared Brex OAuth client supports that endpoint. This related capability has not been verified live.
4. Explain how existing connected users should reauthorize after any scope update, and whether a custom OAuth client is required or recommended as a workaround.

The impact is that the customer cannot complete their linked-account workflow in Town. An earlier, separate Idempotency-Key issue was addressed in our application; this request concerns the subsequent authorization failure.

We have not attached credentials, customer financial data, or raw logs. Please let us know which non-secret diagnostic identifiers would help you investigate.

Thanks, George Town

Screenshots:

No screenshots included