Get details for the specified Shopper in OTE Godaddy Shoppers

What this operation does

Get details for the specified Shopper

• GETReads data · v1/v1/shoppers/{shopperId}/status

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 OTE Godaddy Shoppers 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 OTE Godaddy Shoppers operations

• Create a Subaccount owned by the authenticated ResellerPOST · changes data
• Request the deletion of a shopper profileDELETE · changes data
• Update details for the specified ShopperPOST · changes data
• Set subaccount's passwordPUT · changes data
• Get details for the specified ShopperGET · reads data

All 6 OTE Godaddy Shoppers operations

Questions

Can HumDay get details for the specified shopper in OTE Godaddy Shoppers?

Yes. This operation is published in OTE Godaddy Shoppers'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 OTE Godaddy Shoppers account?

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

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 OTE Godaddy Shoppers account.

Where this came from

Read from a published API description for OTE Godaddy Shoppers at developer.godaddy.com/swagger/swagger_shoppers.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.