Mojo UpDocs
API reference

Project teams

One team or specialist of the project

GET/projects/v1/{id}/teams/{teamId}

The team exactly as the project's team list gives it (AIOE 0.49.0). A copy that was merged into another team answers 410 merged with into, so a workbench can follow it without making a change; anything the project does not use answers 404.

Authorization

AuthorizationBearer <token>

A device access token from the device-code flow (aioe_at_…). A DPoP-bound token is sent as Authorization: DPoP <token> with a fresh DPoP proof on every request.

In: header

Path Parameters

id*string

The project.

teamId*string

The team or specialist.

Header Parameters

X-Aioe-Organisation?string

Mojo Up AI Cloud only, with a person's access token: the id of the organisation the request is for. A person's session is not tied to one organisation, so each request names it. Device tokens already carry their organisation.

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/projects/v1/string/teams/string"
{}

Remove a team or specialist of the project

DELETE/projects/v1/{id}/teams/{teamId}

The project's owners and contributors. Only a team granted to this project alone can be removed here.

Authorization

AuthorizationBearer <token>

A device access token from the device-code flow (aioe_at_…). A DPoP-bound token is sent as Authorization: DPoP <token> with a fresh DPoP proof on every request.

In: header

Path Parameters

id*string

The project.

teamId*string

The team or specialist.

Header Parameters

X-Aioe-Organisation?string

Mojo Up AI Cloud only, with a person's access token: the id of the organisation the request is for. A person's session is not tied to one organisation, so each request names it. Device tokens already carry their organisation.

Response Body

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/projects/v1/string/teams/string"
Empty

Create or update a team or specialist of the project

PUT/projects/v1/{id}/teams/{teamId}

The project's owners and contributors, with a sign-in or a desktop's token. A body of exactly { "use": true } takes an organisation team the caller can see into this project ({ "use": false } stops using it here), instead of answering id_taken (AIOE 0.47.0). A copy merged into another team answers 410 merged with into. A key left out stays as stored and null clears it. A team new here is granted to this project alone; which projects and pools a team is granted to stays a portfolio manager's. The answer is the team with memberSchema 2, ignored[] (keys the platform did not take) and refused[] (field changes that lost to a newer edit, each with path, ours and theirs). 201 when created, 200 when updated.

Authorization

AuthorizationBearer <token>

A device access token from the device-code flow (aioe_at_…). A DPoP-bound token is sent as Authorization: DPoP <token> with a fresh DPoP proof on every request.

In: header

Path Parameters

id*string

The project.

teamId*string

The team or specialist. Lower-case letters, digits and -, at most 100 characters.

Header Parameters

X-Aioe-Organisation?string

Mojo Up AI Cloud only, with a person's access token: the id of the organisation the request is for. A person's session is not tied to one organisation, so each request names it. Device tokens already carry their organisation.

Request Body

application/json

The team as the workbench saves it, with every member field.

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PUT "https://example.com/projects/v1/string/teams/string" \  -H "Content-Type: application/json" \  -d '{}'
{  "memberSchema": 2,  "kind": "team",  "ignored": [    "string"  ],  "refused": [    {      "path": "string",      "ours": null,      "theirs": null    }  ]}

The words a team editor offers

GET/portfolio/v1/teams/vocabulary

The union of the teams blocks of the policy manifests the organisation holds, the newest build's word first where two disagree. With none held, the workbench's role words and thinking levels stand alone and the runtime and model lists are empty. For a person or their desktop.

Authorization

AuthorizationBearer <token>

A device access token from the device-code flow (aioe_at_…). A DPoP-bound token is sent as Authorization: DPoP <token> with a fresh DPoP proof on every request.

In: header

Header Parameters

X-Aioe-Organisation?string

Mojo Up AI Cloud only, with a person's access token: the id of the organisation the request is for. A person's session is not tied to one organisation, so each request names it. Device tokens already carry their organisation.

Response Body

application/json

application/json

application/json

curl -X GET "https://example.com/portfolio/v1/teams/vocabulary"
{  "roles": [    {      "id": "string",      "words": "string"    }  ],  "runtimes": [    {      "id": "string",      "name": "string"    }  ],  "thinkingLevels": [    "string"  ],  "models": [    {}  ],  "from": [    {      "digest": "string",      "versions": [        "string"      ]    }  ]}