Delete a person (soft: restorable)

The approved contract does not provide a longer purpose statement for this operation.

App

People & Companies

Contract

People & Companies API 1.5.0

Lifecycle

preview

Runtime

restricted

Operation ID

deletePeopleById

Canonical origin

https://directory.runonvision.com

Purpose and use cases

Delete a person (soft: restorable)

The owning App is Vision People & Companies. Directory owns these facts, its workspace authorization, and its change feed. Apps store a record's id and keep their own data; app-specific fields go in namespaced extensions.

Business use cases and out-of-scope behavior are not yet declared in the approved OpenAPI description.

Request

DELETE https://directory.runonvision.com/api/v1/people/{id}

Authentication and authorization

Send a Vision-issued bearer token for the exact App audience. The token must include the directory entitlement and satisfy the directory workspace required binding.

• Required scope: directory:people:write

Human roles are not declared in OpenAPI. Record-level and business permission checks remain the owning App's authority.

Headers

• Authorization: Bearer <access-token> — required.
• Accept: application/json — recommended where a JSON response is declared.

Undeclared tracing, idempotency, conditional-request, and version headers are not assumed on this page.

Path and query parameters

Request body

This operation declares no request body.

Runnable examples

curl 'https://directory.runonvision.com/api/v1/people/${ID}' \
  --request DELETE \
  --header 'authorization: Bearer ${ACCESS_TOKEN}' \
  --header 'accept: application/json'

const response = await fetch('https://directory.runonvision.com/api/v1/people/${ID}', {
  method: 'DELETE',
  headers: {
    authorization: `Bearer ${ACCESS_TOKEN}`,
    accept: 'application/json',
  },
}

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()

import json
import urllib.parse
import urllib.request

request = urllib.request.Request(
    'https://directory.runonvision.com/api/v1/people/${ID}',
    data=None,
    headers={
    "Accept": "application/json",
    "Authorization": "Bearer <ACCESS_TOKEN>"
},
    method='DELETE',
)
with urllib.request.urlopen(request, timeout=30) as response:
    result = json.load(response)

The current TypeScript reference client covers Platform token exchange and core reads. No native SDK helper is declared for this operation; use the HTTP contract directly and follow the SDK guidance.

Responses

Success response schema

{
  "id": "<id>",
  "deletedAt": "<deletedAt>"
}

Errors and troubleshooting

Error bodies and codes are shown only where the approved contract declares them. Use status, the declared error schema, and any correlation identifier returned by the App; do not infer that two Apps share one envelope.

• 400 — Some details are missing or not valid
• 401 — No credential, or not a valid one
• 403 — Not allowed (also returned for an unknown workspace)
• 404 — No such record in this workspace
• 409 — Duplicate on the record, stale version, reused idempotency key, or sample_record_outbound_blocked (a sample record cannot be given permission to be contacted)
• 500 — An unexpected defect (code internal_error); not retryable, report the requestId
• 503 — The database is temporarily unavailable (code dependency_unavailable); retry with backoff

Collection behavior

Pagination: not declared. Filtering/search: not declared. Sorting: not declared.

Cursor lifetime, cursor binding, stable ordering, maximum traversal, and unknown-filter behavior are not assumed unless stated by a parameter description or schema constraint above.

Operational behavior

• Rate limit: No operation-specific limit or 429 response is declared.
• Retry: Retry only when the documented error model or response headers authorize it. Timeout and backoff values are not declared by this operation.
• Idempotency: No idempotency header or replay window is declared.
• Concurrency: No ETag, If-Match, or optimistic-version header is declared.

Security and privacy

• Keep client credentials and bearer tokens on trusted servers.
• Send only to the exact approved HTTPS origin and audience.
• Treat response data according to the owning App's classification and retention policy; the OpenAPI contract does not itself grant data access.
• Do not log credentials, tokens, complete private payloads, or secrets.

Edge cases and known documentation gaps

• No detailed operation description.
• One or more parameters have no field-level description.
• Business roles, timeout, retry budget, rate value, idempotency window, and concurrency behavior are absent unless explicitly stated above.

Related operations and workflows

• GET /api/v1/people — List or search people
• POST /api/v1/people — Create a person
• POST /api/v1/people/fetch — Get up to 100 people by id, in one call; ids with no record come back in missing
• GET /api/v1/people/{id} — Get a person by id
• PATCH /api/v1/people/{id} — Change a person (absent fields are left alone)
• POST /api/v1/people/{id}/restore — Restore a deleted person
• POST /api/v1/people/{id}/consents — Record a contact permission (appends to the history)
• POST /api/v1/people/{id}/emails — Add emails

Contract history and evidence

• Contract version: 1.5.0
• Approved snapshot SHA-256: e9a21bef4722cf744b269884fe18e2c42858995fb6c78f16ae0aef076c00f5f7
• Approval: Anthony, 2026-11-03T01:23:29.788Z (anthony-docs-live-20261102)
• Download the authoritative OpenAPI 3.1 snapshot