API keys & outbound webhooks

Use the REST API directly, or get a signed POST the moment a scan finishes.


API keys

Open Account → Developers in the sidebar to create and revoke API keys. Send your key as a Bearer token: Authorization: Bearer zk_…

The REST API reads the completed scans, clients and locations you see in the app, your team’s included. It also creates and finds CRM leads and manages webhooks. It allows 120 requests per minute per person, shared by every key you create and every SI assistant you connect; each teammate has their own. The count starts again at the top of every clock minute. A call over the limit is answered with HTTP 429 and a Retry-After header giving the number of seconds until that minute ends, so wait that long, then send it again. Account → API Reference lists every endpoint, with the OpenAPI file to download.

  • GET /api/v1/scans: list the completed scans you can see, your team’s included.
  • GET /api/v1/scans/{id}: one scan with its grid results.

Outbound webhooks

Add an https URL on the same page to get a POST the moment something happens: paste a Zapier “Catch Hook”, Make, n8n, or any endpoint.

  • Events: scan.completed, scan.failed, rank.changed, reputation.feedback.created and lead.created, plus site_audit.issue when you click Send on an issue in SEO.
  • A webhook takes your whole team’s events, a teammate’s scans and reviews as well as your own. A teammate’s leads reach it when you can see every lead in the CRM. Someone who sees only chosen clients gets their own events.
  • Every call is signed with an X-Semwiser-Signature header so you can verify it came from Semwiser.
  • The signing secret is shown once when you add the webhook. Copy it then.

SI assistants (MCP)

Connect Claude or another assistant that supports MCP to work with your Semwiser data in plain language. The SI assistants card on Account → Developers gives the server URL: your Semwiser app address followed by /api/mcp. The assistant signs in with an API key as a Bearer token, or through its own Connect flow. Like API keys, it can require the GBP Management plan, and each tool call it makes counts toward the same 120 requests per minute as your keys. A call over that limit is refused with the number of seconds until the next minute, when the count starts again.

An assistant can read your scans, clients, locations and leads, create leads, schedule scans and client report emails, and manage your GBP profiles, reviews and posts. Scheduled scans spend credits like any other scan.

Assistants you approved through Connect are listed under Connected SI assistants. Disconnect one and it loses access on its next request.