Skip to content
LeadityDocs

Validations

Stop validation

Stop a live validation run: keep what it answered and refund the rest.

POSTapi.leadity.io/v1/validations/{id}/stop
Scope writeMCP tool stop_validation

Stops a queued or running validation run. It settles on what has been answered and refunds the rest at once; items not answered stay unanswered and cost nothing. A stopped run cannot be resumed, and one that is already final answers not_running. Needs a key with the write scope.

Headers

Authorizationstringrequired

Bearer, a space, then an API key: Bearer lk_api_... An MCP key is refused here with wrong_key_kind.

Path parameters

idstringrequired

The validation run's id, as create_validation and list_validations answer it.

1 to 64 characters, matches ^[A-Za-z0-9]{1,64}$.

Response

idstringrequired
creditsUsedintegerrequired

Credits kept for the items answered.

refundedintegerrequired

Credits returned to the balance.

Errors

Every refusal answers { error, message } with the status below. The full list is on the Errors page.

CodeStatusMeaningExtra fields
unauthorized401The API key is missing, malformed, revoked or expired.-
wrong_key_kind401This key opens the other surface: an API key works on the HTTP API, an MCP key on the MCP server.-
insufficient_scope403The key does not carry the scope this operation needs.requiredScope: The scope the operation needs: read, write or spend.
account_suspended403The account is suspended.-
email_not_verified403The account's email address is not verified yet.-
invalid_body400The request does not match the operation's schema.issues: The problems found, each with path (the field as a dotted path, led by the part of the request it travels in: path, query or body, such as body.items.1) and message (what is wrong there).
not_found404No such resource on this account.id: On export_scrapes: the first id that is not one of the account's scrapes.
not_running409The validation run is already final. The body carries its status.status: The run's final status.
rate_limited429Too many requests. Wait for the Retry-After seconds and try again.retryAfterSeconds: The seconds to wait, the same number as the Retry-After header.
try_again503Leadity could not answer just now. Retry in a moment, with the same Idempotency-Key on a spending call.retryAfterSeconds: When a request with this Idempotency-Key is still being processed: the seconds to wait before retrying with the same key, as the Retry-After header says.
internal_error500Something failed on our side. Nothing was charged twice.body: On the MCP server, when Leadity answered in a shape the tool does not publish: that answer as it came.