Prodaksha Developers

Other integrations

Besides supplier and society systems, these are the common ways to connect.

Accounting and payment systems

Read what the factory owes and paid its suppliers and societies:

curl -s -H "Authorization: Bearer $TOKEN" "$BASE/invoices?status=issued"
curl -s -H "Authorization: Bearer $TOKEN" "$BASE/payments?supplier_ref=39"
  • Invoices list lines with deductions, total, paid, outstanding and due_date. Drafts are never shown.
  • Payments list payment_no, invoice_no, amount, currency, rail (mpesa, bank, cash…), txn_ref and paid_at.
  • For the factory's whole books, subscribe to journal.posted, sales_invoice.posted, credit_note.posted and receipt.recorded. The factory can also export to Xero, QuickBooks Online and Sage 50 from its own screens.

Buyers, exporters and traceability

  • GET /lots/{lot_no}/trace answers one step back (the deliveries or runs a lot came from) and one step forward (the runs and deliveries it went to). Call it again on each lot to walk the whole tree.
  • Every printed label carries a QR code to a public page for the lot (https://prodaksha.com/l/{code}), with no login.
  • Subscribe to delivery.posted and sales_invoice.posted to know what was shipped and billed to a buyer, and einvoice.signed for the tax authority's control number (eTIMS in Kenya).

Sensors and devices

Cold-store probes post a reading; a token with only write:readings is enough:

curl -s -X POST $BASE/temperature-readings \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" -H "Idempotency-Key: $(uuidgen)" \
  -d '{"location": "COLD1", "reading": 3.4, "recorded_at": "2026-11-15T08:00:00+03:00"}'

The answer says whether the reading was within the store's band. Outside it, the chilled and frozen lots in that store are put on hold, and you receive lot.hold_changed.

Weighbridges and label printers connect to the factory's own screens or its offline factory box, not to this API.

Dashboards and reports

  • GET /company for the factory's name, country, currency, time zone and modules.
  • GET /items and GET /price-lists?scope=purchase (or sales) for the catalogue and prices by grade and period.
  • GET /intakes for deliveries received, and GET /work-orders/{id}/outputs for a run's results.
  • To stay in step without polling, subscribe to the events you chart (intake.posted, run.completed, delivery.posted…).

Something is missing?

The API grows with what partners need. If your integration needs data that is not here, tell the factory you work with, so it can ask the Prodaksha team. New fields and endpoints are added to version 1 without breaking what you built.