> ## Documentation Index > Fetch the complete documentation index at: https://docs.powerdialer.ai/llms.txt > Use this file to discover all available pages before exploring further. # Delete a contact > Delete the contact itself when your integration intends to remove that PowerDialer record. Requires `contacts:write`, and the contact must belong to the key's workspace and permitted owner scope. Use its numeric PowerDialer ID; deleting by phone number is not supported here. If you only want to take a lead out of one calling list, use the list-membership deletion endpoint instead. This endpoint is a contact deletion, not a membership-only change. It returns `{id,deleted:true}` when the operation succeeds; there is no request body. Persist an `Idempotency-Key` before sending the delete. A matching retry returns the saved success even after the contact has been removed. A new logical delete of an already missing or inaccessible contact returns `404 not_found`. `409 idempotency_conflict` means the key was previously used for another request; do not discard your original operation record. See [membership versus deletion](/guides/contact-lists#list-membership). ## OpenAPI ````yaml /api/openapi.json delete /contacts/{id} openapi: 3.1.0 info: title: PowerDialer API v2 version: 2.0.0 description: >- Connect your CRM, sales workspace or reporting tools to PowerDialer using scoped API keys. Manage contacts and calling lists, read call evidence and analytics, and receive signed events. All example records and IDs are synthetic; replace them with values from your workspace. Shared-key v1 is retired. API availability was verified on 2026-10-08; see /availability for historical data coverage. Legacy outbound webhooks use a separate contract. servers: - url: https://api.migration.powerdialer.ai/api/public/v2 description: Production API v2; availability verified on 2026-10-08. security: - ApiKey: [] tags: - name: Authentication - name: Contacts - name: Calling lists - name: Imports - name: Calls - name: Synchronization - name: Analytics - name: Webhooks - name: Webhook deliveries - name: Incoming webhook payloads paths: /contacts/{id}: delete: tags: - Contacts summary: Delete a contact description: >- Delete the contact itself when your integration intends to remove that PowerDialer record. Requires `contacts:write`, and the contact must belong to the key's workspace and permitted owner scope. Use its numeric PowerDialer ID; deleting by phone number is not supported here. If you only want to take a lead out of one calling list, use the list-membership deletion endpoint instead. This endpoint is a contact deletion, not a membership-only change. It returns `{id,deleted:true}` when the operation succeeds; there is no request body. Persist an `Idempotency-Key` before sending the delete. A matching retry returns the saved success even after the contact has been removed. A new logical delete of an already missing or inaccessible contact returns `404 not_found`. `409 idempotency_conflict` means the key was previously used for another request; do not discard your original operation record. See [membership versus deletion](/guides/contact-lists#list-membership). operationId: deleteContactsById parameters: - name: id in: path required: true schema: type: integer minimum: 1 maximum: 2147483647 description: >- Numeric PowerDialer contact ID, not your CRM externalId. The contact must be inside the credential’s workspace and owner scope. example: 123 - name: Idempotency-Key in: header required: true schema: type: string pattern: ^[A-Za-z0-9._:-]{1,200}$ description: >- Persist one key for this logical operation before sending it. Reuse the same value only with the same method, path and body after a timeout. A changed request returns 409 idempotency_conflict; a matching retry returns the original response. example: 9d6b623c-c132-4d2f-b8cf-7c65d4760dbe responses: '200': description: >- The contact was deleted, or the original successful deletion response was replayed. headers: X-Request-Id: schema: type: string format: uuid RateLimit-Limit: schema: type: integer RateLimit-Remaining: schema: type: integer Idempotency-Replayed: schema: type: string enum: - 'true' - 'false' content: application/json: schema: $ref: '#/components/schemas/Deleted' example: id: 123 deleted: true default: description: >- Error. 400 invalid request; 401 invalid credential; 403 insufficient access; 404 not found; 409 state/idempotency conflict; 413 size limit; 422 verification failure; 429 rate limit (Retry-After seconds); 503 temporary service failure. headers: Retry-After: schema: type: integer X-Request-Id: schema: type: string format: uuid content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: invalid_api_key message: API key is invalid, expired or revoked requestId: 00000000-0000-4000-8000-000000000004 x-codeSamples: - lang: bash label: cURL source: >- # Replace example resource IDs and ownerId with values from your workspace. : "${POWERDIALER_API_KEY:?Set POWERDIALER_API_KEY to your scoped API key}" # Set this once per operation; reuse it with the same request after a timeout. : "${POWERDIALER_REQUEST_ID:?Set POWERDIALER_REQUEST_ID to a new UUID for this operation}" curl --request DELETE \ --url 'https://api.migration.powerdialer.ai/api/public/v2/contacts/123' \ --header "Authorization: Bearer $POWERDIALER_API_KEY" \ --header "Idempotency-Key: $POWERDIALER_REQUEST_ID" components: schemas: Deleted: type: object properties: id: type: integer description: ID of the deleted contact or list. deleted: const: true description: True when deletion succeeded. required: - id - deleted examples: - id: 123 deleted: true Error: type: object properties: error: type: object properties: code: type: string description: Stable machine-readable error code. message: type: string description: Human-readable explanation. requestId: type: string format: uuid description: Request identifier to include when investigating a failure. details: type: array items: type: object properties: path: type: string message: type: string required: - path - message description: Validation errors, when available. required: - code - message - requestId required: - error examples: - error: code: insufficient_scope message: Requires contacts:read requestId: 00000000-0000-4000-8000-000000000004 securitySchemes: ApiKey: type: http scheme: bearer bearerFormat: pd__. description: >- Issued in Developers. Workspace/owner/scopes come from credential, never acting-user headers. API keys cannot manage API credentials. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.