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

Spot Accounts API

Create, update, list, and delete Spot accounts within an organization.

Spot Accounts API is one of 32 APIs that Spot by Flexera publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 8 JSON Schema definitions.

Tagged areas include Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 8 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.spotinst.io.

4 operations 2 paths 5 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.spotinst.io
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Spot Accounts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Spot API uses Bearer Token Authentication. Include your API token in the Authorization header.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Accounts 4

Create, update, list, and delete Spot accounts within an organization.

POST
/setup/account
Spot Create Account
createAccount body → 200
GET
/setup/account
Spot List Accounts
listAccounts 1 param → 200
PUT
/setup/account/{accountId}
Spot Update Account
updateAccount 1 param body → 200
DELETE
/setup/account/{accountId}
Spot Delete Account
deleteAccount 1 param → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Account (3 properties), AccountListResponse (2 properties), AccountResponse (2 properties), UpdateAccountRequest (1 property). Each schema is shown below with its type and property counts.

Account
object
3 properties
AccountResponse
object
2 properties
AccountListResponse
object
2 properties
CreateAccountRequest
object
1 property
UpdateAccountRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

flexera-accounts-api-openapi.yml Raw ↑

Other APIs Spot by Flexera publishes across the network.

Spot Access Policies API
Spot Audit API
Spot Billing Accounts API
Spot Billing Engine Setup API
Spot Cloud Credentials API
Spot Cost Analysis API
Spot Cost Intelligence API
Spot Deployments API
Spot Eco AWS API
Spot Eco Azure API
Spot Eco GCP API
Spot Elastigroup AWS API
Where this information came from

This is an independent, third-party profile of Spot Accounts 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.