---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/80605#article
headline: "80605: Proxy Identifier Not In Service"
url: https://www.twilio.com/docs/api/errors/80605
inLanguage: en
dateModified: 2026-06-08T12:04:59.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 80605: Proxy Identifier Not In Service

Log Level: WARNING

## Description

This warning means the Proxy Identifier you supplied is not part of the Proxy `Service` handling the request. In Proxy, phone numbers are associated directly with a specific `Service`, and when you set `proxyIdentifier` for a Participant, that number must already be in that service's phone number pool. If you omit `proxyIdentifier`, Proxy selects a number from the pool automatically.

### Possible causes

* You provided `proxyIdentifier` for a Participant, but that Twilio number was never added to the target Proxy `Service`.
* The number is associated with a different Proxy `Service`. A Twilio number can be associated with only one Proxy Service at a time.
* The request used the wrong `Service` or `Session` SID, so Proxy checked a different service than the one that contains the number.

### Possible solutions

* Add the Twilio number to the correct Proxy `Service` before you assign it as `proxyIdentifier`.
* If you do not need to force a specific masked number, remove `proxyIdentifier` and let Proxy select an available number from the service's pool.
* Verify that you are using the intended `Service` and `Session` SIDs, then retry with a number that belongs to that service. This follows from the way Participant requests are scoped to a service and session, and the way Proxy numbers are attached to a service.

#### Additional resources

* [Proxy Participant resource](/docs/proxy/api/participant)
* [Proxy Phone Number resource](/docs/proxy/api/phone-number)
* [Proxy Quickstart](/docs/proxy/quickstart)