openapi: 3.0.1
info:
title: Upsun.com Rest Add-ons Cert Management 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: Cert Management
description: 'User-supplied SSL/TLS certificates can be managed using these
endpoints. You can now list and modify certificate provisioners
using the `/projects/{projectId}/provisioners` and
`/projects/{projectId}/provisioners/{certificateProvisionerDocumentId}`
endpoints. For more information, see our
[Third-party TLS certificate](https://docs.upsun.com/anchors/domains/custom/custom-certificates/)
documentation. These endpoints are not for managing certificates
that are automatically supplied by Upsun via Let''s Encrypt.
'
paths:
/projects/{projectId}/certificates:
get:
parameters:
- in: path
required: true
schema:
type: string
name: projectId
operationId: list-projects-certificates
responses:
default:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/CertificateCollection'
tags:
- Cert Management
summary: Get list of SSL certificates
description: 'Retrieve a list of objects representing the SSL certificates
associated with a project.
'
post:
parameters:
- in: path
required: true
schema:
type: string
name: projectId
operationId: create-projects-certificates
responses:
default:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/AcceptedResponse'
requestBody:
description: ''
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CertificateCreateInput'
tags:
- Cert Management
summary: Add an SSL certificate
description: 'Add a single SSL certificate to a project.
'
/projects/{projectId}/certificates/{certificateId}:
get:
parameters:
- in: path
required: true
schema:
type: string
name: projectId
- in: path
required: true
schema:
type: string
name: certificateId
operationId: get-projects-certificates
responses:
default:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/Certificate'
tags:
- Cert Management
summary: Get an SSL certificate
description: 'Retrieve information about a single SSL certificate
associated with a project.
'
patch:
requestBody:
description: ''
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CertificatePatch'
parameters:
- in: path
required: true
schema:
type: string
name: projectId
- in: path
required: true
schema:
type: string
name: certificateId
operationId: update-projects-certificates
responses:
default:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/AcceptedResponse'
tags:
- Cert Management
summary: Update an SSL certificate
description: 'Update a single SSL certificate associated with a project.
'
delete:
parameters:
- in: path
required: true
schema:
type: string
name: projectId
- in: path
required: true
schema:
type: string
name: certificateId
operationId: delete-projects-certificates
responses:
default:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/AcceptedResponse'
tags:
- Cert Management
summary: Delete an SSL certificate
description: 'Delete a single SSL certificate associated with a project.
'
/projects/{projectId}/provisioners:
get:
parameters:
- in: path
required: true
schema:
type: string
name: projectId
operationId: list-projects-provisioners
responses:
default:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/CertificateProvisionerCollection'
tags:
- Cert Management
/projects/{projectId}/provisioners/{certificateProvisionerDocumentId}:
get:
parameters:
- in: path
required: true
schema:
type: string
name: projectId
- in: path
required: true
schema:
type: string
name: certificateProvisionerDocumentId
operationId: get-projects-provisioners
responses:
default:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/CertificateProvisioner'
tags:
- Cert Management
patch:
requestBody:
description: ''
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CertificateProvisionerPatch'
parameters:
- in: path
required: true
schema:
type: string
name: projectId
- in: path
required: true
schema:
type: string
name: certificateProvisionerDocumentId
operationId: update-projects-provisioners
responses:
default:
description: ''
content:
application/json:
schema:
$ref: '#/components/schemas/AcceptedResponse'
tags:
- Cert Management
components:
schemas:
CertificateProvisionerCollection:
type: array
items:
$ref: '#/components/schemas/CertificateProvisioner'
CertificatePatch:
type: object
properties:
chain:
type: array
items:
type: string
title: Certificate chain
description: The certificate chain
is_invalid:
type: boolean
title: Is Invalid
description: Whether this certificate should be skipped during provisioning
additionalProperties: false
AcceptedResponse:
type: object
properties:
status:
type: string
title: Status text
description: The status text of the response
code:
type: integer
title: Status code
description: The status code of the response
required:
- status
- code
additionalProperties: false
Certificate:
type: object
properties:
id:
type: string
title: Certificate Identifier
description: The identifier of Certificate
created_at:
type: string
format: date-time
nullable: true
title: Creation date
description: The creation date
updated_at:
type: string
format: date-time
nullable: true
title: Update date
description: The update date
certificate:
type: string
title: Certificate
description: The PEM-encoded certificate
chain:
type: array
items:
type: string
title: Certificate chain
description: The certificate chain
is_provisioned:
type: boolean
title: Is Provisioned
description: Whether this certificate is automatically provisioned
is_invalid:
type: boolean
title: Is Invalid
description: Whether this certificate should be skipped during provisioning
is_root:
type: boolean
title: Is Root
description: Whether this certificate is root type
domains:
type: array
items:
type: string
title: Domains
description: The domains covered by this certificate
auth_type:
type: array
items:
type: string
title: Authentication Type
description: The type of authentication the certificate supports
issuer:
type: array
items:
type: object
properties:
oid:
type: string
title: OID
description: The OID of the attribute
alias:
type: string
nullable: true
title: Alias
description: The alias of the attribute, if known
value:
type: string
title: Value
description: The value
required:
- oid
- alias
- value
additionalProperties: false
title: Issuer
description: The issuer of the certificate
expires_at:
type: string
format: date-time
title: Expiration date
description: Expiration date
required:
- id
- created_at
- updated_at
- certificate
- chain
- is_provisioned
- is_invalid
- is_root
- domains
- auth_type
- issuer
- expires_at
additionalProperties: false
CertificateCreateInput:
type: object
properties:
certificate:
type: string
title: Certificate
description: The PEM-encoded certificate
key:
type: string
title: Private Key
description: The PEM-encoded private key
chain:
type: array
items:
type: string
title: Certificate chain
description: The certificate chain
is_invalid:
type: boolean
title: Is Invalid
description: Whether this certificate should be skipped during provisioning
required:
- certificate
- key
additionalProperties: false
CertificateCollection:
type: array
items:
$ref: '#/components/schemas/Certificate'
CertificateProvisionerPatch:
type: object
properties:
directory_url:
type: string
title: ACME directory url
description: The URL to the ACME directory
email:
type: string
title: Contacted email address
description: The email address for contact information
eab_kid:
type: string
nullable: true
title: EAB Key identifier
description: The key identifier for Entity Attestation Binding
eab_hmac_key:
type: string
nullable: true
title: EAB HMAC Key
description: The Keyed-'Hashing Message Authentication Code' for Entity Attestation Binding
additionalProperties: false
CertificateProvisioner:
type: object
properties:
id:
type: string
title: CertificateProvisioner Identifier
description: The identifier of CertificateProvisioner
directory_url:
type: string
title: ACME directory url
description: The URL to the ACME directory
email:
type: string
title: Contacted email address
description: The email address for contact information
eab_kid:
type: string
nullable: true
title: EAB Key identifier
description: The key identifier for Entity Attestation Binding
eab_hmac_key:
type: string
nullable: true
title: EAB HMAC Key
description: The Keyed-'Hashing Message Authentication Code' for Entity Attestation Binding
required:
- id
- directory_url
- email
- eab_kid
- eab_hmac_key
additionalProperties: false
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