Palantir Event and Subscription Integration

Overview

Start from the event producer and delivery guarantee: real-time Ontology object updates use OSDK or Object Set Watcher WebSocket subscriptions, while monitoring notifications and outbound integrations use their documented webhook surfaces. Never invent a general ontology.object.created registration API.

Prerequisites

• Identify the producer, consumer, object set or monitoring view, supported delivery surface, data sensitivity, latency objective, and recovery behavior.
• Confirm the generated OSDK version or direct WebSocket contract, or the configured Data Connection webhook required by monitoring.
• Read references/official-docs.md and verify target-enrollment feature access.
• Prepare a non-production object set or monitoring view and an idempotent consumer.

Current Contract

• TypeScript OSDK subscriptions require a compatible generated OSDK/client and receive object-set updates through .subscribe.
• Direct Object Set Watcher subscriptions use a documented WebSocket endpoint and authenticate with a bearer token encoded in the WebSocket subprotocol format.
• Subscriptions can report an out-of-date state that requires reloading the full object set.
• Monitoring views can route notifications through webhooks configured in Data Connection; that is distinct from Ontology object subscriptions.