Remove an entity from continuous monitoring
Take an entity out of continuous monitoring by its monitored-record id. No further re-screens or webhooks are produced for it. An unknown id — or a second delete for an id already removed — returns 404.
ApiKeyAuthAuthorizationBearer <token>Your API key, sent as Authorization: Bearer <key>.
id*stringThe monitored-record id returned by PUT /monitor.
Removed; the monitored-record id that left monitoring.
application/json- response
id*string^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidcurl -X DELETE "https://example.com/monitor/string" \ -H "Authorization: Bearer $EXCLIA_API_KEY"{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08"}Current billing-period consumption GET
This billing period’s metered consumption — /v1/screen calls and monitored record-months, priced — matching exactly what is metered for billing over the same period, so you can reconcile before the invoice arrives.
Screen one person or organization POST
Screen a single person or organization synchronously against the current pinned list versions. Returns status `clear` or `potential_match` with per-field evidence and provenance — never an automated "excluded" verdict. Each successful call counts toward the org’s metered API usage. Pass an optional `Idempotency-Key` header so retries are not double-counted.