> ## Documentation Index > Fetch the complete documentation index at: https://apidocs.ripio.com/llms.txt > Use this file to discover all available pages before exploring further. # Delete External Contact > Deletes/unlinks a contact, identified by the composite key `(type, id)` (same pattern as `banking/accounts/{rail_type}/{id}/`): the auto-incrementing IDs of the crypto/bank store and of the rp_tag store collide with each other, so `type` is required to disambiguate and is authoritative for resolving the entity. `type=crypto`/`type=bank` unlinks (soft delete) the contact from the account; `type=rp_tag` deletes the P2P contact. Returns `404` if the `id` does not exist within the store selected by `type`, including when the `id` exists but belongs to a different type (no existence leak across types). Requires the `contacts_write` permission. The account must be fully operative. --- **Authorization** - Requires a valid API key. ## OpenAPI ````yaml delete /wallet/contacts/{type}/{pk}/ openapi: 3.0.0 info: title: Ripio Gateway description: Ripio API - Services documentation. version: 0.1.0 x-logo: url: https://cwstatic.nyc3.digitaloceanspaces.com/1996/bitcointrade.png servers: - url: https://api.ripio.com description: Production environment security: [] paths: /wallet/contacts/{type}/{pk}/: delete: tags: - Ripio Wallet summary: contacts - Delete external contact description: >- Deletes/unlinks a contact, identified by the composite key `(type, id)` (same pattern as `banking/accounts/{rail_type}/{id}/`): the auto-incrementing IDs of the crypto/bank store and of the rp_tag store collide with each other, so `type` is required to disambiguate and is authoritative for resolving the entity. `type=crypto`/`type=bank` unlinks (soft delete) the contact from the account; `type=rp_tag` deletes the P2P contact. Returns `404` if the `id` does not exist within the store selected by `type`, including when the `id` exists but belongs to a different type (no existence leak across types). Requires the `contacts_write` permission. The account must be fully operative. --- **Authorization** - Requires a valid API key. parameters: - in: path name: type required: true description: >- Contact type discriminator. Required to disambiguate colliding IDs across the crypto/bank and rp_tag stores. schema: example: crypto type: string - in: path name: pk required: true description: >- ID of the contact/entity to delete, within the store selected by `type`. schema: example: 42 type: integer - in: header name: authorization required: true description: The API key as a string. schema: type: string - in: header name: signature required: true description: >- See the [Generating Signature](/static/api/authentication#generating-signature) section for more details. schema: type: string - in: header name: timestamp required: true description: >- A timestamp in milliseconds. See the [Timestamp Security](/static/api/authentication#timestamp-security) section for more details. schema: type: number - in: header name: timstamp-tolerance required: false description: >- An additional, non-required parameter, that you can send to specify the number of milliseconds after the timestamp for the request to be valid. See the [Timestamp Security](/static/api/authentication#timestamp-security) section for more details. schema: type: number responses: '200': description: '' content: application/json: schema: description: Contact deleted/unlinked successfully. properties: error_code: type: string example: null message: type: string example: null data: properties: id: type: integer deleted: type: boolean type: object required: - error_code - message - data type: object '400': description: Error response 400 '401': description: Error response 401 '403': description: '' content: application/json: schema: description: Gateway error response wrapper. properties: error_code: description: >- Error code identifying the failure. Gateway codes: 'ERR_0001'=internal error, 'ERR_0003'=bad request, 'ERR_0004'=not found, 'ERR_0006'=service unavailable, 'ERR_0008'=unauthorized, 'ERR_0009'=forbidden, 'ERR_0010'=method not allowed, 'ERR_0012'=too many requests. type: string example: ERR_0008 message: description: Human-readable error message. type: string example: Invalid Gateway JWT data: description: >- Null for most errors. May contain field-level validation errors as an object with a `detail` array. type: object example: null required: - error_code - message - data type: object '404': description: '' content: application/json: schema: description: Gateway error response wrapper. properties: error_code: description: >- Error code identifying the failure. Gateway codes: 'ERR_0001'=internal error, 'ERR_0003'=bad request, 'ERR_0004'=not found, 'ERR_0006'=service unavailable, 'ERR_0008'=unauthorized, 'ERR_0009'=forbidden, 'ERR_0010'=method not allowed, 'ERR_0012'=too many requests. type: string example: ERR_0008 message: description: Human-readable error message. type: string example: Invalid Gateway JWT data: description: >- Null for most errors. May contain field-level validation errors as an object with a `detail` array. type: object example: null required: - error_code - message - data type: object '409': description: '' content: application/json: schema: description: Gateway error response wrapper. properties: error_code: description: >- Error code identifying the failure. Gateway codes: 'ERR_0001'=internal error, 'ERR_0003'=bad request, 'ERR_0004'=not found, 'ERR_0006'=service unavailable, 'ERR_0008'=unauthorized, 'ERR_0009'=forbidden, 'ERR_0010'=method not allowed, 'ERR_0012'=too many requests. type: string example: ERR_0008 message: description: Human-readable error message. type: string example: Invalid Gateway JWT data: description: >- Null for most errors. May contain field-level validation errors as an object with a `detail` array. type: object example: null required: - error_code - message - data type: object '429': description: '' content: application/json: schema: description: Gateway error response wrapper. properties: error_code: description: >- Error code identifying the failure. Gateway codes: 'ERR_0001'=internal error, 'ERR_0003'=bad request, 'ERR_0004'=not found, 'ERR_0006'=service unavailable, 'ERR_0008'=unauthorized, 'ERR_0009'=forbidden, 'ERR_0010'=method not allowed, 'ERR_0012'=too many requests. type: string example: ERR_0008 message: description: Human-readable error message. type: string example: Invalid Gateway JWT data: description: >- Null for most errors. May contain field-level validation errors as an object with a `detail` array. type: object example: null required: - error_code - message - data type: object ````