/api/v1/request-organisationRequest an organisation
Submits a request for a new organisation and its first workspace, for a signed-in user who does not belong to an organisation yet, and stores it for staff review.
This is the route for a signed-in user with no organisation of their own. Nothing
is created when you call it: the request is recorded with your contact details and
the names you want, and staff review it and create the organisation on approval.
You may have one open request at a time, so check
GET /api/v1/get-my-organisation-request
before submitting another. A user who already belongs to an organisation creates
further ones directly with POST /api/v1/create-org.
monthly_volume is a tier key rather than a figure, for example "1m_to_10m",
and referral_source_detail is required when referral_source is "other". The
stored request comes back as request, an OnboardingRequest documented under
Shared objects.
first_namestringrequiredlast_namestringrequiredwork_emailstringrequiredmessaging_platformstringrequiredmessaging_handlestringrequiredmonthly_volumestringrequiredreferral_sourcestringrequiredreferral_source_detailstringoptionalorg_namestringrequiredworkspace_namestringrequired#What happens next
Staff review the request. Read its progress with
GET /api/v1/get-my-organisation-request:
status is pending until it is reviewed, review_note carries the reviewer's
note, and was_created with created_org_uid records the organisation created
on approval, which is the id you then pass as org_uid to
POST /api/v1/create-workspace.