Returns a single user in Bufferapp
A documented Bufferapp 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
Returns a single user.
- GETReads data
api.bufferapp.com/user{mediaTypeExtension}
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 Bufferapp 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 Bufferapp operations
- Create one or more new status updatesPOST · changes data
- Immediately shares a single pending updatePOST · changes data
- Edit the order at which statusesPOST · changes data
- Randomize the order at which statusesPOST · changes data
- Edit an existing, individual status updatePOST · changes data
- Permanently delete an existing status updatePOST · changes data
- Move an existing status update to the top of the queuePOST · changes data
- "Set the posting schedules for the specified social media profilePOST · changes data
Questions
- Can HumDay returns a single user in Bufferapp?
- Yes. This operation is published in Bufferapp'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 Bufferapp account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Bufferapp.
- 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 Bufferapp account.
Where this came from
Read from a published API description for Bufferapp at raw.githubusercontent.com/APIs-guru/unofficial_openapi_specs/master/bufferapp.com/1/swagge. The description above is the provider’s own wording, not ours. Last published 2021-06-21.