Update Device Lists returns Status Code 204

65 views
Skip to first unread message

ch...@pushspring.com

unread,
Aug 23, 2016, 12:41:12 PM8/23/16
to PocketMath API
I am calling https://api.pocketmath.com/v2/device_lists/52339.json

I am passing name and remote_file_url.  The remote file url is public and I can paste into a browser and download it.

I am calling the patch method.

I get back a 204 No Content.

I never see any data show up in the console in that device list.

Does it need a while to process the file?  Should I be getting back a 200 instead of a 204?  Trying to figure out what is wrong here and not much surface area to get traction against.

Thanks,

Ross Finch

unread,
Aug 24, 2016, 4:10:46 AM8/24/16
to PocketMath API
Hi Chris,

I've had a quick look at your account and I don't see a device list with that id. You do have a publisher list with that id though.

We obviously have a bug here, we should be returning you a 404 for a list that does not exist.

Are you trying to create a publisher list or device list?

Let me know if there's anything I can do to help.

Regards,
Ross

ch...@pushspring.com

unread,
Aug 24, 2016, 9:24:43 AM8/24/16
to PocketMath API
Trying to create a device list.  

I accidentally pasted in the wrong id above.  The correct one is https://console.pocketmath.com/device_identifier_lists/36877

We attached it to an order in an attempt to get it to load but we still see a X Failed in red when we navigate to the above page.

Thanks!

ch...@pushspring.com

unread,
Aug 24, 2016, 10:28:58 AM8/24/16
to PocketMath API
BTW also playing with the docs it looks like the example for the PATCH doesn't include the multipart form data:

curl -X PATCH --header 'Content-Type: multipart/form-data' --header 'Accept: application/json' --header 'Authorization: Token token=XXXXXXX' 'https://api.pocketmath.com/v2/device_lists/36877.json'

Ross Finch

unread,
Aug 29, 2016, 5:13:32 AM8/29/16
to PocketMath API
For people who find this in the future; I've been talking to Chris through a different channel and we've found a problem with the way we're processing some unicode escape characters in device lists. Chris has removed one of the entries from his list and it has started processing.
Reply all
Reply to author
Forward
0 new messages