A Meraki SSID enable call returns HTTP 403 for the city's service account. How should the consumer treat that response compared with a 429?
Select an answer to reveal the explanation.
Short Explanation
403 means this badge cannot open that door. Waiting in line will not grow new permissions. Fail the hop and escalate role, token audience, or resource—unlike a 429 wait.
Full Explanation
HTTP 403 is an unrecoverable permission stop under 2.2: sleeping and retrying will not grant scope. Contrast with 429 (2.1), where waiting can be correct. The consumer must fail the hop and escalate credentials, role, or target resource rather than inventing success or applying rate-limit backoff.