scrapewise_delete_api_key
Permanently removes the key with the given id for the authenticated customer.
The key cannot be used after this call returns (any in-flight request using
it will succeed, but new requests get 401). Revocation is a hard delete today;
an `active=false` soft-revoke is on the M1 follow-up list. Idempotent —
deleting a non-existent or wrong-customer id is a silent no-op.
Args:
- id (string, path param, required): the key's MongoDB ObjectId. Get from
scrapewise_list_api_keys.
Returns:
200 OK with empty body. Idempotent (succeeds even if id doesn't exist).
Examples:
- Use when: "revoke the 'ci-deploy' key" → list first to find id, then delete
- Don't use when: you want to ROTATE a key → revoke + create_api_key
(no rotate-in-place API)
Error Handling:
- 401 Unauthorized.
- 500 INTERNAL.[runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP outputSchema is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>"
},
"name": "scrapewise_delete_api_key"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the key's MongoDB ObjectId. Get from scrapewise_list_api_keys. |