You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of the REST-API, I would like to be able to get a poll using only a share token.
Currently, it is only possible to access a poll by PollId when using REST-API. When someone gets a public share, they can use the share/{token} endpoint to get the PollId but this doesn't give them the authorization of accessing the poll.
Describe possible solutions
I see two possible implementations :
Automatically mark the user as involved with a poll when they use the share/{token} endpoint so that they can simply GET poll/{pollId} (or create a dedicated endpoint to get involved with a poll using the share token).
Create a new endpoint like GET /api/v1.0/poll/{token} which would return a poll.
I would recommend against the second option as it would require more work to create endpoints to let the user access the list of options and to vote to make it entirely functional.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the goal you'd like to achieve
As a user of the REST-API, I would like to be able to get a poll using only a share token.
Currently, it is only possible to access a poll by PollId when using REST-API. When someone gets a public share, they can use the
share/{token}
endpoint to get the PollId but this doesn't give them the authorization of accessing the poll.Describe possible solutions
I see two possible implementations :
share/{token}
endpoint so that they can simply GETpoll/{pollId}
(or create a dedicated endpoint to get involved with a poll using the share token).GET /api/v1.0/poll/{token}
which would return a poll.I would recommend against the second option as it would require more work to create endpoints to let the user access the list of options and to vote to make it entirely functional.
Additional context
No response
The text was updated successfully, but these errors were encountered: