Create institution in user in PocketSmith

What this operation does

Create institution in user

• POSTChanges data · Institutionsapi.pocketsmith.com/users/{id}/institutions

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 PocketSmith 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 PocketSmith operations

• Create an account in userPOST · changes data
• Update the display order of accounts in userPUT · changes data
• Create event in scenarioPOST · changes data
• Create category in userPOST · changes data
• Create attachment in userPOST · changes data
• Delete eventDELETE · changes data
• Update eventPUT · changes data
• Delete forecast cache for userDELETE · changes data

All 56 PocketSmith operations

Questions

Can HumDay create institution in user in PocketSmith?

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

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

Where this came from

Read from a published API description for PocketSmith at raw.githubusercontent.com/pocketsmith/api/master/openapi.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.