- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
POST merakiAuthUsers returning "null" body
Hi there!
I'm using the Meraki API in order to create guests access over some Wifi networks.
It works everytime, except that some time the response got a 201 status, but with "null" in the response body.
The response should always contains a body as described in your own API docs here : https://developer.cisco.com/meraki/api-v1/create-network-meraki-auth-user/
Can you reproduce the problem on your side or do you have any logs that goes on this way?
Thank you boys and girls.
Cheers.
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a workaround you can use the GET call to retrieve an accounts ID. But as mentioned before I would engage support as to why your getting a 201 with a null body.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How many API calls are you making? The Meraki Dashboard API is rate-limited to ten calls per second, per organization.
https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API
Please, if this post was useful, leave your kudos and mark it as solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
you would get a 429 response if you hit a rate limit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a user forum, your post reads like it's addressed to Meraki, imo it's unlikely anyone at Meraki will investigate specifics based on a posting here.
As the response is 201 with no data, it conflicts with the API documentation. The best thing will be open a support case (via Dashboard) detailing call parameters and the problem with the endpoint intermittently giving a response that doesn't match documentation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there an underlying concern here? If you get a 201 back you know its successful and the account was created.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The documentation shows a successful response returns data, with elements not present in the request.
The created user ID for instance - which I think is required by other calls, for instance to delete the user.
If the call isn't returning that data, it's a clear error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a workaround you can use the GET call to retrieve an accounts ID. But as mentioned before I would engage support as to why your getting a 201 with a null body.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you all for responding 🙂
I was able to do the workarround as described in the accepted solution. It is not optimal, and I wanted to create a support case in the "dashboard" but I wasn't able to find out where this part is.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Login to Dashboard for the organization.
Top right of screen there's a ? icon, click on it, in the drop-down list click on "Get help & cases"
There's a new "Support Center" page design now, assuming that's what you get, click the "API and webhooks" tile.
On the new page, click "Submit a case", fill in the details and click 'Submit'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm only able to report a new case related to "Licensing issue" unfortunately there 😕
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Odd, I get a list of networks and devices.
But it really doesn't matter, the list regularly doesn't have anything matching what I am opening a case about.
Just open the case, add a comment that it is only allowing you this option.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I recently opened a case regarding the "null" response to the user creation. Looks like any uppercase letter in the email creates this behaviour. Sending the email variable as email.lower() resolves the issue. Note that in all cases (sending uppercase letters or not), the resulting created user's email is always lowercase in the dashboard.
