Read Entities in NLPCloud
A documented NLPCloud 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
Read Entities
- POSTChanges data
/v1/en_core_web_sm/entities
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 NLPCloud 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 NLPCloud operations
Questions
- Can HumDay read entities in NLPCloud?
- Yes. This operation is published in NLPCloud'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 NLPCloud data?
- Yes — this is a POST operation, so it changes something in NLPCloud. 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 NLPCloud account.
Where this came from
Read from a published API description for NLPCloud at nlpcloud.io/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-01-25.