A Python script uses the Meraki Dashboard API to create a branch network with a valid API access key and a known organization ID, and the account already manages other networks in that organization. The call returns HTTP 400 naming invalid parameters. Which request details must be present for network creation to succeed?

Network creation is organization-scoped, so the request must use POST /organizations/{organizationId}/networks, with the organization ID in the URL path. The endpoint creates a network within that organization, while the JSON body supplies its configuration: it must contain the network name and a productTypes list identifying the products the new network will support. A collection-level POST to /networks uses the wrong endpoint because it omits the organization scope. The name-only body fails because it leaves out the required productTypes field. The query-parameter approach also fails: putting the name and product types in the URL query does not supply them in the required JSON body. An exam caveat is that a valid API key and organization ID do not make an otherwise malformed request valid; optional body fields such as tags, notes, and a copy-from source are not required for network creation. As a practical check, verify the HTTP method and organization-scoped path, then inspect the serialized request to confirm that the JSON body contains both the network name and productTypes before adding optional fields.