Visitor History is stored on the server with every request in Miataru

What this operation does

Visitor History is stored on the server with every request to the location or location history information of a device.

• POSTChanges data · getVisitorHistoryservice.miataru.com/GetVisitorHistory

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 Miataru operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Miataru operations

• To retrieve a specific devices latest known location thePOST · changes data
• This method is used to update the location of a devicePOST · changes data
• Location History is stored on the server onlyPOST · changes data
• Retrieves a devices Location in GeoJSON formatGET · reads data

All 5 Miataru operations

Questions

Can HumDay visitor history is stored on the server with every request in Miataru?

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

Will this change my Miataru data?

Yes — this is a POST operation, so it changes something in Miataru. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

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 Miataru account.

Where this came from

Read from a published API description for Miataru at raw.githubusercontent.com/miataru/miataru-protocol-specification/swagger/miataru-v1/api/sw. The description above is the provider’s own wording, not ours. Last published 2021-06-21.