Status check in Idtbeyond Active Documentation for /
A documented Idtbeyond Active Documentation for / 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
Status check
- GETReads data · utilities
api.idtbeyond.com/status
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 Idtbeyond Active Documentation for / 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 Idtbeyond Active Documentation for / operations
- Search topups transactionsPOST · changes data
- Topup a mobile phonePOST · changes data
- Reversal of a TopupPOST · changes data
- List of account topups in JSONGET · reads data
- List of account charges in JSONGET · reads data
- Get a list of products in JSON formatGET · reads data
- Account balanceGET · reads data
- Mobile number validationGET · reads data
Questions
- Can HumDay status check in Idtbeyond Active Documentation for /?
- Yes. This operation is published in Idtbeyond Active Documentation for /'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 Idtbeyond Active Documentation for / account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Idtbeyond Active Documentation for /.
- 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 Idtbeyond Active Documentation for / account.
Where this came from
Read from a published API description for Idtbeyond Active Documentation for / at app.idtbeyond.com/swagger/spec-08ef3dc298.json. The description above is the provider’s own wording, not ours. Last published 2018-02-05.