Re: v4/checkin/add does't seem to work

28 views
Skip to first unread message
Message has been deleted

Greg Avola

unread,
Jan 19, 2020, 11:39:48 AM1/19/20
to untappd-api-d...@googlegroups.com
Access token must be in the url - like ?access_token=XXx and the rest of the parameters go int the body POST.

Does this helps?

Greg

On Sun, Jan 19, 2020 at 11:27 AM Jaime Lafleur-Vetter <jve...@gmail.com> wrote:
I've been using the Untapped API for a couple months now and every endpoint I try with my access_token works accept checkin. 

For example, when I do a post to v4/checkin/add with the minimal parameters ( "gmt_offset": -4, "timezone":"EDT", "bid", 21768, "access_token": [my token]), I get the error: 

error_detail: Your missing the 'client_secret' and\\/or 'client_id' parameter

I've pretty much tried every combination of parameters, required, not required, and different values for each. Even tried including the client_secret and client_id with the access_token, which of course didn't help. Regardless of what I do I get that error.

Any idea why?

--
You received this message because you are subscribed to the Google Groups "Untappd API Developer Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to untappd-api-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/untappd-api-developer-group/78bbd2f3-8697-4550-9982-a17c25418a39%40googlegroups.com.
--
--

Greg Avola
Co-Founder / CTO
Untappd

Message has been deleted

Greg Avola

unread,
Jan 19, 2020, 11:51:10 AM1/19/20
to untappd-api-d...@googlegroups.com
This means you are not passing the access token via the url - which means it’s looking for client iD.

Sounds like there may be an issue with the library - or do you have way of outputting the url you are sending?


Greg

On Sun, Jan 19, 2020 at 11:49 AM Jaime Lafleur-Vetter <jve...@gmail.com> wrote:
Thanks for the quick response.

I'll double check what its doing, but I'm using Untappd.Net wrapper, so I presume its doing the access_token right since other calls requiring authentication works. Does the checkin endpoint use the access_token differently than other authenticated endpoints (e.g. beer search)?

The part that is confusing to me is the error message. Why would it be giving me an error about client_secret and client_id if the endpoint requires full authentication. 

Thanks.
Reply all
Reply to author
Forward
Message has been deleted
Message has been deleted
0 new messages