Johari Payment Request API

Appearance

Johari Payment Request APIRaise payment requests from your own system

Send a request in, get told every time its status changes. Nine endpoints, one signing rule.

Get Started
Full Example

Nine Endpoints

Four lookups to find the right IDs, one to raise a request, one to check its status, one to download its files, one to answer a return, one to add files. Nothing else to learn.

Signed Both Ways

Every call you make is signed with your secret, and every callback we send you is signed with the same secret. Nobody can fake either side.

Safe to Retry

Every request, response and upload carries an idempotency key. Send the same one twice and only one payment request is ever created, one answer given, one set of files added.

Live Status Updates

Give us a callback URL and we tell you the moment a request is approved, rejected, paid, returned or deleted. We keep retrying until you answer.

What this guide covers ​

Johari is the system construction companies use to raise, approve and pay payment requests. This API lets your system (an ERP, a procurement tool, a site app) raise those requests directly, instead of someone typing them into Johari by hand.

It covers nine endpoints:

  • Four GET lookups: companies, sites, cost codes and approvers
  • One POST to raise a payment request, with up to 5 files attached
  • One GET to check a request's current status
  • One GET to download a file on a request
  • One POST to answer a request the cashier returned to you
  • One POST to add files to a request

Plus the callbacks we send to your server when a request's status changes or it is deleted.

Every page has field tables, real example requests and responses, and a list of common mistakes.

What this guide does not cover ​

  • The Johari app itself. This guide is API only.
  • Approving, paying or editing requests. Those are done by people in Johari. Your system raises requests, follows their progress, answers returns made to it and adds files.
  • Purchase orders, requisitions, petty cash and the other Johari modules.

Start here ​

  1. Read Getting Started: what you need and how the whole thing fits together.
  2. Read Signing Requests: every call must be signed, and it is the one thing people get wrong.
  3. Copy the Full Example and change it to fit your system.

Need help? ​

For credentials, the test server, or help with your integration, contact your Johari administrator, or Labedan IT Solutions at support@labedan.solutions.

Using an AI assistant? ​

The whole guide is available as one plain-text file at /llms-full.txt on this site (and a short index at /llms.txt). Give that file to your AI assistant and it has everything it needs to build the integration.

A machine-readable OpenAPI 3.1 spec of the whole API is at /openapi.yaml, for generating clients or agent tools.