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
I think you're requesting two different things, aren't you? First one would be to be able to leave out the origin parameter and second one is to pass the payload via URL parameters, instead of as part of the body.
To conform with web standards, the format would look slightly different (see below), but apart from that this is definitely something we could implement. Thanks for these feature requests.
Example: GET /api/messages?recipient_token=f9e1-bb79-4db2-8fff-cfbb8&origin=somedevice&type=TEXT
muety
changed the title
URL with body JSON content
Allow to pass payload as query parameters of GET request
Oct 9, 2021
Is it possible to achieve this form:
https://domain.com/api/messages/?data={"recipient_token":"f9e1-bb79-4db2-8fff-cfbb8","type":"TEXT","origin":"somedevice"}
Because not all software supports all values, such as
origin
.The text was updated successfully, but these errors were encountered: