Onparallel Parallel API
★ Only Publicly Available OpenAPI DocumentProductivityForms Surveysbearer5 EndpointsREST
For Agents
Send a structured data-collection petition to a recipient and download replies and attachments using bearer-token authentication.
Use for: I need to send a client onboarding form with branching questions, Find all templates available in my Parallel account, Add a new recipient to an existing petition, Get the field schema for a petition I am about to send
Not supported: Does not handle e-signature, contract negotiation, or scheduling — use for sending structured data-collection petitions and reading replies only.
Jentic publishes the only available OpenAPI specification for Parallel API, keeping it validated and agent-ready. Parallel is a structured-data collection platform that uses petitions, which are smart forms with branching logic and document attachments, to gather information from clients, partners, or employees. The API lets developers create petitions from templates, send them to recipients, and download replies for downstream processing. It is built for back-office workflows in financial services, legal, and operations where unstructured email and PDFs make data entry slow and error-prone.
Install Jentic One Beta
Connect the Parallel API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Parallel 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.
1
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 | sh2
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 instanceJentic 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 Parallel API.
Create a petition from an existing template and pre-fill its fields
Add one or more recipients to an existing petition
Read the field definitions of a petition to map them onto an internal schema
List the templates available to the calling account
Download a recipient's reply file when the petition is completed
Use Cases
Patterns agents use Parallel API for, with concrete tasks.
★ Client onboarding for financial services
Wealth managers, accountants, and lenders use Parallel to collect KYC information, supporting documents, and disclosures from new clients. The API lets the firm's CRM or onboarding tool create a petition from a template, pre-fill known fields, and send the link to the client. Replies come back as structured data plus attached files, ready to be loaded into the back office without re-keying.
POST /petitions with a template id and the client's prefill data, then POST /petitions/{petitionId}/recipients with the client's name and email.
Legal intake and document collection
Law firms run client intake through structured forms that branch based on matter type. Parallel's petition model handles the conditional logic, so the firm only sees the questions relevant to a given engagement. The API surfaces the resulting field map and reply files for ingestion into the matter management system, replacing PDF email loops.
GET /templates to find the intake template, POST /petitions to instantiate it, then GET /petitions/{petitionId}/fields to confirm the field mapping before sending.
AI agent structured collection through Jentic
An AI agent that handles back-office onboarding can use Parallel through Jentic to send a structured form rather than asking the client to write a long email. The agent searches Jentic for the petition operation, loads the schema, and posts the petition with the recipient. Once the recipient replies, a follow-up agent can pull the reply file and parse it into the system of record.
Search Jentic for 'send a parallel petition', load the POST /petitions operation, and execute it for a known template_id with a single recipient.
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for parallel api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/petitions
Create a new petition from a template
GET
/petitions/{petitionId}/fields
Read the field schema of a petition
POST
/petitions/{petitionId}/recipients
Add recipients to a petition
GET
/petitions/{petitionId}/replies/{replyId}/download
Download a recipient's reply file
GET
/templates
List available petition templates
POST
/petitions
Create a new petition from a template
GET
/petitions/{petitionId}/fields
Read the field schema of a petition
POST
/petitions/{petitionId}/recipients
Add recipients to a petition
GET
/petitions/{petitionId}/replies/{replyId}/download
Download a recipient's reply file
GET
/templates
List available petition templates
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Parallel uses a long-lived bearer token tied to the workspace. Jentic stores it in the vault and injects it at execution time, which is important because the same token can both create petitions and download recipient replies that contain client PII.
Intent-based discovery
Agents search Jentic with intents like 'send a structured client form' or 'download a petition reply' and Jentic returns the matching Parallel operations with their input schemas, so the agent does not have to read the onparallel.com developer docs to wire up the call.
Time to first call
Direct Parallel integration: 2-3 days for bearer auth, template selection, recipient management, and reply download. Through Jentic: under 1 hour to search, load the schema, and send the first petition.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Parallel API through Jentic.
Why is there no official OpenAPI spec for Parallel API?
Parallel publishes its API as developer-facing HTML at onparallel.com/developers/api but does not ship a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Parallel 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 Parallel API use?
Parallel uses HTTP bearer authentication. Pass your API key as 'Authorization: Bearer <key>' on every request. Through Jentic, the bearer token is held in the vault and injected at execution time, which keeps client-data tokens out of agent prompts and logs.
Can I send a petition to multiple recipients?
Yes. Create the petition with POST /petitions, then call POST /petitions/{petitionId}/recipients once per recipient or in a single batch payload. Each recipient receives their own link so replies can be tracked individually against the same petition.
What are the rate limits for the Parallel API?
Parallel does not publish a global rate limit in its OpenAPI spec. In practice, the platform handles bursts from typical onboarding workflows comfortably, and integrations should back off on 429 responses if they appear during bulk sends. Surface area is small (5 endpoints), so rate limit pressure is unusual outside of bulk-import jobs.
How do I download a recipient's reply through Jentic?
Install the SDK with 'pip install jentic', search for the operation with the query 'download parallel reply', then load the GET /petitions/{petitionId}/replies/{replyId}/download operation, and execute it with the petitionId and replyId. Jentic streams the reply file back to the agent.
How do I find the right template to send?
Call GET /templates to list the templates configured in the account, then use the matching template_id when calling POST /petitions. The template id is also what governs the field schema that GET /petitions/{petitionId}/fields will return.
GET STARTED