Any changes of the response ?

[helicalgear]

Hi,

Today, I found that the contents of "pagination" in the response of Activity Feed (v4/checkin/recent) is different.

I think that the "pagination" is contained "since_url", "next_url" and "max_id", conventionally.

But It seemed be changed to "next_url" and "offset".

User Activity Feed (v4/user/checkin/USERNAME) returned the "pagination" with "since_url", "next_url" and "max_id" as in the past.

Is it changed permanently ?

Best regards,

[Greg Avola]

I can take a look at this over the weekend. We no longer support since_url - it wasn't widely used for activity feed, since you wouldn't be able to get data or changes for previous check-ins. I can look to add back the max_id, which is the last entry, but you should be using next_url for pagination and not max_Id anymore.

Is there a use-case you are using here for max_id and since_url?

Greg

--
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-developer-group+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

[helicalgear]

Thank you very much for your swift response.

I personally can not think of special use case to need the max_id strongly, right now.

Thanks!

2018年2月24日土曜日 11時17分51秒 UTC+9 Greg Avola [Untappd]:

[Greg Avola]

max_id is now the pagination set.

Greg

On Fri, Feb 23, 2018 at 9:29 PM, helicalgear <helic...@gmail.com> wrote:

Thank you very much for your swift response.

I personally can not think of special use case to need the max_id strongly, right now.

Thanks!

2018年2月24日土曜日 11時17分51秒 UTC+9 Greg Avola [Untappd]:

I can take a look at this over the weekend. We no longer support since_url - it wasn't widely used for activity feed, since you wouldn't be able to get data or changes for previous check-ins. I can look to add back the max_id, which is the last entry, but you should be using next_url for pagination and not max_Id anymore.

Is there a use-case you are using here for max_id and since_url?

Greg

On Fri, Feb 23, 2018 at 8:41 PM, helicalgear <helic...@gmail.com> wrote:

Hi,

Today, I found that the contents of "pagination" in the response of Activity Feed (v4/checkin/recent) is different.

I think that the "pagination" is contained "since_url", "next_url" and "max_id", conventionally.

But It seemed be changed to "next_url" and "offset".

User Activity Feed (v4/user/checkin/USERNAME) returned the "pagination" with "since_url", "next_url" and "max_id" as in the past.

Is it changed permanently ?

Best regards,

--
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-developer-group+unsubs...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

--
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-developer-group+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Greg Fiumara]

I have been using max_id to build up a request to get the previous set of check-ins from the activity feed in reverse chronological order (max_id from the response was the max_id input to the next request). I didn't notice this change because I'd been basing the visibility of the button to issue the next request based on the presence of the since_url parameter (when this parameter went away, it seemed to be as far back as Untappd would let us query). As of this morning, the max_id return parameter is back.

I use a similar technique with user/checkins, but this still has since_url and max_id. Is this going to change in the near future?

Thanks,

-Greg

To unsubscribe from this group and stop receiving emails from it, send an email to untappd-api-develop...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

-- 

Greg Fiumara

[Greg Avola]

Greg,

I don't 100% follow what you are trying to do, but for pagination, you should alway be using "next_url" not max_id. We don't support any other type of interaction besides pagination (next page) and since url (more content after a checkin ID)

We don't have plans to remove since_url as this time, it's not just i the pagination response for activity_feed. The reason why it's not there is because it's a common confusion point for developers when a user is not active, and they use since ID on an older ID, and get back an error (if it's more than 7 days ago). We just recommend using the next_url and refreshing the same endpoint to get the new feed data. You should still be able to request via the normal way that it's documented - but we don't recommend due to that error I mentioned.

Greg

On Sat, Feb 24, 2018 at 11:31 AM, Greg Fiumara <gr...@gregfiumara.com> wrote:

I have been using max_id to build up a request to get the previous set of check-ins from the activity feed in reverse chronological order (max_id from the response was the max_id input to the next request). I didn't notice this change because I'd been basing the visibility of the button to issue the next request based on the presence of the since_url parameter (when this parameter went away, it seemed to be as far back as Untappd would let us query). As of this morning, the max_id return parameter is back.

I use a similar technique with user/checkins, but this still has since_url and max_id. Is this going to change in the near future?

Thanks,

-Greg

On Feb 23, 2018, at 9:29 PM, helicalgear <helic...@gmail.com> wrote:

Thank you very much for your swift response.

I personally can not think of special use case to need the max_id strongly, right now.

Thanks!

2018年2月24日土曜日 11時17分51秒 UTC+9 Greg Avola [Untappd]:

I can take a look at this over the weekend. We no longer support since_url - it wasn't widely used for activity feed, since you wouldn't be able to get data or changes for previous check-ins. I can look to add back the max_id, which is the last entry, but you should be using next_url for pagination and not max_Id anymore.

Is there a use-case you are using here for max_id and since_url?

Greg

On Fri, Feb 23, 2018 at 8:41 PM, helicalgear <helic...@gmail.com> wrote:

Hi,

Today, I found that the contents of "pagination" in the response of Activity Feed (v4/checkin/recent) is different.

I think that the "pagination" is contained "since_url", "next_url" and "max_id", conventionally.

But It seemed be changed to "next_url" and "offset".

User Activity Feed (v4/user/checkin/USERNAME) returned the "pagination" with "since_url", "next_url" and "max_id" as in the past.

Is it changed permanently ?

Best regards,

--
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-developer-group+unsubs...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

--
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-developer-group+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 

Greg Fiumara

--
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-developer-group+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Greg Avola]

Greg,

Just checking back in here - to make sure I understand your questions and your workflow. Thanks!

Greg

-- 

Greg Fiumara

--
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-developer-group+unsubs...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

[Greg Fiumara]

Thanks for checking in Greg and sorry about being unclear on my use of the API. Rather than trying to clarify, I think I can just say that I need to change some code, but that I don't think there's anything I can't continue to do as a result of the change in the pagination response. I'll certainly let you know otherwise.

Thanks,

-Greg

To unsubscribe from this group and stop receiving emails from it, send an email to untappd-api-develop...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

-- 

Greg Fiumara

[helicalgear]

Hi,

The Endpoint: /v4/checkin/recent seemed to return only blank ("") as "next_url" (and "max_id")....

2018年2月24日土曜日 11時17分51秒 UTC+9 Greg Avola [Untappd]:

I can take a look at this over the weekend. We no longer support since_url - it wasn't widely used for activity feed, since you wouldn't be able to get data or changes for previous check-ins. I can look to add back the max_id, which is the last entry, but you should be using next_url for pagination and not max_Id anymore.

[Greg Avola]

I'm sorry - I don't follow - what's the question?

Greg

On Wed, Mar 7, 2018 at 5:06 AM, helicalgear <helic...@gmail.com> wrote:

Hi,

The Endpoint: /v4/checkin/recent seemed to return only blank ("") as "next_url" (and "max_id")....

2018年2月24日土曜日 11時17分51秒 UTC+9 Greg Avola [Untappd]:

I can take a look at this over the weekend. We no longer support since_url - it wasn't widely used for activity feed, since you wouldn't be able to get data or changes for previous check-ins. I can look to add back the max_id, which is the last entry, but you should be using next_url for pagination and not max_Id anymore.

Is there a use-case you are using here for max_id and since_url?

Greg

On Fri, Feb 23, 2018 at 8:41 PM, helicalgear <helic...@gmail.com> wrote:

Hi,

Today, I found that the contents of "pagination" in the response of Activity Feed (v4/checkin/recent) is different.

I think that the "pagination" is contained "since_url", "next_url" and "max_id", conventionally.

But It seemed be changed to "next_url" and "offset".

User Activity Feed (v4/user/checkin/USERNAME) returned the "pagination" with "since_url", "next_url" and "max_id" as in the past.

Is it changed permanently ?

Best regards,

--
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-developer-group+unsubs...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

--
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-developer-group+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[helicalgear]

Sorry for my unclear words.

Even if I access the Endpoint: checkin/recent many times, next_url (and max_id) only returns blank("").

Other contents (meta, items, etc...) are normal.

Is it trouble of server-side ?

Or, do I need to change the way to access to this endpoint ?

Best regards,

2018年3月8日木曜日 6時15分00秒 UTC+9 Greg Avola [Untappd]:

I'm sorry - I don't follow - what's the question?

Greg

On Wed, Mar 7, 2018 at 5:06 AM, helicalgear <helic...@gmail.com> wrote:

Hi,

The Endpoint: /v4/checkin/recent seemed to return only blank ("") as "next_url" (and "max_id")....

2018年2月24日土曜日 11時17分51秒 UTC+9 Greg Avola [Untappd]:

I can take a look at this over the weekend. We no longer support since_url - it wasn't widely used for activity feed, since you wouldn't be able to get data or changes for previous check-ins. I can look to add back the max_id, which is the last entry, but you should be using next_url for pagination and not max_Id anymore.

Is there a use-case you are using here for max_id and since_url?

Greg

On Fri, Feb 23, 2018 at 8:41 PM, helicalgear <helic...@gmail.com> wrote:

Hi,

Today, I found that the contents of "pagination" in the response of Activity Feed (v4/checkin/recent) is different.

I think that the "pagination" is contained "since_url", "next_url" and "max_id", conventionally.

But It seemed be changed to "next_url" and "offset".

User Activity Feed (v4/user/checkin/USERNAME) returned the "pagination" with "since_url", "next_url" and "max_id" as in the past.

Is it changed permanently ?

Best regards,

--
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-developer-group+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

--
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-developer-group+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Greg Avola]

If they return blank there are more data to show.

If you want directly ne the call you are making - you can email at gr...@Untappd.com

Greg

To unsubscribe from this group and stop receiving emails from it, send an email to untappd-api-develop...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

--
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.

For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

--
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.

For more options, visit https://groups.google.com/d/optout.

[helicalgear]

Oh... I see !

Thanks !

2018年3月8日木曜日 7時54分47秒 UTC+9 Greg Avola [Untappd]:

To unsubscribe from this group and stop receiving emails from it, send an email to untappd-api-developer-group+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

--
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-developer-group+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

--

Greg Avola

Co-Founder / CTO

Untappd

gr...@untappd.com

--
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-developer-group+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.