Why doesn’t my API key work?

Your workspace is safe while a key fails: a refused request leaves everything as it was. The list on the Developer API page tells you which of the causes below it is.

The key isn’t in the list

It was revoked, and a revoked key can’t be brought back. Create a new one and put it in the code; see Create an API key.

It reads but won’t write

The row’s badge reads Read-only. That key can look at everything but change nothing. Jounce refuses any request that would add or update someone. Create a full access key for that code; see Full access and read-only keys.

Last used never changes

The key in the code isn’t the one you’re looking at. Compare the first and last characters shown in the row, such as jk_live_m4q7…x2vd, with the key in the code. If they differ, the code holds another key, or one that was revoked.

It answers about the wrong workspace

A key reaches only the workspace it was created in. Switch to the workspace you want and create a key there; see Switch workspaces.

I lost the key

Jounce shows a key once, at the moment it’s created, and keeps only enough to tell it apart afterwards. Revoke the lost key and create a new one; see Revoke an API key.

Jounce says Rate limit reached

Jounce’s reply reads Rate limit reached — retry after the reset, or Rate limit reached. Slow to 120 requests per minute. Your code is sending requests faster than Jounce accepts. Each refusal says how long to wait, and the docs describe the limits.

The page says Couldn’t load your keys

The full line reads Couldn’t load your keys. They’re intact — try again. Select Try again. Your keys are unchanged and still working; only the list on this page didn’t load.