Members
Create
Delete
Update
ModelsExpand Collapse
MemberCreateResponse { project }
project: Project { id, createdAt, keys, 13 more }
keys: Array<Key>The keys of the project (get from the ProjectRoles table)
The keys of the project (get from the ProjectRoles table)
The key’s member id (its API user id, apiu_...), taken by the member and
usage routes (example: “apiu_eyVcnFJcR92BxBkz7N6g5w”)
The API key id (api_...), taken by the api-keys routes (example:
“api_eyVcnFJcR92BxBkz7N6g5w”)
A project role value. Accepted values are:
- a built-in role:
"admin","editor"or"reader"(seeProjectRoles); - a custom inline role: a
;-separated scope list, e.g."assets.write;workflows.run".
Resolved to capabilities by ProjectRole.scopesFromRole().
scope: "project" | "team"The scope of the API key: ‘project’ for project-scoped keys, ‘team’ for team-scoped keys
The scope of the API key: ‘project’ for project-scoped keys, ‘team’ for team-scoped keys
The API key last update date as an ISO string (example: “2023-02-03T11:19:41.579Z”)
The member who created the key: a human, or the member id (apiu_...) of
the team API key that created it.
The date the API key was last used to authenticate a request, as an ISO string (example: “2023-02-03T11:19:41.579Z”). Absent if the key has never been used.
The key’s effective consumption (CU) cap for the period (per-key override, else the team-wide default). Absent when the key is uncapped.
For a PROJECT key: the project it was created on (the team id on some legacy keys). Absent for team keys.
Whether the project is privacyMode In a privacyMode project, users can only see their own generated assets (except admins)
users: Array<User>The users of the project (get from the ProjectRoles table)
The users of the project (get from the ProjectRoles table)
The user email (example: “herve@scenario.com”)
A project role value. Accepted values are:
- a built-in role:
"admin","editor"or"reader"(seeProjectRoles); - a custom inline role: a
;-separated scope list, e.g."assets.write;workflows.run".
Resolved to capabilities by ProjectRole.scopesFromRole().
High-level markdown description of the project Only returned on single project GET, not on list
ISO string date when the description was last updated Only returned on single project GET, not on list
When true, IP detection is switched off for this project even if the team has an active posture. Absent means the team posture applies. The posture itself (disabled / active-fail-open / active-fail-closed) is a team-level setting, see the team’s ipDetectionEnforcement.
MemberDeleteResponse { project }
project: Project { id, createdAt, keys, 13 more }
keys: Array<Key>The keys of the project (get from the ProjectRoles table)
The keys of the project (get from the ProjectRoles table)
The key’s member id (its API user id, apiu_...), taken by the member and
usage routes (example: “apiu_eyVcnFJcR92BxBkz7N6g5w”)
The API key id (api_...), taken by the api-keys routes (example:
“api_eyVcnFJcR92BxBkz7N6g5w”)
A project role value. Accepted values are:
- a built-in role:
"admin","editor"or"reader"(seeProjectRoles); - a custom inline role: a
;-separated scope list, e.g."assets.write;workflows.run".
Resolved to capabilities by ProjectRole.scopesFromRole().
scope: "project" | "team"The scope of the API key: ‘project’ for project-scoped keys, ‘team’ for team-scoped keys
The scope of the API key: ‘project’ for project-scoped keys, ‘team’ for team-scoped keys
The API key last update date as an ISO string (example: “2023-02-03T11:19:41.579Z”)
The member who created the key: a human, or the member id (apiu_...) of
the team API key that created it.
The date the API key was last used to authenticate a request, as an ISO string (example: “2023-02-03T11:19:41.579Z”). Absent if the key has never been used.
The key’s effective consumption (CU) cap for the period (per-key override, else the team-wide default). Absent when the key is uncapped.
For a PROJECT key: the project it was created on (the team id on some legacy keys). Absent for team keys.
Whether the project is privacyMode In a privacyMode project, users can only see their own generated assets (except admins)
users: Array<User>The users of the project (get from the ProjectRoles table)
The users of the project (get from the ProjectRoles table)
The user email (example: “herve@scenario.com”)
A project role value. Accepted values are:
- a built-in role:
"admin","editor"or"reader"(seeProjectRoles); - a custom inline role: a
;-separated scope list, e.g."assets.write;workflows.run".
Resolved to capabilities by ProjectRole.scopesFromRole().
High-level markdown description of the project Only returned on single project GET, not on list
ISO string date when the description was last updated Only returned on single project GET, not on list
When true, IP detection is switched off for this project even if the team has an active posture. Absent means the team posture applies. The posture itself (disabled / active-fail-open / active-fail-closed) is a team-level setting, see the team’s ipDetectionEnforcement.
MemberUpdateResponse { project }
project: Project { id, createdAt, keys, 13 more }
keys: Array<Key>The keys of the project (get from the ProjectRoles table)
The keys of the project (get from the ProjectRoles table)
The key’s member id (its API user id, apiu_...), taken by the member and
usage routes (example: “apiu_eyVcnFJcR92BxBkz7N6g5w”)
The API key id (api_...), taken by the api-keys routes (example:
“api_eyVcnFJcR92BxBkz7N6g5w”)
A project role value. Accepted values are:
- a built-in role:
"admin","editor"or"reader"(seeProjectRoles); - a custom inline role: a
;-separated scope list, e.g."assets.write;workflows.run".
Resolved to capabilities by ProjectRole.scopesFromRole().
scope: "project" | "team"The scope of the API key: ‘project’ for project-scoped keys, ‘team’ for team-scoped keys
The scope of the API key: ‘project’ for project-scoped keys, ‘team’ for team-scoped keys
The API key last update date as an ISO string (example: “2023-02-03T11:19:41.579Z”)
The member who created the key: a human, or the member id (apiu_...) of
the team API key that created it.
The date the API key was last used to authenticate a request, as an ISO string (example: “2023-02-03T11:19:41.579Z”). Absent if the key has never been used.
The key’s effective consumption (CU) cap for the period (per-key override, else the team-wide default). Absent when the key is uncapped.
For a PROJECT key: the project it was created on (the team id on some legacy keys). Absent for team keys.
Whether the project is privacyMode In a privacyMode project, users can only see their own generated assets (except admins)
users: Array<User>The users of the project (get from the ProjectRoles table)
The users of the project (get from the ProjectRoles table)
The user email (example: “herve@scenario.com”)
A project role value. Accepted values are:
- a built-in role:
"admin","editor"or"reader"(seeProjectRoles); - a custom inline role: a
;-separated scope list, e.g."assets.write;workflows.run".
Resolved to capabilities by ProjectRole.scopesFromRole().
High-level markdown description of the project Only returned on single project GET, not on list
ISO string date when the description was last updated Only returned on single project GET, not on list
When true, IP detection is switched off for this project even if the team has an active posture. Absent means the team posture applies. The posture itself (disabled / active-fail-open / active-fail-closed) is a team-level setting, see the team’s ipDetectionEnforcement.