Organiser marketplace
Organiser profiles, event briefs, proposals, and appointed event operations.
The organiser marketplace connects host organisations with appointed organisers. Published directory profiles and briefs can be discovered without a session; workspace views and mutations enforce live organisation membership in the API.
Directory and briefs
| Operation | Access | Purpose |
|---|---|---|
GET /api/organisers | Public | List published organiser profiles. |
GET /api/organisers/briefs | Public or optional session | List published briefs; mine=host or mine=organiser requires a live organiser membership. |
GET /api/organisers/profile | Owner or admin membership | Read the current organisation profile. |
POST /api/organisers/profile | Owner or admin membership | Save the current organisation profile. |
Briefs and proposals
| Operation | Access | Purpose |
|---|---|---|
POST /api/organisers/briefs | Owner or admin membership | Create or update an event-planning brief. |
POST /api/organisers/briefs/invite | Host owner or admin membership | Invite an organiser to a brief. |
GET /api/organisers/proposals | Owner or admin membership | List proposals for a brief. |
POST /api/organisers/proposals | Owner or admin membership | Submit a proposal. |
POST /api/organisers/proposals/action | Owner or admin membership | Shortlist, decline, withdraw, or select a proposal. |
POST /api/organisers/briefs/event | Host owner or admin membership | Link a brief to a host event. |
POST /api/organisers/briefs/close | Host owner or admin membership | Close a brief. |
Appointments
| Operation | Access | Purpose |
|---|---|---|
POST /api/organisers/appointments | Host owner or admin membership | Request a direct appointment for an existing organiser company. |
GET /api/organisers/appointments | Host or appointed membership | List appointments; staff-designated appointment members may read their assigned appointments. |
POST /api/organisers/appointments/action | Owner or admin membership | Accept, decline, or revoke an appointment. |
POST /api/organisers/appointments/members | Appointed owner or admin membership | Set staff members for an appointment. |
Appointment memberUserIds are account user UUIDs, not organisation membership-row IDs. Use the optional userId from GET /api/partner/team when selecting designated people. Pending appointments have a response deadline; accepted appointments remain active until revoked. Only the host can revoke an appointment.
All mutations require an exact configured Origin. The generated OpenAPI
document remains the executable source for request and response schemas,
validation limits, and response status details.
Direct appointments (API 4.5.0)
POST /api/organisers/appointments accepts { "eventId": "uuid", "organizationId": "uuid" }
and returns { "id": "appointment-uuid" }. The caller must be a live owner/admin of the
host workspace, and the event must belong to that host. The selected company must be
another active workspace with a published organiser profile and an active owner/admin.
Use the existing searchable, paginated organiser directory to select it.
A request starts pending with a seven-day response deadline. It appears in the company's workspace; no email is sent. Its owner/admin must accept before event access is available. Acceptance designates that administrator; they can then assign other active managers through the existing members operation. The host can revoke the appointment and its dependent crew grants. Event ownership and host approvals do not change.
Creation returns 409 if the event already has a pending or accepted appointment; expired pending requests no longer block a replacement. Concurrent direct requests and proposal selection share the event lock and the existing uniqueness constraint. Missing or ineligible event/company targets return 404, and insufficient authority returns 403.
Appointment responses add optional organizationName, hostOrganizationName, venue,
startsAt, endsAt and source (direct or proposal) fields. Existing records and
response fields remain compatible. Direct requests have no fabricated brief or proposal.
Appointed event changes
Appointed organisers can prepare supported event changes for host review. The request list is scoped to the host event or the caller's accepted appointment.
| Operation | Access | Purpose |
|---|---|---|
GET /api/partner/events/approvals | Host membership or appointed organiser | List pending changes visible to the current host or appointment. |
POST /api/partner/events/approvals/review | Host owner/admin, or designated appointee for withdrawal | Approve or reject a change as host; withdraw it as the appointed organiser. |

