Comments by User in New York Times Community
A documented New York Times Community operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Comments by User
- GETReads data
api.nytimes.com/user-content/user.json
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 New York Times Community operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other New York Times Community operations
Questions
- Can HumDay comments by user in New York Times Community?
- Yes. This operation is published in New York Times Community's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my New York Times Community account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in New York Times Community.
- 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 New York Times Community account.
Where this came from
Read from a published API description for New York Times Community at raw.githubusercontent.com/nytimes/public_api_specs/master/community/community_api_v3.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.