API BUG: Wrong "Link" Header in /api/v0/organizations/{id}/securityEvents

[Greenberet]

Hello,

first of all this is just an informational thread, so that noone else will fall over that. I've opened already a meraki case for that issue.

When you are receiving the result in more pages, you will get the LINK header like this (I've masked the meraki shard):

<https://nXXX.meraki.com/api/v0/securityEvents?perPage=100&startingAfter=1554454686.0724242&timespan=25920000>; rel=first, <https://nXXX.meraki.com/api/v0/securityEvents?perPage=100&startingAfter=1577880115.764001&timespan=25920000>; rel=next, <https://nXXX.meraki.com/api/v0/securityEvents?endingBefore=1580374686.3534946&perPage=100&timespan=25920000>; rel=last

What you can see here is that the "organizations/{id}/" part is missing in the links. Therefore calling them will result in a "404 Not Found" Error.

They should all look like that:

<https://nXXX.meraki.com/api/v0/organizations/YYYYYY/securityEvents?perPage=100&startingAfter=1554454686.0724242&timespan=25920000>; rel=first, <https://nXXX.meraki.com/api/v0/organizations/YYYYYY/securityEvents?perPage=100&startingAfter=1577880115.764001&timespan=25920000>; rel=next, <https://nXXX.meraki.com/api/v0/organizations/YYYYYY/securityEvents?endingBefore=1580374686.3534946&perPage=100&timespan=25920000>; rel=last

[BrechtSchamp]

Thanks for sharing that! I'm sure lots of people would've broken their heads over this.

[TonyC]

Thanks for the report, we will track and get this fixed.

[Greenberet · Accepted solution]

Update: The issue got resolved 😃

[TonyC]

Indeed, thanks for the report and more importantly for opening up a case – that ensures we are getting the report over so we can fix these types of issues for our devs out there 🙂