Multipass Wallet Guide

Each pass in the transaction is a fully independent wallet pass: its own barcode, its own personalised fields, its own update/push lifecycle. The single link is a lightweight group that presents them together.

1. Order is paid on your platform; your fulfilment webhook fires.
2. Your handler calls POST /sendTemplatedEvent with a multipass array — one item per pass, each carrying its own tag_data (code, PIN, expiry, store, …).
3. Every item mints a wallet pass from its pass template, personalised with that item’s data. Validation is all-or-nothing: if any item is invalid, nothing is minted and the send is rejected.
4. One message goes out via your saved trigger (SMS or MMS, chosen by event_type). The trigger’s message body must contain the <Add2WalletLink> tag — that is where the single group link is substituted.
5. The customer taps the link, sees every pass, and adds them individually or all at once.

/sendTemplatedEvent is available on the Basic surface (HTTP Basic auth with your per-merchant credentials) and the Webhook surface (x-api-key header). Use whichever your account was provisioned with — the request body is identical.

Base URL (Basic auth)

https://www.apimobiledigital.com/basic  — interactive reference
POST https://i7p1tu3ftd.execute-api.ap-southeast-2.amazonaws.com/prod/sendTemplatedEvent

A complete example — two passes from one transaction, delivered as one SMS:

POST /sendTemplatedEvent
Content-Type: application/json

{
  "event_name": "order_pass_issue",
  "event_type": "SMS",
  "destination": "61400000000",
  "tracking_id": "order-84213",
  "firstname": "Alex",
  "surname": "Smith",
  "multipass": [
    {
      "pass_config_id": "00117",
      "tag_data": {
        "code": "GC1111222233",
        "pin": "1234",
        "expiry": "31/12/26",
        "storename": "George Street Store",
        "amount": "$24.50"
      }
    },
    {
      "pass_config_id": "00117",
      "tag_data": {
        "code": "GC4444555566",
        "pin": "5678",
        "expiry": "31/12/26",
        "storename": "George Street Store",
        "amount": "$24.50"
      }
    }
  ]
}

Top level

Each multipass[] item

Success

{
  "result": true,
  "message": { "status": 1, "message": "SMS has been scheduled", "cost": 1 },
  "status": 1,
  "transId": "order-84213"
}

Error semantics — the guarantees your integration can rely on

• All-or-nothing validation. Every item’s template and data are checked before anything mints. One bad item (unknown template, missing field, bad expiry) rejects the whole request with per-item detail — you will never get 1 of 2 passes issued.
• No pass-less messages. If the passes cannot be minted, the message is not sent. The failure surfaces in the API response so your retry logic can act on it. (Ordinary single-pass sends behave differently — they strip the tag and send anyway; multipass deliberately does not, because the passes are the payload.)
• Idempotency is yours. Every accepted call mints fresh passes — a retry of a delivered order will issue duplicates. Gate retries on your tracking_id.

Validation failure example

{
  "message": "Invalid Input Data",
  "missing_tags": ["code", "amount"]
}

1. One SMS/MMS from your configured sender, with one short link.
2. A branded landing page listing every pass in the send, numbered in order, each with a live preview and its own Add to Apple Wallet / Add to Google Wallet button.
3. “Add all” — a single tap adds every pass: Apple receives a multi-pass bundle (native one-sheet add), Google receives a multi-object save.
4. Passes stay live. Each pass supports later field updates and lock-screen push notifications (balance changes, reminders, offers) — see the Telemetry Guide for the event feed.

1. Confirm your saved trigger’s body contains <Add2WalletLink> and a pass template is configured.
2. Send a 2-item multipass request to your own mobile with distinct codes per item.
3. Verify: one message arrives, one link, the page lists both passes with the right codes/fields.
4. Add one pass individually on iPhone and Android; then use Add all and confirm both land in the wallet.
5. Send a deliberately broken request (e.g. drop code from one item) and confirm you get missing_tags and no message.
6. Re-send the same order and confirm your tracking_id gating prevents duplicate issuance.