Get snippet for a website in Journy Developer documentation
A documented Journy Developer documentation 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
Get snippet for a website
- GETReads data · Websites
api.journy.io/tracking/snippet
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 Journy Developer documentation 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 Journy Developer documentation operations
- Create or update userPOST · changes data
- Link web activity to userPOST · changes data
- Add users to an accountPOST · changes data
- Remove user from accountPOST · changes data
- Create or update accountPOST · changes data
- Delete accountDELETE · changes data
- Get user segmentsGET · reads data
- Get user propertiesGET · reads data
Questions
- Can HumDay get snippet for a website in Journy Developer documentation?
- Yes. This operation is published in Journy Developer documentation'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 Journy Developer documentation account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Journy Developer documentation.
- 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 Journy Developer documentation account.
Where this came from
Read from a published API description for Journy Developer documentation at api.journy.io/spec.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.