Automate Velopayments Velo Payments
HumDay reads Velopayments Velo Payments’s own published API description and derives 75 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Velopayments Velo Payments is
## Terms and Definitions Throughout this document and the Velo platform the following terms are used: * **Payor.** An entity (typically a corporation) which wishes to pay funds to one or more payees via a payout. * **Payee.** The recipient of funds paid out by a payor. * **Payment.** A single transfer of funds from a payor to a payee. * **Payout.** A batch of Payments, typically used by a payor to
API host: api.sandbox.velopayments.com
What HumDay can do in Velopayments Velo Payments
43 documented operations change something in Velopayments Velo Payments.
- POSTInvite a User
/v2/users/invite - POSTCreate Webhook
/v1/webhooks - DELETEDelete a User
/v2/users/{userId} - POSTUpdate User Details for self
/v2/users/self/userDetailsUpdate - POSTCreate a Payor Link
/v1/payorLinks - POSTCreate Funding Account
/v2/fundingAccounts - POSTEnable a User
/v2/users/{userId}/enable - POSTUnlock a User
/v2/users/{userId}/unlock - POSTDisable a User
/v2/users/{userId}/disable - POSTUpdate User Role
/v2/users/{userId}/roleUpdate - POSTWithdraw a Payment
/v1/payments/{paymentId}/withdraw - POSTUpdate User Details
/v2/users/{userId}/userDetailsUpdate - POSTUnregister MFA for the user
/v2/users/{userId}/mfa/unregister - POSTUpdate Webhook
/v1/webhooks/{webhookId} - POSTUpdate Password for self
/v2/users/self/password - POSTRegister SMS Number
/v2/users/registration/sms - POSTLogout
/v1/logout - POSTInitiate Payee Creation
/v4/payees - POSTSubmit Payout
/v3/payouts - POSTvalidate
/v1/validate - POSTAuthentication endpoint
/v1/authenticate - POSTResend a token
/v2/users/{userId}/tokens - POSTResend Payee Invite
/v4/payees/{payeeId}/invite - POSTCreate a quote for the payout
/v3/payouts/{payoutId}/quote - DELETEDeschedule a payout
/v3/payouts/{payoutId}/schedule - POSTSchedule a payout
/v3/payouts/{payoutId}/schedule - POSTCreate Application
/v1/payors/{payorId}/applications - POSTUnregister MFA for Self
/v2/users/self/mfa/unregister - POSTValidate the proposed password
/v2/users/self/password/validate - POSTReminder Email Opt-Out
/v1/payors/{payorId}/reminderEmailsUpdate - POSTReset password
/v1/password/reset - POSTCreate Funding Request
/v3/sourceAccounts/{sourceAccountId}/fundingRequest - POSTAdd Logo
/v1/payors/{payorId}/branding/logos - DELETEDelete Payee by Id
/v4/payees/{payeeId} - DELETEWithdraw Payout
/v3/payouts/{payoutId} - POSTInstruct Payout
/v3/payouts/{payoutId} - DELETEDelete a source account by ID
/v3/sourceAccounts/{sourceAccountId} - POSTUpdate Payee Remote Id
/v4/payees/{payeeId}/remoteIdUpdate - POSTUpdate Payee Details
/v4/payees/{payeeId}/payeeDetailsUpdate - POSTTransfer Funds between source accounts
/v3/sourceAccounts/{sourceAccountId}/transfers - POSTCreate API Key
/v1/payors/{payorId}/applications/{applicationId}/keys - POSTSet notifications
/v3/sourceAccounts/{sourceAccountId}/notifications - POSTUpdate ping
/v1/webhooks/{webhookId}/ping
What HumDay can read from Velopayments Velo Payments
These are the operations a schedule or a trigger can watch.
- GETList Payment Channel Country Rules
/v1/paymentChannelRules - GETList Users
/v2/users - GETGet User
/v2/users/{userId} - GETList Payees
/v4/payees - GETList the details about the webhooks for the given payor.
/v1/webhooks - GETList Payor Links
/v1/payorLinks - GETList Supported Currencies
/v2/currencies - GETGet list of source accounts
/v3/sourceAccounts - GETList Supported Countries
/v2/supportedCountries - GETGet Self
/v2/users/self - GETList Payee Changes
/v4/payees/deltas - GETGet details about the given webhook.
/v1/webhooks/{webhookId} - GETGet Funding Accounts
/v2/fundingAccounts - GETQuery Batch Status
/v4/payees/batch/{batchId} - GETRetrieve payments for a payout
/v3/payouts/{payoutId}/payments - GETGet Payor
/v2/payors/{payorId} - GETGet Payee by Id
/v4/payees/{payeeId} - GETGet Payout Summary
/v3/payouts/{payoutId} - GETGet Funding
/v1/fundings/{fundingId} - GETGet details about given source account.
/v3/sourceAccounts/{sourceAccountId} - GETGet Funding Account
/v2/fundingAccounts/{fundingAccountId} - GETGet Branding
/v1/payors/{payorId}/branding - GETList Payment Changes
/v4/payments/deltas - GETGet List of Payments
/v4/paymentaudit/payments - GETGet Payee Invitation Status
/v4/payees/payors/{payorId}/invitationStatus - GETGet Payments for Payout
/v4/paymentaudit/payouts/{payoutId} - GETGet Payment
/v4/paymentaudit/payments/{paymentId} - GETGet Payouts for Payor
/v4/paymentaudit/payouts - GETGet Fundings for Payor
/v4/paymentaudit/fundings - GETExport Transactions
/v4/paymentaudit/transactions - GETGet Payout Statistics
/v4/paymentaudit/payoutStatistics - GETGet Funding Audit Delta
/v1/deltas/fundings
How automating Velopayments Velo Payments works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Velopayments Velo Payments account.
- Grant access, then go live. You approve the specific Velopayments Velo Payments operations it may use — and only those.
Automate Velopayments Velo Payments with these
Categories
Questions about Velopayments Velo Payments automation
- Can HumDay connect to Velopayments Velo Payments?
- Yes. HumDay reads Velopayments Velo Payments's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 75 operations are documented.
- Do I need to write code to automate Velopayments Velo Payments?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Velopayments Velo Payments account.
- What can HumDay do in Velopayments Velo Payments?
- 43 of the 75 documented operations change something in Velopayments Velo Payments, and 32 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Velopayments Velo Payments account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Velopayments Velo Payments is held behind that approval.
Where this came from
The operations above are read from a published API description for Velopayments Velo Payments at raw.githubusercontent.com/velopaymentsapi/VeloOpenApi/master/spec/openapi.yaml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.