hooks

GET /api/admin/hooks (hooks.manage; no step-up to look): the security and retention webhooks, newest first, never their secrets.

Caller and authorization

Staff cookie session; permission hooks.manage.

This is the private staff console on https://admin.handwrites.io. A personal API key, organisation token, student login or isolated app-testing credential does not authenticate this route.

Request contract

This operation does not define a JSON payload. Staff writes still require Content-Type: application/json and the session-bound CSRF header.

Response and failures

Success: 200. GET /api/admin/hooks (hooks.manage; no step-up to look): the security and retention webhooks, newest first, never their secrets.

The wrapper returns {error:{code,message}} for CloudError failures, attaches Request-Id, and disables caching. Handle 401 by signing in; show role refusal for 403 forbidden, reauthenticate only for step_up_required, and collect a reason for 400 reason_required. A CSRF failure needs a current page/session token, not blind retries. Operation-specific 404/409/413/422/502/503 errors retain their status. Honor Retry-After on 429.

Usage notes

These are staff security/retention webhooks, separate from user document-event webhooks. A create response reveals its signing secret once; store it securely and never include it in docs or logs.

Implementation contract

Source snapshot: admin/src/app/api/admin/hooks/route.ts. This reference describes the current working tree, not proof of deployment. The response service types and validators remain authoritative. The exact exported handler below makes conditional behavior reviewable. For helpers such as customer-routes or cloudRoute, see the shared API specification notes and the named service module.

/** GET /api/admin/hooks (hooks.manage; no step-up to look): the security and retention webhooks, newest first, never their secrets. */
export const GET = adminRoute("hooks.manage", async () => adminJson({ items: await listHooks() }), { stepUp: false });

Do not use production customer data to test this operation. Use an authorized staff test account and a disposable target in an appropriate environment; email, deletion, role and credential mutations have real effects.

README — GET /api/admin/hooks

GET /api/admin/hooks#

Caller and authorization#

Request contract#

Response and failures#