The Juro open API: unlock your dream workflow

With a contract workflow connected via API, anything is possible - so what, practically, might you look to achieve with the Juro open API?

One way to embed frictionless contract workflows in your company is to integrate your contracts solution with other key systems. 

Juro’s out-of-the-box integrations with common systems of record for commercial teams, like Salesforce, HubSpot, Greenhouse and Workday, offer deep functionality with minimal setup.

But for advanced use cases, customers can use our open API to knit together systems in custom implementations to create the dream workflows for their business. In this guide, we’ll look at some examples of what’s possible when you power contracts with Juro’s flexible, open API.

What is an API?

An API (application programming interface) is simply a way for different software platforms to communicate with each other. Developers can implement APIs in order to connect one system to another, or to several others, so that actions in one system can have an impact in another.

Does Juro have an API?

Of course! Juro offers an open API to customers that’s built for maximum flexibility. Find out more about the technical capabilities of Juro’s API by reading the API documentation here.

To discuss your API use case with a Juro specialist, hit the button below. Otherwise, keep reading to find out more.

What can customers do with the Juro API?

Juro’s API offers a wide range of status and event triggers, including drafting (using data entry from other systems to populate contracts), contract lifecycle events (pushing data around contract events like contract views and approvals to and from other systems), and signatures.

The following is a list of statuses currently supported by Juro's API:

• Draft - the status until you sign yourself or send to someone for signing
• Sent for approval - you have sent the contract and are waiting for it to be approved
• Approved - everyone has approved the contract
• Rejected - one of the approvers has rejected the contract
• Sent for signing - you have sent the contract and are waiting for it to be signed
• Signed by us - signed by a Juro user but not a counterparty
• Signed by them - signed by counterparty but not a Juro user
• Fully signed - everyone has signed the contract

You can construct your dream workflow using any of these statuses to trigger actions in other systems. 

A great way to understand the possibilities of Juro’s flexible platform is to look at some common use cases for our API.

1. Connect Juro to a system of record - or several

While Juro has a deep stack of native integrations, we don’t yet integrate with everything - just everything here, plus everything that connects with Zapier.

However, if you have available developer resource, and a dream contract workflow in mind, you can connect Juro to one or several systems via the API. For example, an end-to-end HR lifecycle used by one enterprise customer could look like this:

• A decision is made to offer a candidate a job
• The candidate record is updated in Lever
• This auto-creates an offer letter and employment contract in Juro
• Internal users have the chance to review this before it’s sent out
• The contract is sent via Juro to candidates for signature
• Once signed, it's stored and tracked in Juro’s secure contract repository
• PDF, and contract values (like salary), are pushed into Oracle Fusion ERP

This enables the customer to seamlessly take group employees from interview to onboarding. After the contract is signed, its data can be pushed into the ERP system of record to help with cost control, budgeting and forecasting.

Juro is the most connected and automated contract generation system I’ve ever encountered

- Luke Hextall, People ops, Gopuff | Case study

Similar use cases would be relevant for other types of commercial teams; for example, sales teams agreeing high volumes of contracts, and using the API to connect their CPQ solution to contracts, as well as their storage solution (for example, Sharepoint) for fully signed documents.

With a flexible API like Juro, returning contracts and their data to key systems can be automated, ensuring data integrity for contracts across your whole tech stack. This helps to increase speed and allow contract volumes to scale, without surrendering any control when it comes to risk.

2. Integrate Juro with your product

For some customers, contracting is an intrinsic part of their product offering. In this case, the goal isn’t to connect one system to another, but to offer contract generation, negotiation and signature within the platform you offer to your own customers, giving a seamless end-to-end experience.

Let’s look at two common examples of this API use case in Juro.

Marketplaces

Juro powers contracts for some of the world’s fastest-growing tech-enabled marketplaces - from food delivery platforms like Deliveroo, Gopuff, Takealot and Wolt, to sectors as diverse as used cars (Cazoo), short-term commercial property (Appear Here), and childcare agreements (Tiney).

An example workflow here, in the context of food delivery, could be:

• A new restaurant wants to join a delivery app
• They fill out a registration form within the app
• The fields in this form connect via API to a contract template in Juro
• The form submission drafts a watertight contract and sends for approval / signing
• The restaurant can sign within the app, which is passed back to Juro
• Fully signed contracts are stored securely in Juro

Juro customers use this workflow to power a range of providers who collect information through their website or product, and then automatically form binding contracts in the subsequent workflow.

We selected Juro for its simplicity, ease of integration and security - I would definitely recommend it

- Khalid Al Turki, Strategy & Ops, Tamara | Case study

Employer-of-Record (EOR) providers

The COVID-19 pandemic accelerated the rise of the ‘digital nomad’, with a step-change in attitudes to remote working. This in turn led to the rapid growth of digital ‘EOR’ providers like Remote, Deel, Velocity Global and Omnipresent who take the administrative hassle out of employing workers overseas.

Many of these EOR providers choose Juro to power the contracting that underlies their product. These platforms need to create not dozens, nor even hundreds, but thousands of employment contracts each month for their clients. 

Juro’s flexible API enables these innovative providers to create a seamless workflow that looks something like this:

• An EOR’s client decides to make an job offer
• This employment offer, or update, is actioned in the EOR product
• This triggers the generation of a contract from Juro, with fields populated from EOR data
• The candidate receives the watertight contract and can accept or negotiate
• Contract events are pushed back into the EOR platform
• Eventually both parties reach an agreement and sign

Juro’s API allows users to stay in the EOR platform, but data is always in sync and the underlying contract technology is secure, robust and legally compliant when it comes to eSignature standards.

These are a handful of the custom, frictionless workflows created by Juro customers. But the only limit to what’s possible is the imagination and the unique requirements of the business in question.

If agreeing contracts faster would help your business in 2023, hit the button below to talk through your dream contract workflow.