A contract management API that sends for signature in one call.
Your CRM, portal or billing system already has the deal data. The fynk REST API turns it into a finished contract on your approved template and puts it in front of the signers. Nobody opens a Word file. Nobody presses send.
Every endpoint, documented.
The reference is generated from the live API, with request fields and examples for every call.
A contract API for the systems that already know the deal.
Retyping deal details into a contract template is a job for nobody. Let the software that already knows the customer do the drafting, and keep people for the decisions.
"It makes us compliant but it also makes us more efficient, because the automated workflow brings us not only time savings but also security that we have been doing everything correctly."

Contract management APILearn moreCreate, fill and send a contract with one API call.
A deal closes in your CRM or ERP and the contract already exists, on the right template, with prices, dates, the counterparty and the signers filled in. A singlecreate-from-templaterequest does all of it. Setinitial_stagetosigningand the signers get it right away."Our sales team also creates offers directly in fynk via the Pipedrive integration, using data from our CRM."
Mark Legal Counsel at Nordwert
E-signature APILearn moreAn e-signature API with SES, AES and QES under eIDAS.
Your system picks who signs and in which order, then hands the contract over. The signature level comes from your template, so legal decides it once and every contract follows. Only when a template leaves it open does your integration passsignature_typeitself, up to a qualified signature."We had a digital signing process, but there was a lot of media disruption between Word and PDFs. We were using Adobe Sign and doing a lot of manual processes too."
Elisa Prößdorf Legal Solutions Manager at Unite
Signature APILearn moreSigning links inside your own portal or app.
Customers and partners never need a fynk login. Thepersonal-linkendpoint returns a signing URL for each signer, ready for your portal, email or app. One click takes them to the contract, where fynk verifies who they are and collects the signature.
Self-service contractsLearn moreA web form on your site, a signed NDA through the API.
Every NDA request that lands in someone’s inbox is a small tax on their week. Pass the form answers to the API and the agreement is drafted and sent before anyone on your team has seen the request.
Use cases
Step by step, from trigger to signed contract.
Follow real automations, field by field.
Template APILearn moreApproved contract templates, used inside your product.
Build a platform on top of approved contract templates without hardcoding a single clause. Your app reads the template list and creates documents from it. When legal changes a clause in fynk, every new contract picks it up, with no deploy on your side."By having predefined templates for contracts and only changing dynamic fields, we can be sure that those contracts comply with our own standards."
Clemens Gaugusch Managing Director at CoastCap
Document automation APILearn moreImport PDF contracts by API, with AI reading the data.
A folder of dead PDFs on a file server is not an archive. Send signed or third-party contracts tocreate-from-pdfand each one becomes a real fynk document. AI reads the dates, parties and values on the way in.
Signed PDFsLearn moreDownload signed contracts to your DMS automatically.
Downloading a signed contract and filing it by hand is how contracts go missing. Your integration fetches the final revision as soon as it’s signed and stores it in your DMS, claims platform or cloud storage. One copy of record, always in the right place.
Contract data APILearn moreContract data in your BI tool and data warehouse.
Contract data locked in one tool is data nobody looks at. Sync contracts, parties, fields and metadata into your data warehouse, then report in Power BI, Looker or Tableau. Join it with CRM deals and you finally see which contracts carry the revenue."Designing our key metrics and extracting them and making them visible really fast is what we really like about fynk."
Lucas F. Jamnig Lead Counsel, fiskaly
Data syncLearn moreUpdate contract fields when your source system changes.
Two systems with two different contract values is a reporting problem waiting to happen. One bulkPUTupdates dynamic fields or metadata values whenever the price, term or owner changes upstream. fynk stays the place where the contract and its numbers agree.
Workflow automationLearn moreMove contracts from draft to archive by API.
Your integration moves each contract through review, signing and done, then archives it when the job is finished. The signing setup from your template still applies. The process runs the same way every time, whoever triggered it."Until now, we had been 'tracking' our contracts using Excel. Now, every follow-up happens automatically, saving us both time and money."
Christoph Director of Corporate Development at RAMPF Group
Webhooks + APILearn moreWebhooks for the event, the API for the details.
Asking the API “is it signed yet?” every minute is a polling loop nobody wants to maintain. A webhook postsdocument.signed_by_all_partiesto your endpoint, signed to the Standard Webhooks spec. Then one API call fetches exactly the details you need.
An API built for the developers who maintain it.
The boring parts done right, so your integration still works next year.
One call, not five.
Create, fill, address and send in a single request. Fewer moving parts to break.
Versions stay put.
Your account is pinned to one API version with a changelog. You upgrade when you choose, never by surprise.
Survives staff turnover.
Tokens belong to the integration, not a person. Someone leaves, nothing stops.
Only the access needed.
Read-only for reporting, document manager for drafting. Add an expiry date and revoke anytime.
QES by API.
SES, AES or QES, whatever the contract needs, all eIDAS-compliant.
Your data, portable.
Fields, metadata, parties, comments, stored files and signed PDFs, all readable by API.
Limits you can see.
200 requests a minute per token. Every response tells your integration how many are left.
Any language works.
Plain REST and JSON. If it can send an HTTP request, it can talk to fynk.
No developers? Fine.
The same actions run through Zapier or an AI assistant over MCP.
No code to write? Start here instead.
Native connectors and no-code tools that use the same contract engine.
Make your first fynk API call in minutes
All you need is a fynk account on the Business or Pro plan
- Step 1
As the account owner, open Account settings > API integrations > fynk API, create a token and give it a role.
- Step 2
Send it as a Bearer token in the Authorization header. Add the
fynk-Api-Versionheader to pin your version. - Step 3
Call Create document from template with your field values, parties and signers. Find every endpoint in the API docs.
Frequently asked questions.
The fynk API is a REST API for contract management and e-signature. Your own software can create contracts from templates, send them for signature, read contract data and download signed PDFs. It runs on the same platform your team uses in the browser.
Yes. API is the general term for any interface between two programs, and REST is the style fynk's API follows: standard HTTPS requests with JSON. So 'fynk API' and 'fynk REST API' mean the same thing.
Yes. The create-from-template endpoint takes dynamic field values, parties and signatories in the same request. With signing as the initial stage, it's out for signature the moment it exists.
The same levels as fynk itself: SES, AES and QES under eIDAS. The level is set on the template. If a template has none, the API can set it per contract, otherwise your account default applies.
A webhook pushes a message to your system when something happens, for example the moment the last signer finishes. The API is what your system calls to read or change data. Use webhooks to know when, and the API to fetch the details.
With an API token sent as a Bearer token. Account owners create tokens in the account settings, give each one a role such as document reader or document manager, and can set an expiry date or revoke it anytime. The REST API guide in our help center walks through it.
API access is part of the Business and Pro plans. Account owners create the tokens. See the plans on the pricing page.
There's no separate sandbox and no official SDK yet. You can test in a separate fynk workspace, and every endpoint comes with example requests in the reference.
Use the API when your developers build a lasting integration. Use Zapier to connect apps without code, and the MCP server when an AI assistant like Claude or ChatGPT should do the work.
Still have questions?
Teams that stopped copying contract data by hand.
What the fynk REST API covers
The fynk REST API uses HTTPS and JSON, with Bearer token authentication. The base URL is https://app.fynk.com/v1/api. Most of what your team does in fynk by hand, an integration can do through it.
Create and send
| What you can do | |
|---|---|
| Create | Create a document from a template, or from an uploaded PDF. |
| Fill | Set dynamic field values, parties and signatories while creating. |
| Send | Start the document in signing, or move it to review, signing or done later. |
| Signers | Add or update signatories, set the signing order, create personal signing links. |
| Share | Create a public link, add document users, link related documents. |
Example: a single request to the create endpoint with initial_stage: signing builds the contract, fills it, adds the signers and starts the signature run.
Read and sync
| What you can do | |
|---|---|
| Find | List and filter documents, templates, document types, teams and tags. |
| Read | Fetch dynamic fields, metadata values, parties, signatories and comments. |
| Update | Bulk-update dynamic fields and metadata values, archive or unarchive documents. |
| Download | Get the latest PDF revision and any files stored on the document. |
Stay stable
| Versioning | Each account uses one fixed API version. Override it per request with the fynk-Api-Version header. |
| Tokens | Scoped roles, optional expiry, revocable, owned by the account and not a person. |
| Rate limit | 200 requests per minute per token. Use webhooks instead of polling to stay well under it. |
The full endpoint reference, data models and example requests are in the fynk API documentation.

Your integration inherits every guarantee.
European by design.
Designed and developed in Austria. fynk is hosted in the EU, in ISO 27001-certified data centers.
Security at the core
Encryption in transit and at rest, and secure engineering standards across a continuously monitored infrastructure.

Tokens on your terms
Tokens are stored hashed and shown once. Only account owners can create, edit or revoke them.
GDPR, fully embedded
Fully compliant with European data protection regulations, supported by regular audits and external penetration testing.

Trusted by companies worldwide
Take control of your agreements. Move your business forward.
Run agreements the way they should run: fast, clear, and on your terms.
No setup headaches
Go live in days, not quarters
No lock-in
Full export anytime
No hidden fees
Signatures included, no envelope fee


























