Unsupported base URI- Pagination

[RaphaelL]

Hi ,

I can't reply to any of the threads ( NOTICE: Unsupported base URIs will stop working September 15, 2025 - The Meraki Community )* about unsupported base URI , but I have noticed that the pagination system still uses the shard instead of api.meraki.com 

Example : 

LINKS received in http header : 

<https://n329.meraki.com/api/v1/organizations/xxxx/networks?perPage=1000&startingAfter=L_0>; rel=first, <https://n329.meraki.com/api/v1/organizations/xxxx/networks?endingBefore=N_a&perPage=1000>; rel=last

What will happen to the pagination after the sunset date ? Will it change , Will it break ?

Edit : thanks alemabrahao , I forgot to paste the link 😑

[Oren]

I noticed that looking at your other post, and I'm checking with the team.

[Jake-Young]

I was trying to get the same thing answered/clarified on post https://community.meraki.com/t5/Developers-APIs/API-Redirects-After-September-15-2025/td-p/282391.   A 302 response is what tells the client the new URL (that's shard specific).

[Oren]

Did you use a browser or an API client when this happened?

[RaphaelL]

Good point. That's curious I'm not getting the same links with a web browser vs python requests module.

Python : 

{'first': {'url': 'https://api.meraki.com/api/v1/organizations/xxxxxx/networks?perPage=3&startingAfter=L_0', 'rel': 'first'}, 'prev': {'url': 'https://api.meraki.com/api/v1/organizations/xxxxx/networks?endingBefore=L_xxxxxxx&perPage=3', 'rel': 'prev'}, 'next': {'url': 'https://api.meraki.com/api/v1/organizations/xxxxxxx/networks?perPage=3&startingAfter=L_xxxxx', 'rel': 'next'}, 'last': {'url': 'https://api.meraki.com/api/v1/organizations/6xxxxx/networks?endingBefore=N_a&perPage=3', 'rel': 'last'}}

Browser : 

<https://n329.meraki.com/api/v1/organizations/xxxx/networks?perPage=1000&startingAfter=L_0>; rel=first, <https://n329.meraki.com/api/v1/organizations/xxxx/networks?endingBefore=N_a&perPage=1000>; rel=last

( redacted )

[Oren · Accepted solution]

Good. You had me worried there for a minute...

For a browser, this is expected behavior, otherwise a browser would block the response due to CORS. An API client using API keys/OAuth should see api.meraki.com in these links.

[RaphaelL]

Perfect then , I'm closing this thread.

I just wanted to scare you a little bit on this Halloween day 😉