List charges in The SureVoIP RESTful
A documented The SureVoIP RESTful operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
List charges
- GETReads data · charges
api.surevoip.co.uk/charges
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which The SureVoIP RESTful operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other The SureVoIP RESTful operations
- Add a new announcement audio filePOST · changes data
- Create charges for invoicesPOST · changes data
- Create phone calls with or without announcementsPOST · changes data
- Delete an announcement audio fileDELETE · changes data
- Return your POSTed data for testingPOST · changes data
- List contactsGET · reads data
- List all customers or find your own accountGET · reads data
- List all Service Status messagesGET · reads data
Questions
- Can HumDay list charges in The SureVoIP RESTful?
- Yes. This operation is published in The SureVoIP RESTful'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 The SureVoIP RESTful account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in The SureVoIP RESTful.
- 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 The SureVoIP RESTful account.
Where this came from
Read from a published API description for The SureVoIP RESTful at raw.githubusercontent.com/SureVoIP/API-Specification/master/openapi/openapi.yaml. The description above is the provider’s own wording, not ours. Last published 2021-07-11.