Skip to content

Brex: Create vendor

Brex payments.paymentsCreateVendor: arguments, response, policy and SDK examples.

← Payments operations · Get started

Operation brex.payments_createvendor

Provider route: POST /v1/vendors. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/brex with npm, or alter-sdk-brex with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { BrexIntegration } from "@alter-ai/brex";
async function execute(input: Parameters<BrexIntegration["payments"]["paymentsCreateVendor"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new BrexIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.payments.paymentsCreateVendor(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_brex import BrexIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = BrexIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.payments.payments_create_vendor(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
headersobjectRequired within parentAdditional keys: not allowed
headers.Idempotency-KeystringRequired within parent
bodyModelRequired within parentExpand Create vendor — request body — body

Referenced models: Create vendor — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Get vendor — response body

Referenced models: Get vendor — response body

6 more schemas are linked from the tables above, on the schema pages.

Get vendor — response body
FieldTypePresenceDescription and constraints
$objectRoot
company_nameJSONOptional
company_name (anyOf 1)stringAlternative
company_name (anyOf 2)nullAlternative
emailJSONOptional
email (anyOf 1)stringAlternative
email (anyOf 2)nullAlternative
idstringRequired within parentVendor ID: Can be passed to /transfers endpoint to specify counterparty.
payment_accountsJSONOptional
payment_accounts (anyOf 1)arrayAlternative
payment_accounts (anyOf 1)[]ModelEach itemExpand Get vendor — response body — payment accounts array item
payment_accounts (anyOf 2)nullAlternative
phoneJSONOptional
phone (anyOf 1)stringAlternative
phone (anyOf 2)nullAlternative

Referenced models: Get vendor — response body — payment accounts array item

Create vendor — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
company_namestringRequired within parentName for vendor. The name must be unique.
emailJSONOptional
email (anyOf 1)stringAlternativeEmail for vendor.
Format: email
email (anyOf 2)nullAlternative
payment_accountsJSONOptional
payment_accounts (anyOf 1)arrayAlternativePayment accounts associated with the vendor.
payment_accounts (anyOf 1)[]ModelEach itemExpand Update vendor — request body — body payment accounts array item
payment_accounts (anyOf 2)nullAlternative
phoneJSONOptional
phone (anyOf 1)stringAlternativePhone number for vendor.
phone (anyOf 2)nullAlternative

Referenced models: Update vendor — request body — body payment accounts array item

Get vendor — response body — payment accounts array item
FieldTypePresenceDescription and constraints
$objectRoot
detailsModelRequired within parentExpand Get vendor — response body — payment accounts array item details

Referenced models: Get vendor — response body — payment accounts array item details

Update vendor — request body — body payment accounts array item
FieldTypePresenceDescription and constraints
$objectRoot
detailsModelRequired within parentExpand Update vendor — request body — body payment accounts array item details

Referenced models: Update vendor — request body — body payment accounts array item details

Get vendor — response body — payment accounts array item details
FieldTypePresenceDescription and constraints
$objectRootdiscriminator: {"mapping": {"ACH": "#/components/schemas/payments__ACHDetailsResponse", "CHEQUE": "#/components/schemas/payments__ChequeDetailsResponse", "DOMESTIC_WIRE": "#/components/schemas/payments__DomesticWireDetailsResponse", "INTERNATIONAL_WIRE": "#/components/schemas/payments__InternationalWireDetailsResponse"}, "propertyName": "type"}
$ (anyOf 1)ModelAlternativeExpand Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__ACHDetails Response
$ (anyOf 2)ModelAlternativeExpand Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__Domestic Wire Details Response
$ (anyOf 3)ModelAlternativeExpand Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__Cheque Details Response
$ (anyOf 4)ModelAlternativeExpand Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__International Wire Details Response

Referenced models: Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__ACHDetails Response, Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__Cheque Details Response, Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__Domestic Wire Details Response, Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__International Wire Details Response

Update vendor — request body — body payment accounts array item details
FieldTypePresenceDescription and constraints
$objectRootPayment Instruments associated with the vendor.
Each vendor can only have one payment account per payment instrument type. For instance, a vendor may have associated details for each of ACH, DOMESTIC_WIRE, and CHEQUE, but they cannot have 2 entries for ACH. If you modify a vendor's existing payment instrument type with new details, it will overwrite any previous data.

discriminator: {"mapping": {"ACH": "#/components/schemas/payments__ACHDetailsRequest", "CHEQUE": "#/components/schemas/payments__ChequeDetailsRequest", "DOMESTIC_WIRE": "#/components/schemas/payments__DomesticWireDetailsRequest"}, "propertyName": "type"}
$ (oneOf 1)ModelAlternativeExpand Update vendor — request body — body / payment_accounts / array / item / details / account_class: BUSINESS, PERSONAL, account type: CHECKING, SAVING, type: ACH, DOMESTIC WIRE, CHEQUE
$ (oneOf 2)ModelAlternativeExpand Update vendor — request body — body / payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE — payments__Domestic Wire Details Request
$ (oneOf 3)ModelAlternativeExpand Update vendor — request body — body / payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE — payments__Cheque Details Request

Referenced models: Update vendor — request body — body / payment_accounts / array / item / details / account_class: BUSINESS, PERSONAL, account type: CHECKING, SAVING, type: ACH, DOMESTIC WIRE, CHEQUE, Update vendor — request body — body / payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE — payments__Cheque Details Request, Update vendor — request body — body / payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE — payments__Domestic Wire Details Request

Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__ACHDetails Response
FieldTypePresenceDescription and constraints
$objectRoot
$ (allOf 1)objectAll variants apply
$ (allOf 2)JSONAll variants apply
$ (allOf 2).account_classJSONOptional
$ (allOf 2).account_class (anyOf 1)JSONAlternative
$ (allOf 2).account_class (anyOf 1) (allOf 1)stringAll variants applyKnown values: BUSINESS, PERSONAL
$ (allOf 2).account_class (anyOf 2)nullAlternative
$ (allOf 2).account_numberstringRequired within parent
$ (allOf 2).account_typeJSONOptional
$ (allOf 2).account_type (anyOf 1)JSONAlternative
$ (allOf 2).account_type (anyOf 1) (allOf 1)stringAll variants applyKnown values: CHECKING, SAVING
$ (allOf 2).account_type (anyOf 2)nullAlternative
$ (allOf 2).payment_instrument_idstringRequired within parentPayment Instrument ID that can be passed to the /transfers endpoint to trigger a transfer.
The type of the payment instrument dictates the method.
$ (allOf 2).routing_numberstringRequired within parent
$ (allOf 2).typestringRequired within parentKnown values: ACH, DOMESTIC_WIRE, CHEQUE, INTERNATIONAL_WIRE
Get vendor — response body — payment_accounts / array / item / details / type: ACH, DOMESTIC WIRE, CHEQUE, INTERNATIONAL WIRE — payments__Cheque Details Response
FieldTypePresenceDescription and constraints
$objectRoot
$ (allOf 1)objectAll variants apply
$ (allOf 2)JSONAll variants apply
$ (allOf 2).mailing_addressModelRequired within parentExpand Get card — response body — billing address
$ (allOf 2).payment_instrument_idstringRequired within parentPayment Instrument ID that can be passed to the /transfers endpoint to trigger a transfer.
The type of the payment instrument dictates the method.
$ (allOf 2).recipient_namestringRequired within parent
$ (allOf 2).typestringRequired within parentKnown values: ACH, DOMESTIC_WIRE, CHEQUE, INTERNATIONAL_WIRE

Referenced models: Get card — response body — billing address

SDK function policy ID: brex.payments_createvendor. Catalog operation: payments:createVendor. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["vendors"]

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.