For brands that are not on the JK platform. Your platform pushes player and transaction data to us whenever it changes. We never call your platform and we never hold your API credentials. Hand this section to your IT team.

1. 1

   Endpoint and token. We issue a brand id and a push token for each website. Send the token in the header, never in the URL.

   POST https://api.layan-ai.com/ingest/v1/<brand-id>
   Authorization: Bearer <push-token>
   Content-Type: application/json

   If a token is ever exposed, tell us and we issue a replacement. Old and new both work during a short changeover.

2. 2

   Request format. Every request has the same shape: a type and a data array of up to 500 records. Re-sending a record is safe: we match on its id and update instead of duplicating.

   { "type": "transactions", "data": [ { ... }, { ... } ] }

3. 3

   Feed users – player records with current balance. Answers "what is my balance?".

   Field	Type		Notes
   userId	string	required	Your unique player id. Must match the id used in transactions and on your website (step 8).
   balance	number	required	Current main wallet balance, e.g. 125.50
   currency	string	required	MYR
   username	string	optional	Login name, helps agents find the player
   name	string	optional	Display name
   phone	string	optional	Contact number
   vip	string	optional	VIP level or tag
   registeredAt	string	optional	ISO 8601 UTC
   updatedAt	string	required	ISO 8601 UTC, e.g. 2026-09-11T03:20:00Z

   { "type": "users", "data": [ {
     "userId": "884213", "balance": 125.50, "currency": "MYR",
     "username": "ali88", "name": "Ali bin Ahmad", "phone": "60123456789",
     "vip": "Gold", "updatedAt": "2026-09-11T03:20:00Z" } ] }

4. 4

   Feed transactions – deposits, withdrawals and bonuses. This is the most important feed: most questions are about money that has not arrived yet.

   Field	Type		Notes
   txnId	string	required	Unique transaction id, used to avoid duplicates
   userId	string	required	Must match the id in users
   type	string	required	deposit · withdrawal · bonus · rebate · adjustment
   amount	number	required	e.g. 50.00
   currency	string	required	MYR
   method	string	optional	Payment method or gateway name as the player sees it
   status	string	required	pending · completed · rejected · cancelled
   remark	string	required if rejected	Why it was rejected, in the words you want the player to read
   createdAt	string	required	ISO 8601 UTC
   completedAt	string	optional	When it settled or was rejected

   { "type": "transactions", "data": [ {
     "txnId": "TXN-99231", "userId": "884213", "type": "withdrawal",
     "amount": 300.00, "currency": "MYR", "method": "DuitNow",
     "status": "rejected",
     "remark": "Bank account name does not match. Please resubmit.",
     "createdAt": "2026-09-11T02:55:00Z", "completedAt": "2026-09-11T03:10:00Z" } ] }

   Why remark matters When a withdrawal is rejected we tell the player immediately, quoting your remark as the reason. A clear remark prevents an angry message to your support team. Never put a bank account number in it.
5. 5

   Optional feeds. Not required to launch. Send them if you want the assistant to answer these questions too.

   type	Enables	Key fields
   registrations	Welcoming new players, first-deposit prompts	userId, registeredAt, referrerId
   downline	"How many people did I refer?"	userId, downlineUserId, level, joinedAt
   dailyBetTotal	"How much have I wagered?", turnover progress	userId, date, totalBet, totalWin
   promotions	Current bonus list without manual updates	promoId, title, type, amount, turnover, validFrom, validTo

6. 6

   How often to push. The assistant is only as current as your most recent push.

   Feed	Recommended	Minimum acceptable
   transactions	Immediately on every status change	Every 60 seconds
   users	On balance change, or every 1–2 min	Every 5 minutes
   registrations	On signup	Hourly
   downline, dailyBetTotal, promotions	Hourly	Daily

   This one decision decides whether players trust the assistant The most common question is "my deposit hasn't arrived". If transactions are pushed every 5 minutes, a player who deposited 30 seconds ago is told there is no deposit, and contacts your support team anyway. Push each transaction the moment its status changes.
7. 7

   Responses and retries. Keep a queue and remove a record only after a 200.

   Code	Meaning	What to do
   200	Accepted, body shows how many records were stored	Nothing
   400	Malformed JSON or a missing required field	Fix and resend, do not retry unchanged
   401	Token missing, wrong or revoked	Contact us
   429	Too many requests	Wait, then retry
   5xx	Our problem	Retry with backoff (1s, 5s, 30s)

   HTTP/1.1 200 OK
   { "ok": true, "type": "transactions", "accepted": 2, "rejected": 0 }

8. 8

   Your website must tell us who is chatting. We send one line of code for your site (Step 3, item 6). Before it, your page template sets the logged-in player's id, the same userId you push. Leave it empty when nobody is logged in.

   <script>window.LayanAI = { userId: "884213" };</script>  /* value from your server-side template */

9. 9

   What we do not want. Passwords or hashes, full bank account or card numbers, identity documents or KYC images, players who never used your website. If a field is not on this page, we do not want it.