Schedule inbox reprocessing in Contract P Contract.fit
A documented Contract P Contract.fit 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
Schedule inbox reprocessing
- POSTChanges data · inboxes
/inboxes/{inbox_id}/reprocess
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 Contract P Contract.fit 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 Contract P Contract.fit operations
- Upload a new documentPOST · changes data
- Create a new tokenPOST · changes data
- Create a new API KeyPOST · changes data
- Create a new ephemeral tokenPOST · changes data
- Delete a userDELETE · changes data
- Upload a new doc to the inboxPOST · changes data
- Change the current user passwordPOST · changes data
- Create formatPOST · changes data
Questions
- Can HumDay schedule inbox reprocessing in Contract P Contract.fit?
- Yes. This operation is published in Contract P Contract.fit'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 Contract P Contract.fit data?
- Yes — this is a POST operation, so it changes something in Contract P Contract.fit. 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 Contract P Contract.fit account.
Where this came from
Read from a published API description for Contract P Contract.fit at cfportal.contract-p.fit/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.