Skip to main content
Use the @bijectionhq/connectors/foundry entrypoint to declare Palantir Foundry resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Ontology objects

actions: Object listing with single-attempt Apply Action commands

The following example matches configuration standard.
The function references identify application policy queries. Implement those policies in your application; the references alone grant no authority.

Configuration: standard

Case: foundry/objects/actions/standard. Connection and resource configuration are declared by this exact case. Credential kind: foundry. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: objects
Commands
Recorded checks Verification scope Each evidence category has independent scope. A matching recorded pass applies only to its exact artifacts and configuration. Installed connections report their own identity, authority and current status.

Configuration: readOnly

Case: foundry/objects/actions/readOnly. Connection and resource configuration are declared by this exact case. Credential kind: foundry. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: objects
Recorded checks Verification scope Each evidence category has independent scope. A matching recorded pass applies only to its exact artifacts and configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection reads the enrollment’s own origin (baseUrl) with a foundry bearer credential: a user or service token, or one minted from OAuth2 client credentials with api:ontologies-read api:ontologies-write. A binding names one ontology (ontology, its API name or RID); the ontology’s RID is the connection’s identity. objects.actions reads one object type. The listing pages by nextPageToken and claims no coverage; a point read’s 404 withdraws an object. Each declared action is a collection command that posts apply once with VALIDATE_AND_EXECUTE. HTTP 200 means only that Foundry processed the request: validation.result VALID confirms the command and INVALID rejects it. Named refusals that Foundry raises before applying edits reject it; ApplyActionFailed, a timed-out Function, throttling and server errors stay unknown. Foundry has no idempotency key and no lookup by request. The action’s own operationId, which edits history could search, arrives only in the response. So a lost or undecided answer is never resent, and reconciliation stays unknown. Bulk dataset, view, object, link and media-set imports run on customer compute through the bijection-foundry worker job, not this connector. Nothing here has run against Foundry or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 67ee90ebf694b6d250995a5825db38a270a591bd08c7e6412f688ce984239514. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.