Developer docs
The API, API keys, automations, webhooks and integrations, for developers, integrators, agencies and automation builders.
You do not need developer tools to audit your website. Adding sites, running and scheduling audits and reading reports all work in the app without them: that is the user guide.
Start here
- Turn developer tools on in the app. They are off on a new account.
- Create an API key with only the scopes you need.
- Follow the API quickstart: from a key to the first results with curl.
- Go further: automations and webhooks, the API reference, or a recipe for CI, Postman or AI assistants.
In the app, the same tools are under Developers in the menu: Developer home, API keys, API console, Automations and Integrations.
Who they are for
Developer tools are for people who connect Metricevo to other systems and are comfortable working with an API:
| Who | Typical use |
|---|---|
| Developers | Start an audit from a script and read the result as JSON. |
| DevOps and CI owners | Audit after every deploy and stop the build on high findings. |
| Agencies | Audit many client sites from your own tools and pull the results into your reports. |
| Integrators and automation builders | Connect Zapier, Make, n8n or your own service through webhooks. |
| AI assistant users | Give an assistant a key and the API contract as its tools. |
If you only have a company website and want to know what to fix, you can skip this area and use the user guide.
What developer tools include
- API keys: a key lets a program act as your account, limited to the scopes you choose.
- Automations and webhooks: an incoming webhook starts an audit; an outgoing webhook sends the result to your system.
- The API console: in the app under Developers → API console, signed in, against your own data.
- The REST API and its reference. The Free plan includes API access.
Turn them on
Developer tools are off on a new account. To turn them on:
- In the app, open Settings and find Developer tools.
- Read the notice and tick I have read this and understand that developer tools can run automatically and use my audit quota.
- Press Turn on developer tools. The Developers group now appears in the menu.
Until you do, the developer pages in the app open Settings, and calls with an API key, key management, automations and incoming webhooks answer 403 with the code developer_mode_required.
What to know before you turn them on
- An API key acts as you. Anyone who has it can read your sites and audits, and start audits, within its scopes. Keep keys in a secret store, never in code or a chat.
- Automations run on their own. A wrong schedule, loop or retry can use up your audit quota and, on a paid plan, add usage charges. Start small and check the activity of each automation.
- Outgoing webhooks send your results to the address you enter. Use addresses you control.
- You are responsible for what runs under your account.
Turn them off
In Settings → Developer tools, press Turn off developer tools. Your API keys, automations and incoming webhooks stop working at once, and outgoing webhooks are not sent. Nothing is deleted: turn them on again and they work as before.