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

The San Francisco Compute Company Images API

Custom machine images for instances.

The San Francisco Compute Company Images API is one of 14 APIs that The San Francisco Compute Company publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Image. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 9 operations across 7 paths, and defines 25 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.sfcompute.com.

9 operations 7 paths 25 schemas 1 DELETE3 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.sfcompute.com/preview/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

The San Francisco Compute Company Images API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer_auth). By default, every request must be authenticated.

  • bearer_auth — Create an API token using sf tokens create or at https://sfcompute.com/account/api-keys.

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 1 DELETE, 3 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Images 9

Custom machine images for instances.

POST
/preview/v2/images
Create image
create_image body → 201400401403409500
GET
/preview/v2/images
List images
list_images 5 params → 200400401403500
DELETE
/preview/v2/images/{id}
Delete image
delete_image 1 param → 200401403404409500
GET
/preview/v2/images/{id}
Get image
fetch_image 1 param → 200401403404500
POST
/preview/v2/images/{id}/complete
Complete image upload
complete_image_upload 1 param body → 200400401403404500
GET
/preview/v2/images/{id}/download
Download image
download_image 1 param → 200401403404409500
POST
/preview/v2/images/{id}/parts
Get upload part URL
create_image_upload_part_url 1 param body → 200400401403404500
POST
/preview/v2/images/{id}/reinstate
Reinstate image
reinstate_image 1 param → 200401403404409500
POST
/preview/v2/images/{id}/revoke
Revoke image
revoke_image 1 param → 200401403404409500

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are ImageScope (7 properties), ImageDownloadResponse (4 properties), ListImagesResponse (4 properties), ErrorDetail (3 properties). Each schema is shown below with its type and property counts.

Name
string
ImageDownloadResponse
object
4 properties 4 required
ImageListEntry
ImageScope
object
7 properties 7 required
ListImagesResponse
object
4 properties 3 required
DeleteImageResponse
object
3 properties 3 required
NotFoundError
object
1 property 1 required
imageResourcePath_ImageId
string
A resource path for a image resource. Format: sfc:image: : : .
ResourcePathOrId_WorkspaceId
string
A resource path like 'sfc:workspace:acme:my-workspace' or an ID. Resource paths are human-readable but not stable - they change when resources are renamed or m…
ForbiddenError
object
1 property 1 required
UploadPartRequest
object
1 property 1 required
StartUploadRequest
object
Start a multipart image upload. Max image size is 128 GiB.
2 properties 1 required
ConflictError
object
1 property 1 required
ImageUploadStatus
string
InternalServerError
object
1 property 1 required
WorkspaceId
string
ErrorDetail
object
3 properties 2 required
UnauthorizedError
object
1 property 1 required
UnixEpoch
integer
Unix timestamp.
ImageUploadResponse
ImageId
Accepts the canonical prefix below; additional legacy prefixes are aliased for read compatibility. Writes always emit the canonical form.
CompleteUploadRequest
object
Complete a multipart image upload.
1 property 1 required
ImagesCursor
string
UploadPartResponse
object
2 properties 2 required
BadRequestError
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

the-san-francisco-compute-company-images-api-openapi.yml Raw ↑

Other APIs The San Francisco Compute Company publishes across the network.

The San Francisco Compute Company Account API
The San Francisco Compute Company Deployments API
The San Francisco Compute Company Feature Flags API
The San Francisco Compute Company Instance SKU Catalog API
The San Francisco Compute Company Instance SKUs API
The San Francisco Compute Company Instance Templates API
The San Francisco Compute Company Instances API
The San Francisco Compute Company Orderbook API
The San Francisco Compute Company Orders API
The San Francisco Compute Company Pools API
The San Francisco Compute Company Procurements API
The San Francisco Compute Company Users API
Where this information came from

This is an independent, third-party profile of The San Francisco Compute Company Images 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.