A civic location receiver is configured in Meraki Dashboard, but no observations arrive. Meraki first GETs the POST URL during setup. What must the receiver return for that handshake?
Select an answer to reveal the explanation.
Short Explanation
Before the firehose starts, Meraki knocks with a GET and expects you to say back the validator passphrase. A 200 with the wrong body—or a receiver that only handles POST—fails the handshake.
Full Explanation
Before observations flow, Meraki GETs the configured POST URL and expects the validator string configured on the network. A 200 with the wrong body, or a receiver that only handles POST, fails the handshake and you retrieve nothing. Webex challenges and browser login redirects are not the Scanning API validator step.