Developers — the Developer role's home

Organization → Developers. Where the Developer role lands after signing in. For whoever may manage API keys or integrations.

Who opens it: whoever builds or looks after an integration with EntryWick. What they came to do: check that their keys work, that their webhooks are being answered, and find the API docs. What must be true when they leave: they know whether anything they built has stopped working, and where to look if it has.

What is on it

• API calls this month — how many calls this organization has made against its plan's allowance, when the plan has one. The same figure as on Usage.
• API keys — the keys that work now: not revoked, not expired. Each shows its prefix only, whether it is a test key, and when it was last used. "API keys" opens the page where keys are made and revoked (api-keys.md).
• Webhook health — every endpoint with its status, and how many deliveries to it succeeded or failed in the last 24 hours. Only the endpoint's host is shown. An endpoint opens its own page with every delivery (webhooks.md).
• Developer portal — the developer docs, the API reference, the quick-starts, the sandbox, the changelog and the API's status page (developer-docs.md).

What it does not do

It reads. Keys and endpoints are made, changed and revoked on their own pages, and every change is in the audit log.