Upsun Team Access API
The Team Access API from Upsun — 4 operation(s) for team access.
The Team Access API from Upsun — 4 operation(s) for team access.
openapi: 3.0.1
info:
title: Upsun.com Rest Add-ons Team Access API
version: '1.0'
contact:
name: Support
url: https://upsun.com/contact-us/
termsOfService: https://upsun.com/trust-center/legal/tos/
description: "# Introduction\n\nUpsun, formerly Platform.sh, is a container-based Platform-as-a-Service. Our main API\nis simply Git. With a single `git push` and a couple of YAML files in\nyour repository you can deploy an arbitrarily complex cluster.\nEvery [**Project**](#tag/Project) can have multiple applications (PHP,\nNode.js, Python, Ruby, Go, etc.) and managed, automatically\nprovisioned services (databases, message queues, etc.).\n\nEach project also comes with multiple concurrent\nlive staging/development [**Environments**](#tag/Environment).\nThese ephemeral development environments\nare automatically created every time you push a new branch or create a\npull request, and each has a full copy of the data of its parent branch,\nwhich is created on-the-fly in seconds.\n\nOur Git implementation supports integrations with third party Git\nproviders such as GitHub, Bitbucket, or GitLab, allowing you to simply\nintegrate Upsun into your existing workflow.\n\n## Using the REST API\n\nIn addition to the Git API, we also offer a REST API that allows you to manage\nevery aspect of the platform, from managing projects and environments,\nto accessing accounts and subscriptions, to creating robust workflows\nand integrations with your CI systems and internal services.\n\nThese API docs are generated from a standard **OpenAPI (Swagger)** Specification document\nwhich you can find here in [YAML](openapispec-upsun.yaml) and in [JSON](openapispec-upsun.json) formats.\n\nThis RESTful API consumes and produces HAL-style JSON over HTTPS,\nand any REST library can be used to access it. On GitHub, we also host\na few API libraries that you can use to make API access easier, such as our\n[PHP API client](https://github.com/upsun/upsun-sdk-php).\n\nIn order to use the API you will first need to have an [Upsun account](https://auth.upsun.com/register/) \nand [create an API Token](https://docs.upsun.com/anchors/cli/api-token/).\n\n# Authentication\n\n## OAuth2\n\nAPI authentication is done with OAuth2 access tokens.\n\n### API tokens\n\nYou can use an API token as one way to get an OAuth2 access token. This\nis particularly useful in scripts, e.g. for CI pipelines.\n\nTo create an API token, go to the \"API Tokens\" section\nof the \"Account Settings\" tab on the [Console](https://console.upsun.com).\n\nTo exchange this API token for an access token, a `POST` request\nmust be made to `https://auth.upsun.com/oauth2/token`.\n\nThe request will look like this in cURL:\n\n<pre>\ncurl -u platform-api-user: \\\n -d 'grant_type=api_token&api_token=<em><b>API_TOKEN</b></em>' \\\n https://auth.upsun.com/oauth2/token\n</pre>\n\nThis will return a \"Bearer\" access token that\ncan be used to authenticate further API requests, for example:\n\n<pre>\n{\n \"access_token\": \"<em><b>abcdefghij1234567890</b></em>\",\n \"expires_in\": 900,\n \"token_type\": \"bearer\"\n}\n</pre>\n\n### Using the Access Token\n\nTo authenticate further API requests, include this returned bearer token\nin the `Authorization` header. For example, to retrieve a list of\n[Projects](#tag/Project)\naccessible by the current user, you can make the following request\n(substituting the dummy token for your own):\n\n<pre>\ncurl -H \"Authorization: Bearer <em><b>abcdefghij1234567890</b></em>\" \\\n https://api.upsun.com/projects\n</pre>\n\n# HAL Links\n\nMost endpoints in the API return fields which defines a HAL\n(Hypertext Application Language) schema for the requested endpoint.\nThe particular objects returns and their contents can vary by endpoint.\nThe payload examples we give here for the requests do not show these\nelements. These links can allow you to create a fully dynamic API client\nthat does not need to hardcode any method or schema.\n\nUnless they are used for pagination we do not show the HAL links in the\npayload examples in this documentation for brevity and as their content\nis contextual (based on the permissions of the user).\n\n## _links Objects\n\nMost endpoints that respond to `GET` requests will include a `_links` object\nin their response. The `_links` object contains a key-object pair labelled `self`, which defines\ntwo further key-value pairs:\n\n* `href` - A URL string referring to the fully qualified name of the returned object. For many endpoints, this will be the direct link to the API endpoint on the region gateway, rather than on the general API gateway. This means it may reference a host of, for example, `eu-2.platform.sh` rather than `api.upsun.com`.\n* `meta` - An object defining the OpenAPI Specification (OAS) [schema object](https://swagger.io/specification/#schemaObject) of the component returned by the endpoint.\n\nThere may be zero or more other fields in the `_links` object resembling fragment identifiers\nbeginning with a hash mark, e.g. `#edit` or `#delete`. Each of these keys\nrefers to a JSON object containing two key-value pairs:\n\n* `href` - A URL string referring to the path name of endpoint which can perform the action named in the key.\n* `meta` - An object defining the OAS schema of the endpoint. This consists of a key-value pair, with the key defining an HTTP method and the value defining the [operation object](https://swagger.io/specification/#operationObject) of the endpoint.\n\nTo use one of these HAL links, you must send a new request to the URL defined\nin the `href` field which contains a body defined the schema object in the `meta` field.\n\nFor example, if you make a request such as `GET /projects/abcdefghij1234567890`, the `_links`\nobject in the returned response will include the key `#delete`. That object\nwill look something like this fragment:\n\n```\n\"#delete\": {\n \"href\": \"/api/projects/abcdefghij1234567890\",\n \"meta\": {\n \"delete\": {\n \"responses\": {\n . . . // Response definition omitted for space\n },\n \"parameters\": []\n }\n }\n}\n```\n\nTo use this information to delete a project, you would then send a `DELETE`\nrequest to the endpoint `https://api.upsun.com/api/projects/abcdefghij1234567890`\nwith no body or parameters to delete the project that was originally requested.\n\n## _embedded Objects\n\nRequests to endpoints which create or modify objects, such as `POST`, `PATCH`, or `DELETE`\nrequests, will include an `_embedded` key in their response. The object\nrepresented by this key will contain the created or modified object. This\nobject is identical to what would be returned by a subsequent `GET` request\nfor the object referred to by the endpoint.\n"
x-logo:
url: https://docs.upsun.com/images/upsun-api.svg
href: https://upsun.com/#section/Introduction
altText: Upsun logo
servers:
- url: '{schemes}://api.upsun.com'
description: The Upsun.com API gateway
variables:
schemes:
default: https
security:
- OAuth2: []
tags:
- name: Team Access
paths:
/projects/{project_id}/team-access:
parameters:
- $ref: '#/components/parameters/ProjectID'
get:
summary: List team access for a project
description: Returns a list of items representing the project access.
operationId: list-project-team-access
tags:
- Team Access
parameters:
- in: query
name: page[size]
description: Determines the number of items to show.
schema:
type: integer
minimum: 1
maximum: 200
default: null
- in: query
name: page[before]
description: Pagination cursor. This is automatically generated as necessary and provided in HAL links (_links); it should not be constructed externally.
schema:
type: string
- in: query
name: page[after]
description: Pagination cursor. This is automatically generated as necessary and provided in HAL links (_links); it should not be constructed externally.
schema:
type: string
- in: query
name: sort
description: 'Allows sorting by a single field.<br>
Use a dash ("-") to sort descending.<br>
Supported fields: `granted_at`, `updated_at`.
'
schema:
type: string
example: -updated_at
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
properties:
items:
type: array
items:
$ref: '#/components/schemas/TeamProjectAccess'
_links:
$ref: '#/components/schemas/ListLinks'
'400':
description: Bad Request
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
post:
summary: Grant team access to a project
description: Grants one or more team access to a specific project.
operationId: grant-project-team-access
tags:
- Team Access
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
type: object
properties:
team_id:
type: string
description: ID of the team.
required:
- team_id
responses:
'204':
description: No Content
'400':
description: Bad Request
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
/projects/{project_id}/team-access/{team_id}:
parameters:
- $ref: '#/components/parameters/ProjectID'
- $ref: '#/components/parameters/TeamID'
get:
summary: Get team access for a project
description: Retrieves the team's permissions for the current project.
operationId: get-project-team-access
tags:
- Team Access
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/TeamProjectAccess'
'403':
description: Forbidden
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
delete:
summary: Remove team access for a project
description: Removes the team from the current project.
operationId: remove-project-team-access
tags:
- Team Access
responses:
'204':
description: No Content
'400':
description: Bad Request
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
/teams/{team_id}/project-access:
parameters:
- $ref: '#/components/parameters/TeamID'
get:
summary: List project access for a team
description: Returns a list of items representing the team's project access.
operationId: list-team-project-access
tags:
- Team Access
parameters:
- in: query
name: page[size]
description: Determines the number of items to show.
schema:
type: integer
minimum: 1
maximum: 200
default: null
- in: query
name: page[before]
description: Pagination cursor. This is automatically generated as necessary and provided in HAL links (_links); it should not be constructed externally.
schema:
type: string
- in: query
name: page[after]
description: Pagination cursor. This is automatically generated as necessary and provided in HAL links (_links); it should not be constructed externally.
schema:
type: string
- in: query
name: sort
description: 'Allows sorting by a single field.<br>
Use a dash ("-") to sort descending.<br>
Supported fields: `project_title`, `granted_at`, `updated_at`.
'
schema:
type: string
example: -updated_at
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
properties:
items:
type: array
items:
$ref: '#/components/schemas/TeamProjectAccess'
_links:
$ref: '#/components/schemas/ListLinks'
'400':
description: Bad Request
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
post:
summary: Grant project access to a team
description: Adds the team to one or more specified projects.
operationId: grant-team-project-access
tags:
- Team Access
requestBody:
required: true
content:
application/json:
schema:
type: array
items:
type: object
properties:
project_id:
type: string
description: ID of the project.
required:
- project_id
responses:
'204':
description: No Content
'400':
description: Bad Request
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
/teams/{team_id}/project-access/{project_id}:
parameters:
- $ref: '#/components/parameters/TeamID'
- $ref: '#/components/parameters/ProjectID'
get:
summary: Get project access for a team
description: Retrieves the team's permissions for the current project.
operationId: get-team-project-access
tags:
- Team Access
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/TeamProjectAccess'
'403':
description: Forbidden
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
delete:
summary: Remove project access for a team
description: Removes the team from the current project.
operationId: remove-team-project-access
tags:
- Team Access
responses:
'204':
description: No Content
'400':
description: Bad Request
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Forbidden
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found
content:
application/problem+json:
schema:
$ref: '#/components/schemas/Error'
components:
parameters:
ProjectID:
name: project_id
in: path
required: true
description: The ID of the project.
schema:
type: string
TeamID:
name: team_id
in: path
required: true
description: The ID of the team.
schema:
type: string
schemas:
TeamProjectAccess:
type: object
properties:
team_id:
type: string
format: ulid
description: The ID of the team.
organization_id:
type: string
format: ulid
description: The ID of the organization.
project_id:
type: string
description: The ID of the project.
project_title:
type: string
description: The title of the project.
granted_at:
type: string
format: date-time
description: The date and time when the access was granted.
updated_at:
type: string
format: date-time
description: The date and time when the access was last updated.
_links:
type: object
properties:
self:
type: object
description: Link to the current access item.
properties:
href:
type: string
description: URL of the link.
update:
type: object
description: Link for updating the current access item.
properties:
href:
type: string
description: URL of the link.
method:
type: string
description: The HTTP method to use.
delete:
type: object
description: Link for deleting the current access item.
properties:
href:
type: string
description: URL of the link.
method:
type: string
description: The HTTP method to use.
Error:
description: ''
type: object
properties:
status:
type: string
message:
type: string
code:
type: number
detail:
type: object
title:
type: string
title: ''
x-examples:
example-1:
status: Invalid input
message: This field is required.
code: 400
detail:
field:
- This field is required.
title: Bad Request
Link:
type: object
title: Link
description: A hypermedia link to the {current, next, previous} set of items.
properties:
href:
type: string
description: URL of the link
ListLinks:
type: object
properties:
self:
$ref: '#/components/schemas/Link'
previous:
$ref: '#/components/schemas/Link'
next:
$ref: '#/components/schemas/Link'
securitySchemes:
OAuth2:
type: oauth2
flows:
authorizationCode:
tokenUrl: https://auth.api.platform.sh/oauth2/token
refreshUrl: https://auth.api.platform.sh/oauth2/token
scopes: {}
authorizationUrl: https://auth.api.platform.sh/oauth2/authorize
description: ''
OAuth2Admin:
type: oauth2
flows:
clientCredentials:
tokenUrl: https://auth.api.platform.sh/oauth2/token
refreshUrl: ''
scopes:
admin: administrative operations
description: ''
x-tagGroups:
- name: Organization Administration
tags:
- Organizations
- Organization Members
- Organization Invitations
- Organization Projects
- Add-ons
- name: Project Administration
tags:
- Project
- Domain Management
- Cert Management
- Certificate Provisioner
- Project Variables
- Repository
- Third-Party Integrations
- Support
- name: Environments
tags:
- Environment
- Environment Backups
- Environment Type
- Environment Variables
- Routing
- Source Operations
- Runtime Operations
- Deployment
- Autoscaling
- name: User Activity
tags:
- Project Activity
- Environment Activity
- name: Project Access
tags:
- Project Invitations
- Teams
- Team Access
- User Access
- name: Account Management
tags:
- API Tokens
- Connections
- MFA
- Users
- User Profiles
- SSH Keys
- Plans
- name: Billing
tags:
- Organization Management
- Subscriptions
- Orders
- Invoices
- Discounts
- Vouchers
- Records
- Profiles
- name: Global Info
tags:
- Project Discovery
- References
- Regions
- name: Internal APIs
tags:
- Project Settings
- Environment Settings
- Deployment Target
- System Information
- Container Profile