How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Spectro Cloud projects API

The projects API from Spectro Cloud — 12 operation(s) for projects.

Spectro Cloud projects API is one of 42 APIs that Spectro Cloud publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Project. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 23 operations across 12 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://edge-host-ip:5080.

23 operations 12 paths 33 schemas 5 DELETE6 GET1 PATCH3 POST8 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.spectrocloud.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Spectro Cloud projects API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Authorization).

  • Authorization — JWT authorization token obtained using /v1/users/default/login API

Paths & Operations 23

Across 12 paths, the API surfaces 23 operations — 5 DELETE, 6 GET, 1 PATCH, 3 POST, 8 PUT. Each is listed below with its method, path, parameters, and response codes.

projects 23
GET
/v1/projects
Retrieves a list of projects
v1ProjectsList 7 params → 200
POST
/v1/projects
Creates a project
v1ProjectsCreate 1 param body → 201
GET
/v1/projects/alerts
Retrieves a list of supported alerts for a project
v1ProjectsAlerts → 200
DELETE
/v1/projects/{uid}
Deletes the specified project
v1ProjectsUidDelete 2 params body → 204
GET
/v1/projects/{uid}
Returns the specified project
v1ProjectsUidGet 1 param → 200
PUT
/v1/projects/{uid}
Updates the specified project
v1ProjectsUidUpdate 1 param body → 204
DELETE
/v1/projects/{uid}/alerts/{component}
Deletes the specified alert to the specified project
v1ProjectsUidAlertDelete 2 params → 204
POST
/v1/projects/{uid}/alerts/{component}
Create the specified alert to the specified project
v1ProjectsUidAlertCreate 2 params body → 201
PUT
/v1/projects/{uid}/alerts/{component}
Upsert the specified alert to the specified project
v1ProjectsUidAlertUpdate 2 params body → 204
DELETE
/v1/projects/{uid}/alerts/{component}/{alertUid}
Deletes the specified alert of the specified project
v1ProjectsUidAlertsUidDelete 3 params → 204
GET
/v1/projects/{uid}/alerts/{component}/{alertUid}
Get the specified alert of the specified project
v1ProjectsUidAlertsUidGet 3 params → 200
PUT
/v1/projects/{uid}/alerts/{component}/{alertUid}
Update the specified alert of the specified project
v1ProjectsUidAlertsUidUpdate 3 params body → 204
DELETE
/v1/projects/{uid}/macros
Delete the macros for the specified project by macro name
v1ProjectsUidMacrosDeleteByMacroName 1 param body → 204
GET
/v1/projects/{uid}/macros
List the macros of the specified project
v1ProjectsUidMacrosList 1 param → 200
PATCH
/v1/projects/{uid}/macros
Update the macros for the specified project by macro name
v1ProjectsUidMacrosUpdateByMacroName 1 param body → 204
POST
/v1/projects/{uid}/macros
Create or add new macros for the specified project
v1ProjectsUidMacrosCreate 1 param body → 204
PUT
/v1/projects/{uid}/macros
Update the macros of the specified project
v1ProjectsUidMacrosUpdate 1 param body → 204
PUT
/v1/projects/{uid}/meta
Update the metadata of the specified project
v1ProjectsUidMetaUpdate 1 param body → 204
GET
/v1/projects/{uid}/preferences/clusterSettings
Get project cluster settings
v1ProjectClusterSettingsGet 1 param → 200
PUT
/v1/projects/{uid}/preferences/clusterSettings/nodesAutoRemediationSetting
Update project clusters nodes auto remediation setting
v1ProjectClustersNodesAutoRemediationSettingUpdate 1 param body → 204
PUT
/v1/projects/{uid}/teams
Update the teams association to the specified project
v1ProjectsUidTeamsUpdate 1 param body → 204
PUT
/v1/projects/{uid}/users
Update the users association to the specified project
v1ProjectsUidUsersUpdate 1 param body → 204
DELETE
/v1/projects/{uid}/validate
Validate and returns active resource of project before delete
v1ProjectsUidValidate 1 param → 200

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are v1Channel (8 properties), v1ObjectMeta (7 properties), v1ProjectSpec (4 properties), v1ListMetaData (4 properties). Each schema is shown below with its type and property counts.

v1TeamRoleMap
object
2 properties
v1UserRoleMap
object
2 properties
v1ObjectMeta
object
ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.
7 properties
v1Time
string
Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON. Wrappers are provided for many of the factory methods that the time pack…
v1AlertEntity
object
1 property
v1Uid
object
1 property 1 required
v1Macro
object
2 properties
v1ProjectActiveAppDeployment
object
Active app deployment
2 properties
v1ProjectEntity
object
Project information
2 properties
v1ProjectClusterSettings
object
2 properties
v1TenantClusterSettings
object
1 property
v1ProjectActiveCluster
object
Active clusters
2 properties
v1ObjectEntity
object
Object identity meta
2 properties
v1ProjectActiveResources
object
Active project resources
3 properties
v1Project
object
Project information
3 properties
v1Alert
object
2 properties
v1ProjectAlertComponents
object
Supported project alerts component
1 property
v1NodesAutoRemediationSettings
object
2 properties
v1ProjectSpec
object
Project specifications
4 properties
v1AlertNotificationStatus
object
3 properties
v1ProjectUsersEntity
object
1 property
v1ProjectCleanup
object
Project delete request payload
2 properties
v1ProjectActiveAppDeployments
object
Active app deployment
2 properties
v1ProjectStatus
object
Project status
2 properties
v1ProjectCleanUpStatus
object
Project cleanup status
3 properties
v1ProjectTeamsEntity
object
1 property
v1ProjectActiveClusters
object
Active clusters
2 properties
v1ListMetaData
object
ListMeta describes metadata for the resource listing
4 properties
v1ProjectAlertComponent
object
Project alert component
3 properties
v1Projects
object
2 properties 1 required
v1Channel
object
8 properties
v1ProjectEntitySpec
object
Project specifications
3 properties
v1Macros
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

spectro-cloud-projects-api-openapi.yml Raw ↑

Other APIs Spectro Cloud publishes across the network.

Spectro Cloud activations API
Spectro Cloud apiKeys API
Spectro Cloud appDeployments API
Spectro Cloud appProfiles API
Spectro Cloud audits API
Spectro Cloud auth API
Spectro Cloud cloudaccounts API
Spectro Cloud cloudconfigs API
Spectro Cloud clouds API
Spectro Cloud clustergroups API
Spectro Cloud clusterprofiles API
Spectro Cloud clusterTemplates API
Where this information came from

This is an independent, third-party profile of Spectro Cloud projects API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.