---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/91001#article
headline: "91001: Sink could not be found"
url: https://www.twilio.com/docs/api/errors/91001
inLanguage: en
dateModified: 2026-06-09T11:00:42.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 91001: Sink could not be found

Log Type: APPLICATION

Log Level: ERROR

## Description

Twilio returns this error when your Event Streams request references a sink that Twilio cannot find. In Event Streams, a sink is the destination for subscription data, and each sink is identified by a 34-character SID with the `DG` prefix.

### Possible causes

* The request used a sink `Sid` that does not match any existing Event Streams sink. Twilio fetches sink configurations by SID.
* The sink was deleted, and your application is still using the deleted sink SID.
* The request was sent with credentials for a different account or subaccount than the one that owns the sink. Twilio lists and returns sinks for the account associated with the request.

### Possible solutions

* List your sinks for the account making the request and confirm that the sink still exists before you fetch, update, or reference it.
* Verify that the sink SID is copied exactly and that it is a 34-character sink SID with the `DG` prefix.
* If the sink was deleted, create a new sink and update your application or subscription workflow to use the new sink SID.
* If you use subaccounts, make the request with credentials for the account that owns the sink.

#### Additional resources

* [Sink resource](/docs/events/event-streams/sink-resource)
* [Subscription resource](/docs/events/event-streams/subscription)
* [Event Streams overview](/docs/events)