Connections

The Connections area of the Byndr product API manages relationships between event attendees. When one attendee scans another's badge, a reciprocal connection is created between both parties. These connections are persistent, status-driven, and allow each party to independently manage their view of the relationship.EndFragment

Connection States:

• Pending: A connection is proposed but awaits approval. (Currently not in use)

• Active: Both parties have accepted the connection.

• Blocked: One party has explicitly blocked the other.

• Deleted: Soft-deleted connection; can be re-established.

Typical Flow:

1. Attendee scans another badge via QR code.

2. The system authenticates the user and processes the scan.

3. A reciprocal connection is created (e.g. Active ↔ Pending).

4. An Encounter and optional Metadata are recorded.

5. Users can later approve, block, or delete the connection.

Connection Perspective

All connections and their associated statuses are interpreted from the perspective of the initiator user.

This means that:

• The connection status (e.g. connected, pending, blocked) always reflects how the initiator views the relationship with the target user.

• Actions such as creating, deleting, blocking, or retrieving connections are performed and evaluated as if seen from the initiator’s side.

This ensures consistency when querying or manipulating connections via the API.