Create a Draft Registration in OSF APIv2 Documentation

What this operation does

Create a Draft Registration

• POSTChanges data · Draft Registrationsapi.test.osf.io/draft_registrations/

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 OSF APIv2 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 OSF APIv2 Documentation operations

• Create a new Schema ResponsePOST · changes data
• Create a commentPOST · changes data
• Update a filePATCH · changes data
• Update a userPATCH · changes data
• Delete a commentDELETE · changes data
• Update a commentPUT · changes data
• Create a nodePOST · changes data
• Create a preprintPOST · changes data

All 156 OSF APIv2 Documentation operations

Questions

Can HumDay create a draft registration in OSF APIv2 Documentation?

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

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

Where this came from

Read from a published API description for OSF APIv2 Documentation at developer.osf.io/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.