Export Transactions in Velopayments Velo Payments

What this operation does

Export Transactions

• GETReads data · Payment Audit Serviceapi.sandbox.velopayments.com/v4/paymentaudit/transactions

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Velopayments Velo Payments operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Velopayments Velo Payments operations

• Invite a UserPOST · changes data
• Create WebhookPOST · changes data
• Delete a UserDELETE · changes data
• Update User Details for selfPOST · changes data
• Create a Payor LinkPOST · changes data
• Create Funding AccountPOST · changes data
• Enable a UserPOST · changes data
• Unlock a UserPOST · changes data

All 75 Velopayments Velo Payments operations

Questions

Can HumDay export transactions in Velopayments Velo Payments?

Yes. This operation is published in Velopayments Velo Payments's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my Velopayments Velo Payments account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Velopayments Velo Payments.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Velopayments Velo Payments account.

Where this came from

Read from a published API description for Velopayments Velo Payments at raw.githubusercontent.com/velopaymentsapi/VeloOpenApi/master/spec/openapi.yaml. The description above is the provider’s own wording, not ours. Last published 2023-03-06.