Skip to main content
The beta Admin By Request integration reads elevation requests and supports approval and denial through ABR’s Requests API.

​
Connect

  1. In ABR, open Settings → Tenant Settings → Data → API Keys. Create a dedicated API key and save it.
  2. Note the API prefix shown on that page. Its dc1–dc6 prefix identifies your region.
  3. In Serval, open Integrations → Admin By Request. Select that region, choose a unique connection identifier for the ABR tenant, and enter the API key.
  4. Run Test Admin By Request Access. It reads at most one request; an empty tenant is valid. This check does not test approval or denial.
Serval stores the key as a secret and injects it into the apikey header. Workflows receive the connection ID and regional API host, not the key. A connection’s region and identifier cannot change; create a new connection for another tenant. When rotating a key, use a replacement from the same ABR tenant. ABR does not provide a tenant identifier in this connector’s API, so Serval cannot verify that a replacement key belongs to the same tenant.

​
Requests API

Use adminByRequest.apiRequest with these operations: List requests with take (1–1000), optional inclusive startid, and optional status: Pending, Approved, Denied, or Quarantined. Alternatively use last (1–1000), without take or startid. No automatic pagination is performed. Account for ABR’s daily API quota when scheduling polling. Approval and denial are privileged actions. Configure human approval in your workflow before either call. Re-read the request immediately before deciding, and read it again afterward to confirm the outcome. ABR can return success without changing requests that were already approved or started. After a timeout, inspect the current state before retrying. Optional approvedby and deniedby emails only take effect when they match an existing ABR portal user; denial also accepts reason.

​
Ticket workflows

This connection supplies the API operations. It does not automatically create tickets, select approvers, or subscribe to ABR webhooks. A ticket workflow must authenticate incoming webhooks, re-fetch the request through the saved connection, resolve the requester in the same Serval organization, and prevent duplicate tickets when events repeat. Use an explicit approval policy before writing decisions back to ABR. See the vendor’s Requests API and Public API documentation.