Listeners [Beta]

Event 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 standard Foundry API endpoints.

To accept inbound events 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 event-based data feeds into Foundry.

When to use listeners

Listeners are one of many options to ingest data into the Palantir platform. Before setting up your listener, evaluate whether your use case is compatible with the following criteria required for listeners:

1. Use for inbound connections
2. Use for low-throughput event streams
3. When the external system cannot be customized

For inbound connections

Listeners can be used solely for inbound requests (when an external system pushes data to Foundry). To make requests from Foundry to external systems, you should leverage sources. There is a suite of no-code capabilities availble such as syncs and outbound webhooks available for use. Custom code-based data connections are also available with external transforms, TypeScript and Python functions, compute modules, and more.

For low-throughput streams

Only low-throughput event streams should be pushed to your listener. Listeners are rate-limited at approximately 50 requests per second, so integrations requiring substantially higher throughput should instead leverage streaming syncs or the public streaming API endpoints when possible.

If your use case requires a higher rate limit than what is currently provided, and listeners are the only appropriate integration option, contact Palantir Support to discuss increasing the limit for your listener.

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 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, the public API should be used instead. With the public API, you can push to streams, upload to datasets, or directly interact with your ontology.

Enable listeners

Listeners need to be enabled for your enrollment before listeners can be used. To do this, a user with the Enrollment administrator role must navigate to Control Panel > Data Connection and enable the Listeners toggle. While this toggle allows the usage of listeners in the enrollment, individual listeners will still need to be approved by a user with the Information security officer role.

Disabling this toggle will result in any existing listeners in your enrollment to stop processing requests.

Configure a listener

Navigate to Data Connection > Listeners to connect the Palantir platform to systems and workflows outside it.

For information on securely configuring listeners and incoming data, refer to the listener security documentation.

This dataset can subsequently be explored within Data Lineage to further provide you with insight into data transformations and flows.

Supported listeners

---

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.