BursaPay Logo
Knowledge Base
Ticket Sign In
Help Center > Event Networking & Attendee Connect > Connection Self-Checks and Duplicate Prevention

Connection Self-Checks and Duplicate Prevention

Published 2026-08-24 5 min read
Who is this article for?
This guide is for Event Attendees, Delegates, Developers seeking operational guidance on BursaPay workflows.

UI Navigation Path (Step-by-Step)

  1. Confirm the sender and target IDs are different.
  2. Check whether a connection already exists.
  3. Send the request only when no existing connection blocks it.
  4. Handle the returned error instead of retrying the same invalid request.
Verified BursaPay networking workflow: Explains the guardrails that stop invalid attendee connections.

1. Overview & Purpose

The connection endpoint explicitly rejects self-connections and existing connections.

2. Requirements & Setup

Provide a valid sender profile and target profile.

3. Step-by-Step Workflow

  1. Confirm the sender and target IDs are different.
  2. Check whether a connection already exists.
  3. Send the request only when no existing connection blocks it.
  4. Handle the returned error instead of retrying the same invalid request.

4. Rules & Troubleshooting

The API returns a failure for self-connections and duplicate existing connections.

5. Verification & Next Steps

Treat these responses as validation outcomes, not transient failures.

Was this article useful?

Related Articles

Starting a Connection Request Connection Request Status: Pending, Accepted and Rejected
Ask Bursa AI