Accept / Reject a Quote in Noosh application
A documented Noosh application 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
Accept / Reject a Quote
- PUTChanges data · Quote
example.com/v1/workgroups/{workgroup_id}/projects/{project_id}/quotes/{quote_id}
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 Noosh application 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 Noosh application operations
- Upload Profile Image. A multipart/form-data requestPOST · changes data
- Create a new taskPOST · changes data
- Upload File to ProjectPOST · changes data
- Create a ProjectPOST · changes data
- Create Exchange RatesPOST · changes data
- Create a quick buy orderPOST · changes data
- Update a specific WorkgroupPUT · changes data
- Create a RFEPOST · changes data
Questions
- Can HumDay accept / reject a quote in Noosh application?
- Yes. This operation is published in Noosh application'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 Noosh application data?
- Yes — this is a PUT operation, so it changes something in Noosh application. 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 Noosh application account.
Where this came from
Read from a published API description for Noosh application at api.noosh.com/api/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.