Server keys and the reindex webhook
ak_secret_ keys for your backend: scopes, storage, and the two endpoints they open.
Some things happen server to server: your CMS telling us a page changed, your backend reporting
a conversion. Both use a server key minted on the dashboard's Install page (ak_secret_…,
shown once. We store only its hash.
Keys carry scopes (reindex, track) and can be bound to one site. Revoke from the dashboard;
revocation is immediate.
Reindex
POST https://api.actessia.ai/v1/webhooks/reindex
Authorization: Bearer ak_secret_…
Content-Type: application/json
{ "urls": ["https://help.example.com/cancellations"] }
Without urls, the whole site is queued for a re-crawl. The response is 202 with the crawl
run's id; the dashboard's Knowledge page shows its progress and the per-page outcomes.