Valid Meraki API Network Creation Request Structure

300-435 By islever Editorial Last updated

Construct a network automation solution with Python using RESTCONF to manage and monitor configurations Troubleshoot network automation solutions based on REST APIs

Short answer

D The valid request uses POST with the organization ID in the path and only name/type in the JSON body.

Question

Which HTTP request is valid to create a new wireless network called Demo Wireless Network in the organization QASD-EROA-MKAW?
  1. [sampleXML/xmlfile-82_1.png]
  2. [sampleXML/xmlfile-82_2.png]
  3. [sampleXML/xmlfile-82_3.png]
  4. [sampleXML/xmlfile-83_1.png] Correct Answer

Key Takeaways

The main trap is including the organization ID in the JSON body; it must be part of the URL path, leaving the body to contain only network-specific attributes like name and product types.

Identify the correct HTTP request to create a Meraki wireless network using the Dashboard API. The solution requires POSTing to the organizations/networks endpoint with the organization ID in the URL path.

Common mistake: Choosing Option A because it includes all apparent data points. However, this is incorrect because Meraki APIs do not accept organizationId in the request body for this endpoint, leading to validation errors.

Expert Analysis

The question asks for a valid HTTP request to create a new wireless network in the Meraki Dashboard API. The endpoint for creating a network is POST /organizations/{organizationId}/networks. This is a RESTful resource creation, so the HTTP method must be POST.

In Meraki's API design, the {organizationId} is passed as a path parameter (part of the URL), not as a body parameter. Therefore, any JSON payload containing an organizationId field is structurally incorrect for the request body; the organization context is already defined by the URL path. The request body should contain only the properties required to define the new network. For a wireless-only network, the standard fields are name and productTypes (or historically just type in older versions, but modern API documentation emphasizes productTypes).

Let's evaluate the options based on these constraints:

  • Option A: Contains organizationId inside the JSON body. This is redundant and invalid because the ID is already in the URL path. Comments correctly note that "OrganizationID never goes in the body" and it is "not a valid body parameter."
  • Option B & C: These appear to have structural issues or incorrect methods/payloads not aligned with the standard Meraki schema.
  • Option D: Uses the correct POST method and includes the necessary fields (name, type/productTypes) in the body without including the organizationId. This aligns with the API specification where the path defines the scope and the body defines the resource attributes. As one comment states: "D - OrganizationID never goes in the body for meraki api calls...v1 or v0". Another confirms: "correct answer is D because the org id is on the path already."

Therefore, Option D represents the syntactically and semantically correct request structure.

Official Reference

https://developer.cisco.com/meraki/api/#!create-organization-network

This link opens the official vendor documentation in a new tab.

Exam Strategy

When working with REST APIs in certification exams, always distinguish between path parameters and body parameters. If an identifier (like an Organization ID) appears in the URL template (e.g., /organizations/{id}/...), it is a path parameter and should NOT be repeated in the JSON body. Focus on what attributes are unique to the resource being created (name, type, settings) rather than its parent context.

Frequently Asked Questions

Why is organizationId not in the JSON body?

The organizationId is a path parameter defined in the URL (/organizations/{organizationId}/networks). Including it in the body is redundant and often causes validation failures in Meraki's API.

What HTTP method is used to create a Meraki network?

A POST request is used to create new resources. GET retrieves data, PUT updates existing resources, and DELETE removes them.

More 300-435 FAQ →

Community Votes

D
34%
B
22%
C
22%
A
22%

34% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 11 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 11

  1. kekoa 👍 5
    A - POST /organizations/{organizationId}/networks https://developer.cisco.com/meraki/api/#!create-organization-network
  2. pafcio84 👍 3
    I think D because in Schema Definition: https://developer.cisco.com/meraki/api/#!create-organization-network There is only necessary to add "name" and "type"
  3. NoobChampion 👍 3
    NoobChampion here again! Considering it is asking for which request is the valid one. I think the answer should be D
  4. rhmgh 👍 2
    he wants create a wireless network, not a combined, then i think A is correct answer.
  5. ThePokemonNuzlockingMaster 👍 1
    UPDATE: I Believe the answer to be A. I posted before stating that I think D is the answer but I was wrong, I'm fairly sure it would be A. OrganizationID being in the body is strange, however there are other questions on this site whereby OrganizationID is part of the body and that is the correct answer (for example question 96). The reason I think A is the correct answer despite this is because the "type: combined" isn't actually an accepted network type. Combined is applied when you list out more than one network type, so for example it could be {"type": "wireless applicance"}. This is shown in the v0 documentation, which is the api version which this question is referring to: https://developer.cisco.com/meraki/api-v0/create-organization-network/ Type: The type of the new network. Valid types are wireless, appliance, switch, systemsManager, camera, cellularGateway, or a space-separated list of those for a combined network.
Show 6 more comments
  1. ThePokemonNuzlockingMaster 👍 1
    This is a bit confusing, looking at the documentation it kinda looks like none of them? https://developer.cisco.com/meraki/api/create-organization-network/ This doesn't have a "type" option defined in a schema, instead having a field called "productTypes", so that makes them all incorrect. Perhaps this question was written for an older version of the API. However, considering that it has to be between A and D (because the URL in B and C is incorrect), and there isn't the option to put organizationID or anything similar in the request body, I would be most inclined to go with D. Honestly though, this could go either way.
  2. NoobChampion 👍 1
    Could be A or D. Depends if the JSON is either the response or the body of the request. The request does not need an Organization ID but the response does have the field in it.
  3. jchutch2 👍 1
    It's D - OrganizationID never goes in the body for meraki api calls...v1 or v0
  4. jchutch2 👍 1
    A will fail because organizationid isn't a valid body parameter.
  5. Dominican_Beard 👍 1
    correct answer is D because the org id is on the path already.
  6. pafcio84 👍 1
    Maybe better is A because is more specific type: wireless.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Receiving Meraki Webhooks with FastAPI

A-grade

RESTCONF vs NETCONF Data Encodings

A-grade

Git Branch Creation and Checkout Commands

A-grade

Cisco DNA Center Webhook Properties

A-grade

Practice All 300-435 Questions

Access 150 questions with complete answers and detailed explanations.

View Full 300-435 Practice Test →

← Back to 300-435 Study Guide