Statuspage API - Caching for "Get a list of subscribers" endpoint

[Lukas Schwab]

Dear Comunity,

I noticed that when I create a new subscriber using the statuspage API and then try to find it in the list of all subscribers (GET /pages/{page_id}/subscribers) it doesn't show up right away.

I haven't found out the exact time it takes until a newly created subscriber shows up in this list but it for sure takes longer than 5-10 minutes.

I know that I can use the "Get a subscriber" endpoint (GET /pages/{page_id}/subscribers/{subscriber_id}) to get a single subscriber, and this one works imediately after I create a new subscriber.

My Problem here is that my application only knows the email address of the subscriber, so I use the above mentioned "Get a list of subscribers" endpoint and add a query parameter like this: "?q=john.doe@work.com".

My Questions:

1. Does anyone know if atlassian uses caching for this endpoint?

2. If they use chaching, is there a way to disable it for this endpoint?

3. If there's no way to disable the caching, for how long does the caching last exactly?

Thanks a lot for your help!

[Lukas Schwab]

Hello Jesse,

The problem doesn't occur the first time I try to create a subscriber and then try to look for him in the list of all subscribers.

It occurs when I try to create a subscriber than has been unsubscribed before. This is why I thought it probably had something to do with caching.

These steps don't work:

1. create subscriber (works)

2. get list of subscribers and find our subscriber (works)

3. unsubscribe subscriber (works)

4. create new subscriber with same email as old subscriber (works)

5. get list of subscribers and find our new subscriber (doesn't work)

[Jesse Klein]

Hello Lukas,

This is Jesse from the Statuspage support team. Thanks for your question around API caching and welcome to the community.

I find it a bit strange that you're experiencing delays in the API responses for changes. For the manage API, there is no caching going on. The only thing that is cached is the status API, which does not apply here.

I just ran some testing on my side and was able to get instantaneous results each time I ran the request. I even added the ?q=john.doe@work.com part of this to see if that had an effect and got the same results. I am curious why this would be happening for you. If you had any more details of your setup, I would love to understand more. If you have anything outside of a Free plan, also feel free to send us a support ticket. I hope you have a great day!

Regards,
Jesse

[Lukas Schwab]

Hello, Jesse

I accidentally posted my reply as a reply to my post, not your response so feel free to check it out and thanks a lot for your help!

Lukas