Prismatic Integration Platform API

Name: Prismatic Integration Platform API
Brand: Prismatic Integration Platform API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer5 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Prismatic Integration Platform API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Prismatic Integration Platform API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Prismatic Integration Platform API.

List all integrations configured on the Prismatic platform with their metadata

Retrieve detailed configuration for a specific integration by ID

Browse available integration components and their connection types

GET STARTED

Start building with Prismatic Integration Platform API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Prismatic Integration Platform API for, with concrete tasks.

★ Integration Catalog Management

Monitor and inspect the catalog of integrations built on the Prismatic platform. The API lists all configured integrations with their names, descriptions, and IDs. This enables B2B SaaS companies to programmatically audit their integration portfolio, check which integrations exist, and retrieve configuration details for specific integrations without using the Prismatic dashboard.

List all integrations on the Prismatic platform and return the name and ID for each, then retrieve full details for the first integration

Customer Deployment Monitoring

Track which customers have active integration instances deployed and monitor the state of those deployments. The instances endpoint returns all deployed integration instances across the customer base, while the customers endpoint shows which organizations are configured. This enables proactive monitoring of integration health across a B2B customer portfolio.

List all customers, then list all instances, and cross-reference to identify customers without any active integration instances

Component Discovery for Integration Building

Browse the available component catalog to identify connectors and actions that can be used when building new integrations. Components represent the building blocks of Prismatic integrations, each providing connections to external services. Agents can query the catalog to determine which services are supported before designing a new integration flow.

List all available components on the Prismatic platform and count how many are currently registered

AI Agent Integration Platform Management

AI agents can use the Prismatic API through Jentic to automate integration platform operations such as auditing deployment status, discovering available components, and monitoring customer integration health. Jentic provides credential isolation and operation schemas so agents manage the integration platform without accessing raw bearer tokens.

Search Jentic for 'list prismatic integrations', load the listIntegrations operation schema, and execute to retrieve the full integration catalog

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for prismatic integration platform api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/integrations

List all configured integrations

GET

/integrations/{id}

Get details of a specific integration

GET

/components

List available integration components

GET

/customers

List customers on the platform

GET

/instances

List deployed integration instances

GET

/integrations

List all configured integrations

GET

/integrations/{id}

Get details of a specific integration

GET

/components

List available integration components

GET

/customers

List customers on the platform

GET

/instances

List deployed integration instances

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Prismatic bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped session credentials per request and never see the raw platform API token in their context.

Intent-based discovery

Agents search by intent (e.g., 'list prismatic integrations' or 'check integration deployment status') and Jentic returns the matching operation with request/response schemas, so agents call the correct endpoint without navigating documentation.

Time to first call

Direct Prismatic API integration: 1-2 days for auth setup and endpoint mapping. Through Jentic: under 30 minutes using pip install jentic, search, load, and execute.

FAQs

Specific to using Prismatic Integration Platform API through Jentic.

Why is there no official OpenAPI spec for Prismatic Integration Platform API?

Prismatic does not publish an OpenAPI specification for their REST API. Jentic generates and maintains this spec so that AI agents and developers can call Prismatic Integration Platform API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Prismatic API use?

The Prismatic API uses Bearer token authentication. Include your API token in the Authorization header as 'Bearer your-token'. Through Jentic, the bearer token is stored encrypted in the vault and agents receive scoped access without handling raw credentials.

Can I list all deployed integration instances with the Prismatic API?

Yes. The GET /instances endpoint returns all deployed integration instances across your customer base. Each instance includes its configuration and deployment status. Combined with GET /customers, you can map which customers have active deployments and identify any without running instances.

What are the rate limits for the Prismatic API?

The Prismatic API specification does not document explicit rate limits. Standard API rate limiting practices apply. If you receive 429 responses, implement exponential backoff. For high-volume monitoring use cases, cache results locally and poll at reasonable intervals.

How do I discover available integration components through Jentic?

Search Jentic for 'list prismatic components', load the listComponents operation schema, and execute the call. The response returns all available connector components that can be used to build integrations. Install with pip install jentic and set your JENTIC_AGENT_API_KEY environment variable.

Is the Prismatic API the same as their GraphQL API?

No. Prismatic primarily uses a GraphQL API for their full platform capabilities. This REST API covers a subset of operations for listing integrations, components, customers, and instances. For advanced operations like creating integrations or configuring flows, the GraphQL API provides broader coverage.