Quiltt API

Name: Quiltt API API
Brand: Quiltt API
Availability: InStock

✓ Official Vendor SpecPaymentsPayouts Transfersbearer17 EndpointsREST

For Agents

Programmatically issue session token, revoke current session. Covers 17 operations with bearer authentication.

Use for: I need to issue session token, I want to revoke current session, Search for validate api key, Find all validate session token

Connect the Quiltt API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Quiltt 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.

Install Jentic One Beta (Self-Hosted)

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

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 Quiltt API API.

Issue session token

Revoke current session

Validate API key

Create profile

List all profiles

GET STARTED

Start building with Quiltt API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Quiltt API API for, with concrete tasks.

★ Payments Operations

Use the Quiltt API to perform payments operations programmatically. The API provides 17 endpoints covering core functionality including issue session token, revoke current session, validate api key.

Call POST /v1/users/sessions to issue session token

Automated Accounts Management

Automate accounts operations by combining multiple Quiltt API endpoints. Agents can revoke current session and then validate api key in a single workflow.

Call DELETE /v1/users/session to revoke current session, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Quiltt API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'issue session token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

17 endpoints — financial data platform api for managing profiles, connections, accounts, transactions, and integrations with financial data providers.

METHOD

PATH

DESCRIPTION

POST

/v1/users/sessions

Issue session token

DELETE

/v1/users/session

Revoke current session

POST

/v1/introspect/api_key

Validate API key

POST

/v1/introspect/session_token

Validate session token

POST

/v1/introspect/processor_token

Validate processor token

POST

/v1/profiles

Create profile

GET

/v1/profiles

List all profiles

GET

/v1/profiles/{id}

Get profile

POST

/v1/users/sessions

Issue session token

DELETE

/v1/users/session

Revoke current session

POST

/v1/introspect/api_key

Validate API key

POST

/v1/introspect/session_token

Validate session token

POST

/v1/introspect/processor_token

Validate processor token

Why though Jentic?

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

Credential isolation

Quiltt API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'issue session token') and Jentic returns the matching Quiltt API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Quiltt API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Alternative payments API

Choose Stripe when you need a different approach to payments operations

Alternative

Adyen

Alternative payments API

Choose Adyen when you need a different approach to payments operations

Complementary

Square

Complementary payments API

Choose Square when you need a complementary approach to payments operations

Complementary

Paypal

Complementary payments API

Choose Paypal when you need a complementary approach to payments operations

FAQs

Specific to using Quiltt API API through Jentic.

What authentication does the Quiltt API use?

The Quiltt API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I issue session token with the Quiltt API?

Yes. Use the POST /v1/users/sessions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Quiltt API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I issue session token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'issue session token'. Jentic returns the matching Quiltt API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Quiltt API have?

The Quiltt API exposes 17 endpoints covering accounts, authentication, connections operations.