Get usage statistics per user in I CUE Growth

What this operation does

Get usage statistics per user

• GETReads data · Reporting and Monitoring/report/user

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 I CUE Growth 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 I CUE Growth operations

• Map from old product to new product to create artifical historyPOST · changes data
• Map from old product to new product to create artifical historyPOST · changes data
• Calculate economic order quantityPOST · changes data
• Calculate lead time demandPOST · changes data
• Calculate minimum order quantityPOST · changes data
• Register new forecasting modelPOST · changes data
• Issue a tokenPOST · changes data
• Create organizationPOST · changes data

All 64 I CUE Growth operations

Questions

Can HumDay get usage statistics per user in I CUE Growth?

Yes. This operation is published in I CUE Growth'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 I CUE Growth account?

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

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 I CUE Growth account.

Where this came from

Read from a published API description for I CUE Growth at api.i-cue.solutions/swagger/v1/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.