Deprecated operations

Listed by deprecation date (newest first).

2026 June

getNetworkSyslogServers

getNetworkSyslogServers is deprecated in favor of getOrganizationDevicesSyslogServersByNetwork or getOrganizationDevicesSyslogServersRolesByNetwork, based on your use case.

Replacement operations

Use case: reading syslog server configuration for one or more networks

getOrganizationDevicesSyslogServersByNetwork returns syslog server configuration for networks in an organization. Pass the networkIds[] query parameter to limit results to specific networks (for example, a single network ID when migrating from getNetworkSyslogServers).

This operation is paginated and supports reading syslog configuration for many networks in fewer API calls than issuing one network-scoped request per network.

Use case: discovering valid syslog role values before configuring servers

When migrating write workflows, use getOrganizationDevicesSyslogServersRolesByNetwork to list the role name and value pairs available for each network. The replacement update operation expects role value strings (for example, wirelessEventLog), not the human-readable titles returned by the deprecated read and update operations (for example, Wireless event log).

Migration notes

  • OAuth scope: dashboard:general:telemetry:read → dashboard:general:config:read
  • Response shape: the deprecated operation returns { "servers": [ ... ] }. The replacement returns a paginated collection: { "items": [ { "network": { "id": "..." }, "servers": [ ... ] } ], "meta": { ... } }.
  • Server attributes: replacement responses include transportProtocol and encryption settings in addition to host, port, and roles.
  • Roles: replacement responses return per-product-type role values in camelCase (for example, applianceUrlLog, wirelessEventLog) instead of the deprecated operation's rolled-up human-readable titles (for example, URLs, Wireless event log).

updateNetworkSyslogServers

updateNetworkSyslogServers is deprecated in favor of updateNetworkDevicesSyslogServers.

Replacement operations

Use case: updating syslog server configuration for a network

updateNetworkDevicesSyslogServers updates syslog servers for a network. It supports the same core inputs (host, port, roles) and adds optional transportProtocol and encryption settings for encrypted syslog.

This operation supports action batches via the standard Meraki action batch mechanism.

Use case: determining which role strings are valid for a network

Before calling the replacement update operation, query getOrganizationDevicesSyslogServersRolesByNetwork and use each role object's value property in the update request body.

Migration notes

  • OAuth scope: dashboard:general:telemetry:write → dashboard:general:config:write
  • Request body: the servers array structure is similar, but roles must use camelCase enum values (for example, ["wirelessEventLog", "applianceUrlLog"]) rather than human-readable titles (for example, ["Wireless event log", "URLs"]).
  • Response shape: the deprecated operation returns { "servers": [ ... ] }. The replacement returns { "network": { "id": "..." }, "servers": [ ... ] } with camelCase role values and optional transportProtocol / encryption fields.
  • Role specificity: the replacement API models roles per product type (for example, separate wireless and appliance URL log roles). The deprecated API rolled some non-event-log roles into generic titles; callers should map to the appropriate per-product-type role values for their network.

Example migration

Before (deprecated):

PUT /networks/{networkId}/syslogServers

{
  "servers": [
    {
      "host": "1.2.3.4",
      "port": 514,
      "roles": ["Wireless event log", "URLs"]
    }
  ]
}

After (replacement):

PUT /networks/{networkId}/devices/syslog/servers

{
  "servers": [
    {
      "host": "1.2.3.4",
      "port": 514,
      "roles": ["wirelessEventLog", "applianceUrlLog"],
      "transportProtocol": "UDP"
    }
  ]
}

To resolve role values for a network programmatically:

GET /organizations/{organizationId}/devices/syslog/servers/roles/byNetwork?networkIds[]={networkId}

2026 May

createOrganizationPolicyObject (Request body parameter deprecation)

createOrganizationPolicyObject ipAndMask which is part of the API request body parameter type is deprecated and will be removed in a future release. Use cidr instead.

2024 October

getNetworkDevices

getNetworkDevices is deprecated in favor of the following operations, based on your use case:

Replacement operations

Use case: gathering device serial numbers, names, notes, models, MACs, and other hardware metadata, including network assignments

getOrganizationDevices provides all this information, and offers more query parameter options for filtering the result, including filtering on networkIds.

getOrganizationDevicesUplinksAddressesByDevice lists the current uplink addresses for devices in an organization.

getOrganizationDevicesStatuses

getOrganizationDevicesStatuses is deprecated in favor of the following operations, based on your use case:

Replacement operations

Use case: continuous monitoring of device up/down/alerting/dormant status and/or status history

Most of the time, most devices in a network should be in an online status. The operation getOrganizationDevicesAvailabilitiesChangeHistory provides the most efficient means of gathering status information over time. Thus, by monitoring the change history, you can assert device status by comparing the changes provided by this operation with a one-time snapshot of the statuses provided in getOrganizationDevicesAvailabilities. This is substantially more efficient than polling device statuses on an interval, because an empty response in the change history means were no status changes during that time for any device in an entire organization.

Use case: one-time poll of device up/down/alerting/dormant status

getOrganizationDevicesAvailabilities provides status information for devices in a more performant manner than the deprecated statuses operation.

Use case: Polling device power module status

getOrganizationDevicesPowerModulesStatusesByDevice lists the most recent status information for power modules in rackmount MX and MS devices that support them.

getOrganizationDevicesUplinksAddressesByDevice lists the current uplink addresses for devices in an organization.

Use case: Polling device provisioning status

getOrganizationDevicesProvisioningStatuses provides the provisioning status for each device.

2024 May

getNetworkHealthAlerts

getNetworkHealthAlerts is deprecated in favor of getOrganizationAssuranceAlerts which offers more extensive filtering capabilities

2024 March

Camera analytics

The following operations are deprecated in favor of the newer boundaries operations.

2023 August

claimIntoOrganization

claimIntoOrganization is deprecated in favor of claimIntoOrganizationInventory, which offers full feature parity.