Go to content

Your client wants booking built into their own website, or sales data in their own system. With the Johku Partner API you build it directly on Johku's products, availability, prices and orders, without writing booking logic or handling payments yourself. Using the API requires an affiliate agreement, so start by joining the Johku affiliate program.

Join the affiliate program Open the Partner API documentation

Examples of what you build with the Partner API

Products and availability in your own solution

You fetch the shop's products, categories, prices and free times in the shop's own languages and show them on your client's website exactly the way you want.

Booking in the interface you build, payment in Johku

You ask for a price, hold the places for 30 minutes and send the buyer to pay in the shop's own checkout. The order is created in the merchant's Johku and shows in the sales report under your integration's name. You never handle payments.

Orders and sales into other systems

You fetch changed orders, upcoming reservations and sales reports for your client's reporting or your own application.

Confirmed bookings when you sell yourself

If you sell the merchant's products in your own service and take the payment yourself, you create a confirmed booking directly in the merchant's Johku. The merchant grants this permission separately.

An API your coding AI assistant reads on its own

The Partner API is documented so that your coding AI assistant reads it as well as you do. Give your assistant one address and it finds the rest.

llms.txt as the starting point

At api.johku.com/llms.txt there is a compact index for AI assistants: what the API does, how to authenticate, and where to find the guide, the OpenAPI document and the reference.

Integration guide in Markdown

The guide is written for developers and coding assistants. It walks through the whole booking flow: booking options, booking lines, quote, cart and the link to the shop's checkout.

OpenAPI 3.1 document

More than 30 operations and more than 400 examples in one file. Every operation has its own identifier, so you generate a client library straight from the document.

Responses tell you what to send next

Booking options say, product by product, which fields a booking line needs. Your assistant does not guess. It reads it from the response.

Errors for machines, not only for people

Every error comes back in the same format (RFC 9457) and carries a stable code. Your code and your assistant branch on the code, not on the error text.

The key reports its own limits

With one call you see which partner, integration and key is in use, which permissions it has and what its rate limits are.

Prices and rules always come from Johku

The merchant maintains products, prices, availability and booking terms in Johku. The API tells you what can be booked right now and at what price, and you build your form on that. When the merchant changes a seasonal price or closes a day, the change shows in your implementation without you changing any code.

Built for the way developers work

  • Test key and sandbox shop. You try the whole booking flow in a sandbox shop with made-up products and orders before you connect to a single real shop.

  • Documentation where you run the calls. Every endpoint and schema is described, and with a test key you run the calls right in the browser.

  • A retry does not make two bookings. You send an Idempotency-Key header with POST calls, so a call that was cut off and sent again returns the same response.

  • Separate keys for server and browser. A publishable key works only from the origins you allow, and only for product, availability, cart and Atlas search calls. The secret key stays on your server.

The merchant decides what your integration can reach

No shop's data is available to you without the merchant's consent. A connection is made in one of two ways:

  • You send an access request. The merchant sees your integration's name and description, the permissions you ask for in plain language and your reason, and approves or denies the request.

  • You connect it yourself. When you build for a client and have a user account in their Johku, you connect the integration there yourself and choose which permissions to turn on. The connection is active at once.

The merchant can revoke the connection at any time. Reading customer data is a permission of its own, and each read of a single customer's data is written to the shop's log.

The merchant needs Johku Power or Johku Max for an integration to be connected to their shop.

See plans and prices

The storefront's look with Advanced CSS

Not everything needs an API. When your client sells on a Johku storefront, you write your own CSS on top of the theme and finish the site in your client's look. Advanced CSS is part of Johku Power and Johku Max.

Side note: this entire site is a Johku storefront. Everything done here is possible for you too.

If your client already has a website of their own, the easiest way to embed Johku's products, search and shopping cart there is with widgets. Widgets can be styled with CSS to match the site. Product information updates in them from Johku automatically.

As a developer you get the same benefits as other affiliates

Developers are members of the Johku affiliate program just like consultants and agencies. On top of the API key, you get all the benefits of the program.

Johku Max AI tools in your clients' Johku shops

As an affiliate you have the Johku Max AI capabilities (MCP tools) in all your clients' Johku shops. You build the shop's products and content with your own AI assistant.

20% referral fee

When your client orders Johku Power or Johku Max as an annual subscription and selects you as their affiliate, Johku pays you 20% of the first year's annual fee. The Partner API requires exactly these plans from the merchant. No fee is paid on renewals or on monthly subscriptions.

A review every quarter

Every quarter we go through with you what works and what we develop next.

Read the terms and limits of the affiliate program

How to get started

  1. A meeting and the affiliate agreement. You tell us what you are building and which APIs you need. We agree on the ground rules in the affiliate agreement.

  2. A partner account in your own Johku. Johku opens a partner account for your company and adds its first member as the owner. For this you need a Johku of your own. When the account is ready, the partner interface opens in your own Johku.

  3. Members, integrations and keys. The owner adds the other members of your team, developers and owners, and creates the integrations. Under each integration you manage its keys and permissions yourself.

  4. Sandbox shop. With a test key you build and test the whole implementation in the sandbox shop, without a single real shop.

  5. Pilot. When your implementation works in the sandbox shop, you ask Johku to start your pilot. Live keys work from then on, and you can connect to a limited number of shops, three by default.

  6. Verification. When the pilot shops have had real use, errors are rare and the merchants are happy, Johku verifies you. The shop cap is removed, your rate limits rise and merchants see Johku's verification badge on your integration.

Good to know

  • The API cannot be used without a valid affiliate agreement.

  • You need a Johku of your own. The partner account, its members, integrations and keys are managed there.

  • The Partner API reads and books. It does not change a shop's products, prices or settings.

  • Order and customer data belong to the merchant and their customers. You use them only for what you have agreed with the merchant.

  • If the merchant's Power or Max subscription ends, the connection to the shop is paused. It resumes with the same permissions when the subscription is active again.

  • Not every product can be booked through the API. For such a product, the API gives a link to the shop's own booking page.

  • There are no webhooks. You fetch order changes and the status of access requests from the API.

  • Each key has rate limits, and every response tells you how much of the limit is left.

  • Ready-made SDK libraries will be published soon. Until then, you use HTTP calls or a client library generated from the OpenAPI document.

  • Affiliates are not Johku resellers. The merchant's contract with Johku is always direct.

Start with the affiliate program

You book the meeting from Ilkka's or Sami's calendar on the affiliate program page. In the meantime, get to know the documentation.

Join the affiliate program Open the Partner API documentation