Upload a logo in API .video
A documented API .video 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
Upload a logo
- POSTChanges data · Players
ws.api.video/players/{playerId}/logo
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 API .video 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 API .video operations
- Create WebhookPOST · changes data
- Upload with an upload tokenPOST · changes data
- Create a videoPOST · changes data
- Create a playerPOST · changes data
- Create live streamPOST · changes data
- Generate an upload tokenPOST · changes data
- Delete a WebhookDELETE · changes data
- Delete an upload tokenDELETE · changes data
Questions
- Can HumDay upload a logo in API .video?
- Yes. This operation is published in API .video'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 API .video data?
- Yes — this is a POST operation, so it changes something in API .video. 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 API .video account.
Where this came from
Read from a published API description for API .video at docs.api.video/openapi/5f0d4679158b8d006ea6f068. The description above is the provider’s own wording, not ours. Last published 2021-08-16.