Update queries in Semantria
A documented Semantria 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
Update queries
- PUTChanges data · Queries
api.semantria.com/queries.{content_type}
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 Semantria 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 Semantria operations
- Add user entitiesPOST · changes data
- Add items to blacklistPOST · changes data
- Add user categoriesPOST · changes data
- Create user configurationsPOST · changes data
- Add sentiment-bearing phrasesPOST · changes data
- Add or update queriesPOST · changes data
- Queue document for analysisPOST · changes data
- Remove user entitiesDELETE · changes data
Questions
- Can HumDay update queries in Semantria?
- Yes. This operation is published in Semantria'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 Semantria data?
- Yes — this is a PUT operation, so it changes something in Semantria. 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 Semantria account.
Where this came from
Read from a published API description for Semantria at semantria.com/developer/api-docs-prod. The description above is the provider’s own wording, not ours. Last published 2018-08-24.