Verified BursaPay networking workflow: Explains the most common access failures visible from the implemented networking APIs.
1. Overview & Purpose
The APIs return explicit access errors when verification is missing, the session belongs to another event, or the attendee is not authorized to view the directory.
2. Requirements & Setup
Capture the event custom ID, profile ID where available, and the exact error returned.
3. Step-by-Step Workflow
- Confirm the event custom ID.
- Repeat the attendee email-verification step if the session is missing.
- Confirm the profile is verified.
- Verify ticket-holder or verified-profile eligibility before retrying the directory.
4. Rules & Troubleshooting
Do not bypass a 403 by changing unrelated account records; fix the failed verification/session/event condition.
5. Verification & Next Steps
Escalate with the event custom ID and safe profile identifier when the supported checks all pass but access still fails.