Creates a multipart external upload in Discourse Documentation

What this operation does

Creates a multipart external upload

• POSTChanges data · Uploadsdiscourse.local/uploads/create-multipart.json

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 Discourse Documentation 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 Discourse Documentation operations

• Creates a new topic, a new post, or a private messagePOST · changes data
• Creates a userPOST · changes data
• Send password reset emailPOST · changes data
• Create an invitePOST · changes data
• Creates an uploadPOST · changes data
• Like a post and other actionsPOST · changes data
• Delete a single postDELETE · changes data
• Update a single postPUT · changes data

All 84 Discourse Documentation operations

Questions

Can HumDay creates a multipart external upload in Discourse Documentation?

Yes. This operation is published in Discourse Documentation'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 Discourse Documentation data?

Yes — this is a POST operation, so it changes something in Discourse Documentation. 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 Discourse Documentation account.

Where this came from

Read from a published API description for Discourse Documentation at docs.discourse.org/openapi.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.