Meraki Provision an Organization Network
A 4-step recipe with Cisco. We can help you get access.
Recipe · 4 steps
Meraki Provision an Organization Network
with Cisco
Create a network in a Meraki organization, skipping the write when the name is already taken.
- List the organizations the API key has privileges on and assert the target organization is among them. A Meraki key is user-scoped, so this is the cheapest way to fail fast on a wrong key or a wrong organization id before attempting any wri
- List the networks already in the organization and check whether one already carries the requested name. The Meraki networks endpoint offers no server-side name filter, so the match is evaluated against the returned collection.
- Create the network in the organization with the requested name, product types, timezone, and tags.
- Re-list the organization's networks to confirm the newly created network is present and readable, closing the create/read-back loop before any downstream automation binds to the network id.
What you'll need to have ready
- organizationId: The Meraki organization identifier (e.g. 500123).
- networkName: The name to give the new network (e.g. "Main Office").
- productTypes: Product types to enable on the network, such as appliance, switch, wireless, or camera.
- timeZone: The network timezone in tz database form (e.g. America/Los_Angeles).
- tags: Tags to apply to the new network (e.g. production, campus).
For your developer
Arazzo workflow cisco:provision-meraki-network, 4 operations: getOrganizations → getOrganizationNetworks → createOrganizationNetwork → getOrganizationNetworks. Specs on APIs.io.