Vendors and partners
Applying
Section titled “Applying”| Route | Who it is for |
|---|---|
/collaborate |
Landing page for every partnership type |
/collaborate/vendor |
Vendor / booth information |
/collaborate/vendor/book |
Booth application and booking |
/collaborate/vendor/applied |
Post-submission confirmation |
/collaborate/sponsor |
Sponsorship enquiry |
/collaborate/media |
Media and press enquiry |
Applications land in vendorApplications; sponsorship and media enquiries land
in partnershipLeads, and both are worked from the admin portal.
After applying
Section titled “After applying”Vendors manage their own application from the profile area:
| Route | What it does |
|---|---|
/profile/vendor/applications |
List of the vendor’s applications |
/profile/vendor/applications/[id] |
One application: status, messages, payment |
/profile/vendor/announcements/[id] |
Announcements sent to vendors for an event |
Messaging between the vendor and the team runs through
vendorApplicationMessages, so the thread stays attached to the application
rather than living in someone’s email.
Paying for a booth
Section titled “Paying for a booth”Approved applications check out at /checkout/booth/[applicationId]. Booth
holds run for 60 minutes, cut to 45 once payment starts — longer than the
15-minute windows elsewhere, because booth decisions involve more people.
The rest of the payment path is identical to Booking and checkout, including the server-side amount check and webhook idempotency.
Related routers
Section titled “Related routers”vendorApplications, vendorApplicationMessages, vendorAnnouncements,
vendorProfiles, vendorContacts, vendorInvoices, vendorPageContent,
booths, collaborate, partnershipLeads.