Customs Bridge

Getting started

Every event you send follows the same envelope regardless of type: a event_type, a unique external_ref you generate, and type-specific fields. Here's a goods-in event end to end.

curl -X POST https://openapi.oneerp.app/api/erp-adaptor/v1/events \
  -H "X-Api-Username: your-username" \
  -H "X-Api-Password: your-password" \
  -H "Content-Type: application/json" \
  -d '{
    "event_type": "goods_in",
    "external_ref": "PO-2026-00481",
    "date": "2026-09-08 09:30:00",
    "partner_name": "PT Sumber Makmur",
    "djbc_doc": {
      "no_dok": "000123/BC2.3/2026",
      "tgl_dok": "2026-09-08",
      "jenis_dok_code": "BC 2.3"
    },
    "lines": [
      { "sku": "RM-STEEL-08", "qty": 500, "unit_price": 42000 }
    ]
  }'

Authentication

We issue you a username and password — send them as headers on every request. An API key is optional and only enforced if we've set one for your account.

Idempotency & retries

external_ref is your own reference — a PO number, a stock transfer ID, anything unique in your system. We reject a second event with a reference we've already seen, so it's safe to retry a network timeout with the exact same payload.

Send an event

Reports one stock movement, production event, or periodic count. See the Event Types section below for the fields each event_type expects inside this same envelope.

{
  "externalRef": "PO-2026-00481",
  "state": "processed",
  "eventId": 4821
}

{
  "externalRef": "PO-2026-00481",
  "state": "error",
  "eventId": 4822,
  "errorMessage": "SKU 'RM-STEEL-99' tidak ditemukan..."
}

Check event status

Poll this once you have an external_ref. Since submission to INSW is staged for manual review, inswQueueState moves from draft to sent only after our team confirms it — this is how you'll know it actually reached customs, not just that we received it.

{
  "externalRef": "PO-2026-00481",
  "eventType": "goods_in",
  "state": "processed",
  "errorMessage": null,
  "inswQueueState": "draft"
}

Event types

Nine shapes cover everything a bonded facility needs to report. Each is sent to the same POST /api/erp-adaptor/v1/events endpoint above, distinguished by event_type.

goods_in — import receiving

Goods arriving into the bonded facility from an external supplier. Requires a linked customs document.

{
  "event_type": "goods_in",
  "external_ref": "PO-2026-00481",
  "partner_name": "PT Sumber Makmur",
  "djbc_doc": {
    "no_dok": "000123/BC2.3/2026",
    "tgl_dok": "2026-09-08",
    "jenis_dok_code": "BC 2.3",
    "no_aju": "0812026..."
  },
  "lines": [
    { "sku": "RM-STEEL-08", "qty": 500, "unit_price": 42000 }
  ]
}

goods_out — release / export

Goods leaving the facility. Same shape as goods_in, reversed direction.

{
  "event_type": "goods_out",
  "external_ref": "SO-2026-01102",
  "partner_name": "PT Kirim Jaya",
  "djbc_doc": {
    "no_dok": "000456/BC3.0/2026",
    "tgl_dok": "2026-09-08",
    "jenis_dok_code": "BC 3.0"
  },
  "lines": [
    { "sku": "FG-PANEL-12", "qty": 120 }
  ]
}

internal_transfer — mutasi

Movement between your own internal locations. No customs document needed.

{
  "event_type": "internal_transfer",
  "external_ref": "MUT-2026-0093",
  "direction": "in",
  "lines": [
    { "sku": "RM-STEEL-08", "qty": 50 }
  ]
}

production_in — finished goods output

Finished goods coming out of your production line into stock. Reported without needing a manufacturing module on our side.

{
  "event_type": "production_in",
  "external_ref": "WO-2026-2210-OUT",
  "lines": [
    { "sku": "FG-PANEL-12", "qty": 300 }
  ]
}

production_out — raw material consumption

Raw materials leaving stock to be consumed in production. The mirror of production_in.

{
  "event_type": "production_out",
  "external_ref": "WO-2026-2210-IN",
  "lines": [
    { "sku": "RM-STEEL-08", "qty": 480 }
  ]
}

opening_balance — go-live stock

One-time (or per-period) declaration of stock on hand, filed to INSW as saldo awal.

{
  "event_type": "opening_balance",
  "external_ref": "OB-2026-Q3",
  "lines": [
    { "sku": "RM-STEEL-08", "qty": 1200, "unit_cost": 41500 }
  ]
}

opname — stock opname

Physical count results for a periodic stock opname.

{
  "event_type": "opname",
  "external_ref": "OPN-2026-09",
  "lines": [
    { "sku": "FG-PANEL-12", "counted_qty": 118 }
  ]
}

adjustment — stock correction

A one-off correction outside a formal opname — damage, shrinkage, or a data-entry fix.

{
  "event_type": "adjustment",
  "external_ref": "ADJ-2026-0044",
  "reason": "Water damage, pallet 12",
  "lines": [
    { "sku": "RM-STEEL-08", "counted_qty": 470 }
  ]
}

product_sync — product master data

Upserts products by your own SKU. Send this before reporting any movement for a new item — every other event type looks products up by sku and rejects unknown ones.

{
  "event_type": "product_sync",
  "external_ref": "SYNC-2026-09-08-001",
  "products": [
    {
      "sku": "RM-STEEL-08",
      "name": "Steel Coil 0.8mm",
      "category_name": "Bahan Baku",
      "insw_commodity_code": "1",
      "insw_uom_code": "KGM"
    }
  ]
}

Status codes

Every response is JSON, on every status code — there's no separate error format to special-case.