Connect your systems to Shipment 360.

Start here

The address is https://api.keeplee.com. Every call is over HTTPS, and sends and receives JSON. A key belongs to one company, so the key says whose data a call is about.

1. Make a key for the one thing you want to do. Each company makes its own.
2. Copy it right away. We show it only once.
3. Send your first call, like the one above.

Keys

Make keys for CRM on its Channels page. Make keys for Books in Books, Settings, API keys. We store only a SHA-256 of a key, so we cannot show it to you again. If you lose a key, revoke it and make another. Revoking stops a key at once. A key does one action.

Answers and limits

A good answer is {"data":…}. A refusal is {"error":{…}} with a code, a message and, where it helps, a message for each field. An unexpected failure is a 500 with a reference. Send it to us, and we can find the failure.

HTTP 422
{"error":{
  "code": "validation_failed",
  "message": "Please check the fields.",
  "fields": { "name": "…" }
}}

Limits are per minute. A public key allows 10 per visitor and 120 in all. A webhook key allows 600. After 30 bad keys from one visitor, we refuse that visitor. The X-RateLimit-* headers report the nearest limit, and a refusal carries Retry-After.

CRM: website leads

Make a website key and list the websites allowed to use it. The key is public, because it must be in the page's script. It can only add a lead, and only from those websites.

POST /v1/crm/leads

• Required: name, and either email or phone.
• Kept in their own fields: company, city, message, form (or source) and page.
• Anything else: up to 20 more fields, such as industry, are kept with the lead.

<form id="contact">
  <input name="name" required>
  <input name="email" type="email">
  <input name="phone">
  <textarea name="message"></textarea>
  <!-- Hidden from people. A robot fills it, and nothing is kept. -->
  <input name="website" tabindex="-1" autocomplete="off" style="position:absolute;left:-9999px">
  <button>Send</button>
</form>
<script>
document.getElementById('contact').addEventListener('submit', function (e) {
  e.preventDefault();
  var data = Object.fromEntries(new FormData(this));
  data.form = 'contact';
  data.page = location.href;
  fetch('https://api.keeplee.com/v1/crm/leads', {
    method: 'POST',
    headers: {'Content-Type': 'application/json', 'Authorization': 'Bearer kos_pub_…'},
    body: JSON.stringify(data)
  });
});
</script>

No script? Post an ordinary form with hidden key and redirect fields. The visitor returns to redirect with received=1 or error=1, if that address is on an allowed website.

CRM: channels

Messages arrive at one address, /v1/hooks/{key}. A message from someone with an open lead joins that lead. Otherwise, WhatsApp and SMS make a new lead on their own. Email and comments wait in the CRM's Inbox for a person to handle. You can change this for each channel. A message seen before does nothing, so a service can safely send it twice. For each channel, make a key of the right kind on the Channels page.

Books API

Use a secret key, read only or read and write, sent as Authorization: Bearer. Dates are YYYY-MM-DD. A company with more than one set of books names it with book=ID. Lists give up to 200 at a time with per_page.

A write follows the same rules as the screen: the locks, the numbering, the approvals and the audit trail. The API can read and add. It does not change or delete.

Sending it twice is safe. Add an Idempotency-Key to a write. We keep the first answer for 24 hours. A retry gets that answer, not a second invoice.

curl -X POST https://api.keeplee.com/v1/books/invoices \
  -H "Authorization: Bearer kos_live_…" \
  -H "Idempotency-Key: my-system-invoice-1042" \
  -H "Content-Type: application/json" \
  -d '{"direction":"sales","contact_id":12,"invoice_date":"2026-11-06","issue":true,
       "lines":[{"charge_head_id":3,"description":"Ocean freight",
                 "quantity":2,"unit":"CTR","rate":45000}]}'

Not here yet

So you can plan, here is what the API does not do today. There are no sign-in tokens for acting as a user. It does not send webhooks out to your system. And Job Board, HR & Payroll, Inventory, Asset Management and BI Dashboard have no API. If you need one of these, tell us.