• Documentation
    • Search documentation
    karat

    +

    K

    API Reference ↗
    Developer toolchainDeveloper ConsoleOverview

    Developer Console

    Use Developer Console to build and manage Custom Applications and their associated authorization clients and SDKs. A custom application allows developers to extend Foundry capabilities with custom logic hosted in or outside of Foundry. Legacy OAuth clients are also managed in Developer Console.

    Developer Console or SuperRepo?

    Developer Console is the UI-first way to configure a custom application: you assemble it here, and Foundry generates and publishes the SDK for the resources you add. If you would rather define the application in code, review SuperRepo. A SuperRepo is a pro-code monorepo that holds your Ontology definitions, functions, and frontend together. It generates the SDK locally as you edit, and ships as a Marketplace product that you can deploy to multiple enrollments from your own CI system.

    Custom applications

    The primary components of a custom application are as follows:

    1. Authorization client: An OAuth client that allows human and service users programmatic access to Foundry.

    2. SDKs: One or more SDKs generated from resources added to an application. See Application restrictions.

    3. SDK documentation: Auto-generated API documentation and code snippets tailored to your application's SDK.

    4. Permissions: User and application-level access controls. See Permissions.

    5. Metrics: Usage and performance insights for your application. See Application metrics.

    6. Web hosting (optional): Host a custom frontend on a Foundry subdomain.

    7. Code repository (optional): A linked code repository resource for application code.

    8. Marketplace distribution (optional): Package and deploy applications across Foundry environments. See Install a Developer Console application with Marketplace.

    9. MCP server (optional): Expose ontology resources as Model Context Protocol tools for external AI agents. See Ontology MCP.

    To get started building a custom application, see Create a new Developer Console application.

    OAuth clients

    OAuth clients are a legacy primitive similar to custom applications, but contain only an authorization client and none of the other capabilities listed above. OAuth clients have typically been used to grant unrestricted access to programmatic users. It is recommended that unrestricted applications be used instead of an OAuth client.

    Developer Console landing page

    The Developer Console landing page lists the custom applications and OAuth clients that you have access to.

    For more information on access requirements, review the permissions documentation.

    The Developer Console home page lists all applications and OAuth clients.

    Application pages

    Application overview

    From the application overview page, you can:

    • View website hosting status and generated SDK versions.
    • See the ontology resources included in your application's OSDK.
    • Edit the application metadata or delete the application.

    The application overview page displays resource counts and sharing options.

    For OAuth clients, see Managing an OAuth client in Developer Console.

    OAuth and restrictions

    Configure the authentication flow and resource access restrictions for your application. The restrictions ensure tokens only grant access to resources approved for the application.

    Learn more about configuring permissions and application restrictions.

    The OAuth and restrictions page displays authentication and resource configuration.

    SDK documentation

    Each application includes auto-generated API documentation tailored to its SDK content. You can access it by selecting API documentation from the left panel.

    The API documentation includes:

    • Installation guides for your application-specific SDK.
    • Code examples for loading individual objects and fetching pages of data.
    • Reference materials for each ontology object type, action type, and function.

    Use the language dropdown menu to switch between TypeScript, Python, and other supported languages.

    The application documentation page shows API reference and code examples.

    Sharing and tokens

    Share your application with users, groups, and organizations. Generate long-lived scoped tokens for programmatic access.

    The application permissions page displays sharing settings and token generation.

    Web hosting

    Host frontend-only applications, such as React SPAs, directly on Foundry, eliminating the need for external hosting infrastructure.

    The web hosting page displays deployment options and domain configuration.

    For more detail, review the documentation on hosting an OSDK application on Foundry.

    Metrics

    Monitor application performance including request volume, success rates, and API latency.

    The application metrics page shows request volume and performance data.

    Learn more about application metrics.

    MCP

    Configure your application as an MCP server to expose ontology resources to external AI agents. When enabled, AI agents can discover and use your application's object types, action types, and query functions as MCP tools.

    Learn more about Ontology MCP.

    Limits

    By default, each Developer Console application is limited to a total of 1000 data resources and resource access restrictions. Reach out to a Palantir administrator if you encounter this limitation.