Common Issues

Connection issues

My API key is rejected even though it looks correct

Double-check that the key was copied without leading or trailing spaces. Also confirm that API access is enabled for your Meraki organization — an org admin must turn it on under Organization → Settings → Dashboard API access. If the key was recently regenerated, the old key is immediately invalidated.

The connection times out during the initial sync

This often happens when the start date is set too far back and the API requests entity returns a very large number of records. Try setting a more recent start date and re-running. Once the initial sync succeeds, you can gradually move the start date back.

Missing data

No devices appear in the Organization devices entity

Verify that the API key belongs to a user with access to the organization that contains those devices. Also check that the devices are assigned to a network — unassigned devices may not appear in API responses.

Some organizations or networks are missing from the results

The API key used must have access to all organizations you expect to see. If your Meraki account manages multiple organizations, confirm that the key has the appropriate admin role in each one. Keys scoped to a single org won't return data from other orgs.

The Organization API requests entity returns no rows

Make sure your start date is set within a range where API activity actually occurred. Meraki's API request log retention is limited — logs older than a certain period may no longer be available through the API.

Permission errors

I get a 403 Forbidden error when syncing

The API key you're using doesn't have sufficient permissions for the requested entity. Read-only access is the minimum required, but some endpoints (like SAML configurations) may require org-level admin access. Ask your Meraki org admin to review and update your role.

SAML entity returns empty or errors out

SAML configuration data is only accessible if your organization has SAML enabled and your API key belongs to an org admin. If neither condition is met, this entity will return no data or a permission error.

Data discrepancies

Device status in Coupler.io doesn't match what I see in the Meraki Dashboard

Device status is captured as a snapshot at the time of the sync. If a device went offline after the last sync, the status in your destination won't reflect that until the next run. Increase your refresh frequency to keep status data more current.

API request counts differ between Coupler.io and the Meraki Dashboard

Meraki's Dashboard may display aggregated or deduplicated counts, while the API returns raw log entries. Differences can also result from the start date window you've configured — make sure it aligns with the time range you're comparing against.

Rate limits

Syncs fail partway through with a rate limit error

Meraki's API enforces a limit of 5 requests per second per API key. If you have a large number of organizations, networks, or devices, the connector may hit this limit during a full sync. Try running the data flow during off-peak hours or splitting entities into separate data flows to reduce concurrent API pressure.