Listeners

Listeners enable the Palantir platform to receive events from other systems that do not support OAuth 2.0 authentication directly or cannot provide a configurable payload compatible with standard Foundry API endpoints.

To accept inbound connections from these systems, data connection listeners provision a URL endpoint, implement the specific message signing or other verification schemes for specific external systems, and allow a simple and low-latency mechanism to receive data feeds into Foundry.

Types of listeners

Foundry supports three types of listeners, each designed for different integration scenarios and processing approaches:

HTTPS listeners

HTTPS listeners receive webhook requests from external systems through HTTPS endpoints. Events are written to a stream, enabling processing through Automate, streaming pipelines, or batch processing using the stream's backing dataset.

Learn more about HTTPS listeners.

WebSocket listeners [Experimental]

WebSocket listeners are primarily designed for real-time audio and telephony workflows, enabling bidirectional communication between Foundry and external services such as Twilio, Genesys, and Azure Communication Services. Inbound WebSocket connections are processed directly by a compute module where you can host a custom WebSocket server.

Learn more about WebSocket listeners.

Email listeners

Email listeners allow Foundry to receive inbound emails at dedicated email addresses for downstream processing. Each listener has a unique email address scoped to your enrollment, and applies sender allowlisting, email authentication, and attachment validation before forwarding content.

Learn more about email listeners.

When to use listeners

Listeners are one of many options to ingest data into the Palantir platform. Before setting up a listener, evaluate whether your use case meets the criteria below for inbound connections or for external systems that cannot be customized.

For inbound connections

Listeners can be used solely for inbound connections when an external system establishes the connection into Foundry. To make requests from Foundry to external systems, use sources. No-code capabilities are also available, such as syncs and outbound webhooks. Custom code-based data connections are also available with external transforms, functions, compute modules, and more.

When the external system cannot be customized

Listeners should only be used when the external system cannot be customized to connect to Foundry. For example, many webhook and WebSocket providers have bespoke payload shapes and cannot properly authenticate with Foundry, instead relying on other authentication and verification protocols.

For cases where you can customize the external system, such as when the system allows you to write custom integration code, use the public API instead. With the public API, you can push to streams, upload to datasets, or directly interact with your ontology.

---

All product names, logos, and brands mentioned are trademarks of their respective owners. All company, product, and service names used in this document are for identification purposes only.