Put verified traceability on your own website or system
Two ways to use your supply-chain data, and both can be used at the same time.
1. Public data, no key needed
Show a verified traceability card for any container number or bag code on any website. It carries only public information: no supplier or customer names, no raw-material types, no seal, vessel or order numbers.
Embed widget
<div data-cirva-trace="MRKU4908561" data-theme="light"></div> <script src="https://sals.co.id/embed/trace.js" async></script>
Public JSON
GET https://sals.co.id/api/v1/trace?q=MRKU4908561
q accepts a container number, a bag code, or a verification code (CT-… / PU-…). Limited to 120 requests per minute per address.
2. Your own orders, privately
Read the full record of your orders, including shipment details, straight into your ERP or reporting system, and show it only to your own team. Use a token from your server; never put a token in a web page.
curl -H "Authorization: Bearer ctk_your_token" \ "https://sals.co.id/api/v1/me/orders" curl -H "Authorization: Bearer ctk_your_token" \ "https://sals.co.id/api/v1/trace?q=YOUR-ORDER-NUMBER"
Orders that are not yours return 404, the same as a number that does not exist. Tokens are read-only and can be revoked at any time.
Signed responses
Every response carries an X-Trace-Signature header: an ECDSA (P-256, SHA-256) signature over the exact response body. Verify it with the public key from /api/v1/trace/key. A record that passes the check has not been altered after it left our system. The payload follows Digital Product Passport and GS1 EPCIS concepts (an alignment, not a certified conformance claim).
Current key id: f8a5b1199e435299
Your API tokens
Sign in with your customer account to create tokens.
Customer sign-in