Install Jentic One Beta

Connect the fynk API Reference to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the fynk API Reference, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffynk.com%2Ffynk" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffynk.com%2Ffynk" | 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 fynk API Reference API.

Create a contract document from an uploaded PDF via /documents/create-from-pdf

Generate a contract from a fynk template through /documents/create-from-template

Move a document to the review stage with /documents/{document}/stage-transitions/review

Send a document to signing via /documents/{document}/stage-transitions/signing

GET STARTED

Start building with fynk API Reference API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use fynk API Reference API for, with concrete tasks.

★ Automated Contract Drafting from CRM

Auto-generate sales contracts from a CRM deal record by calling /documents/create-from-template with the matching template ID and merging fields, then moving the document to /stage-transitions/review for legal sign-off. The flow eliminates manual copy-paste from CRM into a Word file.

Call /documents/create-from-template with template_id and the deal's merge fields, then POST /documents/{document}/stage-transitions/review.

PDF Contract Ingestion

Bring legacy PDF contracts into fynk's lifecycle by calling /documents/create-from-pdf with the uploaded file, then routing the new document through review and signing stages. This lets teams centralise external contracts under one tracked workflow.

Upload a PDF via /documents/create-from-pdf and capture the returned document ID.

Signed Contract Archival

Pull the latest signed revision of every closed contract by polling /documents/{document}/revisions/latest/pdf/download and storing the binary in long-term storage for audit. The endpoint returns the PDF so it can be archived without screen-scraping the fynk UI.

Call GET /documents/{document}/revisions/latest/pdf/download for each closed document_id and store the response.

Stage-Transition Automation

Drive the review-to-signing handoff automatically when an approver leaves a comment in another tool by calling /documents/{document}/stage-transitions/signing. This removes the manual button-click that often blocks deal closure.

Call POST /documents/{document}/stage-transitions/signing for the document approved in the review channel.

Agent-Driven Contract Operations via Jentic

A legal-ops agent receives a request such as 'send the NDA we just drafted out for signing' and uses Jentic to find /documents/{document}/stage-transitions/signing, load its parameters, and execute against the workspace's bearer token. Jentic isolates the token so the agent never holds it directly.

Search Jentic for 'send fynk contract to signing', load /documents/{document}/stage-transitions/signing, and execute it with the document_id.

Key Endpoints

43 endpoints — the fynk api gives programmatic access to fynk's contract lifecycle management platform, covering document creation from pdfs or templates, template management, revision retrieval, signing-stage transitions, and account-level operations.

METHOD

PATH

DESCRIPTION

POST

/documents/create-from-pdf

Create a contract from an uploaded PDF

POST

/documents/create-from-template

Create a contract from a fynk template

GET

/documents

List contracts in the workspace

GET

/templates

List available contract templates

GET

/documents/{document}/revisions/latest/pdf

Get the latest revision PDF metadata

POST

/documents/{document}/stage-transitions/review

Move a document to the review stage

POST

/documents/{document}/stage-transitions/signing

Send a document to signing

POST

/documents/create-from-pdf

Create a contract from an uploaded PDF

POST

/documents/create-from-template

Create a contract from a fynk template

GET

/documents

List contracts in the workspace

GET

/templates

List available contract templates

GET

/documents/{document}/revisions/latest/pdf

Get the latest revision PDF metadata

POST

/documents/{document}/stage-transitions/review

Move a document to the review stage

POST

/documents/{document}/stage-transitions/signing

Send a document to signing

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the fynk API by hand means setting up its HTTP bearer auth against app.fynk.com and threading the token through document creation, template, and stage-transition calls yourself. Through Jentic you install once, import the fynk API from the API Directory, store the token once, and your agent calls it.

Permission scoping

fynk puts the document id in the URL path (/documents/{document}/stage-transitions/review), so a rule can pin your agent to one document: it can advance that document through review and signing and nothing else. You choose the operations it may call, so creating documents from a PDF or template is not included unless you add it.

Credential isolation

Your fynk bearer token 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a contract from a template' or 'move a document into signing', and Jentic returns the matching fynk operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using fynk API Reference API through Jentic.

What authentication does the fynk API use?

fynk uses an HTTP bearer scheme defined as 'http' in the spec's securitySchemes; you pass an Authorization header with the workspace token on every request. Jentic stores that token encrypted and attaches it at execution so the agent context never sees it.

Can I create a contract from a template with the fynk API?

Yes. POST /documents/create-from-template with the target template_id and any required merge fields and fynk returns a new document object that you can immediately move through review and signing stages.

What are the rate limits for the fynk API?

The OpenAPI spec does not declare numeric limits for the /documents and /templates endpoints. Watch for HTTP 429 responses, fall back to exponential backoff, and contact fynk support for written quotas if your workload requires guarantees.

How do I send a contract to signing through Jentic?

Run a Jentic search for 'send fynk contract to signing', load POST /documents/{document}/stage-transitions/signing, and execute it with the document_id. Get started with Jentic One, the self-hosted execution layer.

Can I download the latest signed PDF of a contract?

Yes. GET /documents/{document}/revisions/latest/pdf/download returns the PDF binary for the most recent revision, making it suitable for downstream archival or audit storage.

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

Yes. Because you run Jentic One yourself, your own rules decide which fynk operations and which bearer token the agent may use. Since fynk puts the document id in the URL path (/documents/{document}/stage-transitions/review and /stage-transitions/signing), you can pin the agent to a single document and let it advance only that one through review and signing. You choose the operations it may call, so creating documents from a PDF or template stays off unless you explicitly add it.

fynk API Reference

Name: fynk API Reference API
Brand: fynk API Reference
Availability: InStock

Official vendor OpenAPI document · agent-readyProductivityCollaborationhttp43 EndpointsREST

For Agents

Automate contract lifecycle workflows in fynk including creating documents from PDFs or templates, transitioning them to review or signing, and retrieving the latest revision PDF.

Use for: I need to create a contract from a template in fynk, Upload a PDF and convert it into a fynk contract, Send a contract to signing once it is approved, Retrieve the latest signed PDF for a contract

Not supported: Does not handle e-signature legal certification authority, payment processing, or CRM record management - use for fynk contract drafting and lifecycle stage transitions only.

The fynk API gives programmatic access to fynk's contract lifecycle management platform, covering document creation from PDFs or templates, template management, revision retrieval, signing-stage transitions, and account-level operations. The 43 operations are organised into General, Document Operations, Template Operations, File Upload Helpers, Account, and Auth groups, returning JSON contract metadata and revision payloads. Authentication uses HTTP bearer tokens issued by fynk for the workspace. The API is intended for legal-ops, sales, and procurement teams that need to automate contract drafting, routing, signing, and archival from CRM, HRIS, or custom internal tools.

Jentic One on Github View OpenAPI Document

Connect the fynk API Reference to your agent

Capabilities

Start building with fynk API Reference API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

fynk API Reference