activated_wristband

A cashless wristband (chip) was linked to a ticket.

The chip becomes an identifier and a verified edge chip ↔ barcode, strength 100: later cashless payments on the chip join the ticket holder.

Sent with	server, platform keys (see write keys)
Mode	strict: exactly the declared fields; an undeclared key, a wrong type or a missing required key quarantines the event
Version	1 (_schema_version on the stored row)
State	active
Required fields	none
Revenue	none: the revenue block is refused
Identity evidence	chip ↔ barcode, strength 100, verified
Before consent	no

Fields

The activity's own fields, sent as features. Identifier and attribute fields are moved out of features by the processor; see identifiers and attributes.

Field	Type	Required	What happens to it	Meaning
event_id	string	no, may be null	stays in features	The Eventix event the activity is about. Copied to the stream's _event_id column, so filters on an event are fast; it must be a plain string.

Example

One activity in a batch to POST /v1/activities, with debug so the answer says what the processor made of it. The envelope page explains every top-level field.

{
  "batch": [
    {
      "activity_id": "0192f1a4-9c50-7519-8000-9c5051960000",
      "activity": "activated_wristband",
      "ts": "2026-10-17T20:00:00+02:00",
      "owner_ref": "own:own_01M4XX0033FV7QXDRB5BQBRPGR",
      "identifiers": [
        {
          "type": "chip",
          "value": "WB-0093",
          "role": "holder",
          "namespace": "payvent"
        },
        {
          "type": "barcode",
          "value": "TK-4471",
          "role": "holder",
          "namespace": "weeztix"
        }
      ],
      "features": {
        "event_id": "3a114ef5-6105-48fd-aafc-0ae609d0536c"
      }
    }
  ],
  "debug": true
}

Try it

Sends this request from your browser. The key and the endpoint are kept in this browser only.

ServiceWrite key

POST /v1/activities{ "batch": [ { "activity_id": "0192f1a4-9c50-7519-8000-9c5051960000", "activity": "activated_wristband", "ts": "2026-10-17T20:00:00+02:00", "owner_ref": "own:own_01M4XX0033FV7QXDRB5BQBRPGR", "identifiers": [ { "type": "chip", "value": "WB-0093", "role": "holder", "namespace": "payvent" }, { "type": "barcode", "value": "TK-4471", "role": "holder", "namespace": "weeztix" } ], "features": { "event_id": "3a114ef5-6105-48fd-aafc-0ae609d0536c" } } ], "debug": true }

Versions

Version	Mode	Key classes	Change
1 (current)	strict	server, platform	first version

A published version never changes; a change is a new version, and every stored row says which version it was checked against.