topic API v0 EOL verification question in Network Platform API

API v0 EOL verification question

PatWruk — Tue, 16 Jan 2024 18:47:31 GMT

I just received an email saying the extended grace period is expiring January 31st, and I'm getting the email because I haven't moved to v1 yet. I just checked all of my scripts that use the Meraki API and checked the API call "organizations/{orgid}/apiRequests?version=0" and nothing is using v0 anymore. Am I missing something?

Re: API v0 EOL verification question

aleabrahao — Tue, 16 Jan 2024 18:48:33 GMT

It should probably just be an informational message.

Re: API v0 EOL verification question

PatWruk — Tue, 16 Jan 2024 18:50:07 GMT

That's what I was hoping, just wanted to make sure I wasn't missing something that I should check.

Thanks

Re: API v0 EOL verification question

Rasmus Hoffmann Birkelund — Tue, 16 Jan 2024 18:51:06 GMT

I’m getting the same message, and afaik I’m also not using the v0 API, eventhough the email directly says I am.

Re: API v0 EOL verification question

Philip D'Ath — Tue, 16 Jan 2024 19:53:15 GMT

A call to the v0 API looks like:

https://api.meraki.com/api/v0/organizations/...

A call to the V1 API looks like:

https://api.meraki.com/api/v1/organizations/...

There is nothing that uses "?version=0". Instead search for "/v0/" in your code.

Re: API v0 EOL verification question

Ryan_Miles — Tue, 16 Jan 2024 19:56:44 GMT

You can also run the API requests call with parameter version to verify no version 0 calls have been made in the last 31 days

Re: API v0 EOL verification question

PatWruk — Tue, 16 Jan 2024 19:58:52 GMT

I think you misunderstood what I was saying. If you run the api call https://api.meraki.com/api/v1/organizations/{orgid}/apiRequests?version=0, you get a recent list of v0 api calls, if you change it to version=1, you get a recent list of v1 api calls. As explained here: https://community.meraki.com/t5/Developers-APIs/Identify-API-v0-usage-the-easy-way-0%EF%B8%8F%E2%83%A3/m-p/150274/thread-id/6006

Re: API v0 EOL verification question

Philip D'Ath — Tue, 16 Jan 2024 20:13:56 GMT

Oh, you are correct. My mistake.

Re: API v0 EOL verification question

gsauvage6hat — Mon, 22 Jan 2024 09:37:22 GMT

Hello.

I received the same email.

I tried to look for any v0 call in my code, but nothing.

Then I used the API call "getOrganizationApiRequests" , with option version = 0, to check any usage with this version.

Surprisingly, I have a lot ! But it seems it's a mistake :

    {
        "adminId": "xxxxxxxxxxxx",
        "method": "GET",
        "host": "nxxx.meraki.com",
        "path": "/api/v1/organizations/xxxxxx/appliance/trafficShaping/vpnExclusions/byNetwork",
        "queryString": "perPage=1000&startingAfter=xxxxxxxxx",
        "userAgent": "python-requests/2.31.0",
        "ts": "2024-01-22T01:44:45.110913Z",
        "responseCode": 200,
        "sourceIp": "xx.xx.xx.xx",
        "version": 0,
        "operationId": "getOrganizationApplianceTrafficShapingVpnExclusionsByNetwork"
    }

Apparently, every "getOrganizationApplianceTrafficShapingVpnExclusionsByNetwork" call is categorized as version 0, even if in the path we clearly see it's v1.

I'm wondering if there are other calls impacted, and maybe Meraki checks for each Org if there is any v0 call the same way, and as there are some wrong categorization, that's why we receive these emails ?