canonical: https://jentic.com/apis/precisely.se/precisely

# Precisely Se Precisely Public API

Jentic publishes the only available OpenAPI specification for Precisely Public API, keeping it validated and agent-ready. The Precisely API is a contract automation platform that enables document lifecycle management including template-based project creation, document drafting, e-signature requests, approval workflows, and metadata management. It supports 73 endpoints covering organizations, templates with references, projects, documents with versioning, signees, signature requests, reminders, folders, teams, and webhook subscriptions for event-driven integrations. Rate limited to 30 requests per minute per organization.

## For AI agents

Automate contract workflows including document creation from templates, e-signature requests, approval management, and document metadata tracking for organizations.

## Scope

Does not handle payment processing, CRM contact management, or calendar scheduling -- use for contract automation and e-signatures only.

## Capabilities

- Draft contracts from templates by answering reference questions programmatically
- Send documents for e-signature with configurable signee lists and reminders
- Track document status changes through webhook event subscriptions
- Search and filter documents by status, metadata, and creation date
- Manage approval workflows with initial and final approver assignments
- Import external documents into the contract management system
- Organize contracts into folders with team-based access control

## Use cases

### Automated Contract Generation

Generate contracts programmatically by creating projects from templates and providing answers to reference questions. The Precisely API supports template-based drafting where each template defines document content, default signees, and configurable references. Projects created from templates produce ready-to-sign documents without manual drafting.

Example prompt: List templates via GET `/organizations/{orgId}/templates`, get references for template via GET `/organizations/{orgId}/templates/{templateId}/references`, then create a project via POST `/organizations/{orgId}/templates/{templateId}/projects` with answer values

### E-Signature Workflow Management

Send documents for electronic signature by creating signature requests with specified signees. The API manages the full signing lifecycle including adding signees, triggering signature requests, sending reminders, and tracking completion status. Signed documents are available for download as PDF.

Example prompt: Add signees to document via POST `/organizations/{orgId}/documents/{docId}/signees`, then create a signature request via POST `/organizations/{orgId}/documents/{docId}/signature-request`

### Contract Status Monitoring

Monitor contract status changes in real time by subscribing to webhook events. The API delivers callbacks when documents change status (draft, sent, signed, etc.), enabling downstream systems to trigger actions like CRM updates, billing, or compliance checks when contracts reach specific milestones.

Example prompt: Subscribe to document status change events via the webhook subscription endpoint, then verify callback delivery using the subscription callbacks listing

### AI Agent Contract Automation via Jentic

Enable AI agents to manage contract workflows through Jentic by searching for Precisely operations, loading schemas, and executing calls. Agents can create contracts from templates, send them for signing, and check status without managing JWT tokens or API keys directly.

Example prompt: Search Jentic for 'create contract from template', load the Precisely project creation schema, and execute POST `/organizations/{orgId}/templates/{templateId}/projects` with the required reference answers

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/organizations/{organizationId}/documents` | List documents with pagination and filtering |
| POST | `/organizations/{organizationId}/documents/search` | Search documents by status and metadata |
| POST | `/organizations/{organizationId}/templates/{templateId}/projects` | Create a project from template |
| POST | `/organizations/{organizationId}/documents/{documentId}/signature-request` | Send document for e-signature |
| POST | `/organizations/{organizationId}/documents/{documentId}/signees` | Add signees to a document |
| GET | `/organizations/{organizationId}/documents/{documentId}/pdf` | Download document as PDF |
| GET | `/organizations/{organizationId}/templates/{templateId}/references` | Get template reference questions |
| POST | `/authenticate` | Authenticate and obtain JWT token |

## Key resources

- **Documents** — Contracts and documents with versioning, metadata, and status tracking
- **Projects** — Template-based contract drafting sessions with reference answers
- **Templates** — Reusable contract templates with configurable references and signees
- **Signature Requests** — E-signature workflows with signee management and reminders
- **Organizations** — Organization-level access and team management
- **Folders** — Document organization and access control

## Why Jentic

- **Setup:** Wiring the Precisely Public API by hand means obtaining a JWT through /authenticate or setting the X-API-KEY header against api.precisely.se, then refreshing tokens and threading organization ids yourself. Through Jentic you install once, import the Precisely Public API from the API Directory, store the token or API key once, and your agent calls it.
- **Permission scoping:** Precisely puts the organization and document ids in the URL path (`/organizations/{organizationId}/documents/{documentId}/...`), so a rule can pin your agent to one organization: it can create documents and read that organization's content and nothing else. You choose the operations it may call, so sending a signature request is not included unless you add it.
- **Credential handling:** Your Precisely JWT or API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a contract from a template' or 'send a document for e-signature', and Jentic returns the matching Precisely operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **PandaDoc API** — Document automation with proposals, quotes, and e-signatures for sales teams
- **Salesforce API** — CRM platform for managing client relationships that trigger contract generation
- **Calendly API** — Scheduling platform for booking contract review meetings

## FAQ

### Why is there no official OpenAPI spec for Precisely Public API?

Precisely does not publish a standalone downloadable OpenAPI specification file. Jentic generates and maintains this spec so that AI agents and developers can call Precisely Public API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Precisely Public API use?

The Precisely API supports two authentication methods: bearer token authentication using a JWT obtained from the POST /authenticate endpoint, and API key authentication using the X-API-KEY header. Through Jentic, credentials are stored encrypted and agents receive scoped access without managing tokens directly.

### What are the rate limits for the Precisely Public API?

The Precisely API allows up to 30 requests per minute per organization. Rate limit status is returned in response headers: X-Ratelimit-Limit shows the maximum, X-Ratelimit-Remaining shows requests left in the current window, and X-Ratelimit-Reset shows when the window resets in UTC epoch seconds.

### Can I create contracts from templates with the Precisely API?

Yes. Use GET `/organizations/{orgId}/templates/{templateId}/references` to retrieve the questions defined in a template, then POST `/organizations/{orgId}/templates/{templateId}/projects` with your answers to create a new project. The project generates one or more documents based on the template configuration.

### How do I send a document for e-signature through Jentic?

Install the Jentic SDK with pip install jentic, then search for 'send document for electronic signature'. Jentic returns the Precisely signature-request operation. First add signees via POST `/organizations/{orgId}/documents/{docId}/signees`, then trigger the signing via POST `/organizations/{orgId}/documents/{docId}/signature-request.`

### Does the Precisely API support webhook notifications?

Yes. The API supports resthook-style webhook subscriptions for events like document status changes. Callbacks include a Precisely-Signature header for payload verification using HMAC-SHA256. Failed deliveries are retried 3 times, and subscriptions are disabled after 10 consecutive failures.

### Can I limit what my agent is allowed to do with the Precisely API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Precisely operations and credentials the agent may use. Since Precisely puts the organization and document ids in the URL path, such as `/organizations/{organizationId}/documents/{documentId}`, a rule can pin the agent to a single organization so it only reads and creates that organization's content. You also choose the specific operations it may call, so an action like sending a signature request via POST `/organizations/{organizationId}/documents/{documentId}/signature-request` is available only if you explicitly allow it.