Add media to a track in .clarify.io
A documented .clarify.io operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Add media to a track
- PUTChanges data · bundles
api.clarify.io/v1/bundles/{bundle_id}/tracks/{track_id}
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. Because this one changes data, it cannot run until you have explicitly granted it.
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
- Delete bundle tracksDELETE · changes data
- Update a tracks for a bundlePUT · changes data
- Request an insight to be runPOST · changes data
- Delete bundle metadataDELETE · changes data
Questions
- Can HumDay add media to a track 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.
- Will this change my .clarify.io data?
- Yes — this is a PUT operation, so it changes something in .clarify.io. 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 .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.