Create a project
Create a project in a workspace. The parent workspace is identified by the workspace_id
path parameter alone; the x-hh-workspace-id header does not participate.
The optional project_creator field names the user (by email) who receives the
project-creator membership on the new project. The named user must already be a member of
the workspace. When omitted, the project is created without any membership. The field is
only accepted on API-key-initiated requests. User-initiated creation always makes the
calling user the creator, so sending the field returns a 400.
The roles that membership carries come from your organization’s role configuration. An organization that grants no role on project creation is a supported case: the request still succeeds and the named user receives no access. A 200 response is not by itself confirmation that the named user was granted anything.
A project_creator who is already signed in does not see the new project immediately. A
session captures its scope tree and permission grants when it is created, so a membership
granted afterwards is not reflected in it. Creating the project marks that user’s sessions
for refresh, and the refresh takes effect on their next request to the control plane, so
an idle browser tab may need a page reload.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The unique identifier of the workspace the project is created in
Body
Request body for creating a project
Project display name
1Project description
Email of the user to grant the project-creator membership to (API key actors only). A signed-in user does not see the new project until their session refreshes, which happens on their next request to the control plane.

