Spectro Cloud Palette platform capabilities are exposed via REST APIs, providing a subset of features that comply with open application programming interface (API) standards.
Palette interacts with external-facing utility tools such as Terraform to provision, change, and manage your environment automatically and efficiently.
Every API's URI has the prefix of the version and the Palette resource, such as:
Palette supports two types of user authentication methods:
- All requests must be authenticated with an API token that is passed using the HTTP request header
- Activated users can use the
/auth/authenticateAPI to authenticate and obtain the Authorization token.
- Every authorization token is valid for 15 min.
- To refresh the token use this GET call:
Palette uses API keys to provide secure API authentication and authorization. This enables the usage of Palette APIs without requiring user credentials such as username and password. The API key must be present in individual API requests in order to authenticate and authorize the request. The API Key is passed as part of the HTTP request header and in the following format:
- Key: ApiKey
- Value: API key copied from the Palette Console. E.g. QMOI1ZVKVIoW6LM6uXqSWFPsjmt0juvl
All requests are in the
JSON format. In general, the request payload has three sections: metadata, spec and status.
- Metadata consists of common attributes for all the resources such as ids, names, creation timestamps etc.
- Spec consists of attributes that define the resource
- Status contains the status information of the resource. The API does not support creating or modifying the status section.
|POST||To create a resource or a sub-resource.|
|PUT||To update the resource or a sub-resource. The PUT request will overwrite the existing resource data.|
|PATCH||To add, modify, remove a specific attribute or sub-resource within a resource.|
|DELETE||To delete the resource.|
The API returns standard HTTP response codes:
|200||For a successful response. The response payload will vary depending upon the API. Refer to the respective API response schema.|
|201||For a successful resource creation. The response payload contains the uid of the created resource.|
|204||Response without any content for a successful operation. These operations include update, delete and the other actions on the resource.|
|400||Bad request. The request does not adhere to the API request payload schema.|
|401||Missing authorization token or invalid authorization token.|
|403||The API operation is forbidden for the user.|
|404||The resource or the dependent resource is not found for the operation.|
|500||Operational error. For 500 error code, the server responds with an explicit error code and an error message.|
Palette APIs maintain backward compatibility until deprecation. The three API phases in the lifecycle are Production, Sunset, and Deprecated. Spectro Cloud will inform users when APIs transition through this lifecycle.
The Palette APIs are designed to work as intended and expected.
As the API approaches deprecation because it is being replaced or will no longer be supported, a notice will be provided in the documentation that outlines our intent and provides a cut-off date. Within three months of the deprecation date, a notice will be shared that counts down to the end date and recommends the API to use instead.
We indicate that an API is deprecated when it is no longer supported or recommended for use by including a tag to indicate its state. The API documentation will remain available as a subsection of deprecated APIs.
The API lifecycle also applies to external-facing tools such as Terraform.
The version information is included in the API URI, such as
v1. Future APIs will increment the version, leaving the earlier version intact. The existing API request and response schema will be modified to add new attributes or query parameters while maintaining backward compatibility with earlier schemas. Prior notice will be given before advancing to the next version, and users will be advised to migrate to the new API.
Palette groups resources under either a Tenant or Project scope. When making API requests targeting resources belonging to a project, the project scope should be specified. To specify the project scope, use the HTTP header key
ProjectUid with the value
<Project Uid> in the API request. The
ProjectUid needs to be specified for a request to be applied under a specific project scope.
curl --location --request \GET 'https://api.spectrocloud.com/v1/edgehosts/ad3d90ab-de6e-3e48-800f-4d663cec3060?resolvePackValues=false' \--header 'Accept: application/json' \--header 'ProjectUid: ad3d90ab-de6e-3e48-800f-4d663cec3060'
If you do not provide the ProjectUid header, then the assumed scope is of the tenant.
The resources list APIs are limited to 50 items, and therefore pagination is required to retrieve the complete resources list. The list API response includes listMeta with the continue token. To perform pagination, check the presence of the continue token value in the API response. For subsequent requests, use the continue token as a query parameter to paginate the remaining resource items.