Chatted wit Digi today, to double check something. Looks like we'll need to send the id over with a post and not a get. Currently the spoc request is a get, and it passes consumer_key along as a query param. If we move this over to a post, and include the pocket impression_id as a payload item, I'll also want to send consumer_key over as a payload item too.
The payload changes I'll be sending in the spoc request post are:
```
{
consumer_key: "abcd",
impression_id: "abcd",
}
```
Mathijs, does that make sense to you, and is there something separate you need to track for any potential changes needed to be made on the back end?
Bug 1550115 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Chatted with Digi today, to double check something. Looks like we'll need to send the id over with a post and not a get. Currently the spoc request is a get, and it passes consumer_key along as a query param. If we move this over to a post, and include the pocket impression_id as a payload item, I'll also want to send consumer_key over as a payload item too.
The payload changes I'll be sending in the spoc request post are:
```
{
consumer_key: "abcd",
impression_id: "abcd",
}
```
Mathijs, does that make sense to you, and is there something separate you need to track for any potential changes needed to be made on the back end?