Authentication
users
transfers
payout-links
payments
payment-intents
payment-customers
checkout-sessions
accounts-payable
- GETList all vendors
- POSTCreate a vendor
- GETGet vendor details
- DELDelete a vendor
- GETList all payment methods for a vendor
- POSTCreate a payment method for a vendor
- GETGet vendor payment method details
- DELDelete a vendor payment method
- GETList all payables
- POSTCreate a payable
- POSTCreate a payable from a file
- GETGet payable details
- PATCHUpdate a payable
- POSTUpload file to the payable
- DELDelete file from the payable
- POSTCancel a payable
- POSTSubmit a payable for approval
- POSTApprove a payable
- POSTReject a payable
- POSTPay a payable
- GETList all approval policies
- POSTCreate an approval policy
- DELDelete an approval policy
- PATCHUpdate priority of an approval policy
- GETList all approvers for api app
apps
- GETList all Apps
- POSTCreate an App
- GETRetrieve an App
- GETRetrieve an App's Compliance Information
- PUTUpdate an App's Compliance Information
- GETGet App ACH Account
- PUTAdd App ACH Account
- POSTDeposit Funds into App Wallet
- POSTWithdraw Funds From App Wallet
- POSTRefresh compliance flow
- POSTUpdate an application's settings
payment-methods
Authentication
Requests are authorized with a Basic token which requires a client_id
and an api_key
.
The Basic token is the URL-safe Base64 encoding of a string which contains your client_id
followed by a :
for client side requests and your client_id
and your api_key
separated by a colon for server side requests.
Header format:
Authorization: Basic {token}
Client Side Requests
Token format:
BASE64_ENCODE({client_id}):
Example:
ABC123 -> QUJDMTIzOg==
Server Side Requests
Token format:
BASE64_ENCODE({client_id}:{api_key})
Example:
ABC123:DEF456 -> QUJDMTIzOkRFRjQ1Ng==
Was this page helpful?
On this page