Get bundle metadata in .clarify.io
A documented .clarify.io 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 bundle metadata
- GETReads data · bundles
api.clarify.io/v1/bundles/{bundle_id}/metadata
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 .clarify.io 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 .clarify.io operations
- Create a bundlePOST · changes data
- Add a track for a bundlePOST · changes data
- Delete a bundleDELETE · changes data
- Update a bundlePUT · changes data
- Add media to a trackPUT · changes data
- Delete bundle tracksDELETE · changes data
- Update a tracks for a bundlePUT · changes data
- Request an insight to be runPOST · changes data
Questions
- Can HumDay get bundle metadata in .clarify.io?
- Yes. This operation is published in .clarify.io'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 .clarify.io account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in .clarify.io.
- 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 .clarify.io account.
Where this came from
Read from a published API description for .clarify.io at api.clarify.io/api-docs. The description above is the provider’s own wording, not ours. Last published 2019-01-03.