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

Lambda Support Tickets API

The Lambda Support Ticketing API is currently in beta. Contact support to enable access.

Lambda Support Tickets API is one of 13 APIs that Lambda publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Support Tickets. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 9 operations across 6 paths, and defines 24 schemas. It is described by OpenAPI 3.1.0, at version 1.10.0.

Requests are made against 2 base URLs: https://cloud.lambda.ai/, https://cloud.lambdalabs.com/.

9 operations 6 paths 24 schemas 1 DELETE4 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.10.0
Base URL
https://cloud.lambda.ai/api/v1
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Lambda Support Tickets API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • basicAuth — Basic HTTP authentication. Allowed headers: Authorization: Basic : Authorization: Basic
  • bearerAuth — Bearer HTTP authentication. Allowed headers: Authorization: Bearer

Paths & Operations 9

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

Support Tickets 9

The Lambda Support Ticketing API is currently in beta. Contact support to enable access.

GET
/api/v1/tickets
List support tickets
listTickets 6 params → 200400401403404
POST
/api/v1/tickets
Create a support ticket
createTicket body → 200400401403404
GET
/api/v1/tickets/{ticket_id}
Get a support ticket
getTicket 1 param → 200400401403404
PATCH
/api/v1/tickets/{ticket_id}
Update a support ticket
updateTicket 1 param body → 202400401403404
GET
/api/v1/tickets/{ticket_id}/attachments
List ticket attachments
listAttachments 2 params → 200400401403404
POST
/api/v1/tickets/{ticket_id}/attachments
Initiate attachment upload
initiateAttachmentUpload 1 param body → 200400401403404
DELETE
/api/v1/tickets/{ticket_id}/attachments/{attachment_id}
Delete attachment
deleteAttachment 2 params → 200400401403404
POST
/api/v1/tickets/{ticket_id}/attachments/{attachment_id}/complete
Complete attachment upload
completeAttachmentUpload 2 params → 200400401403404
GET
/api/v1/tickets/{ticket_id}/attachments/{attachment_id}/download
Get attachment download URL
getAttachmentDownloadUrl 2 params → 200400401403404

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are Ticket (12 properties), TicketCreateResponse (7 properties), Attachment (7 properties), AttachmentInitiateResponse (5 properties). Each schema is shown below with its type and property counts.

TicketStatus
string
The current status of a support ticket.
Ticket
object
12 properties 6 required
ApiErrorInvalidParameters
object
3 properties 2 required
TicketOrderByField
string
Specifies the field used to sort the list of tickets.
AttachmentInitiateResponse
object
Response with upload instructions.
5 properties 5 required
ApiErrorResourceNotFound
object
3 properties 3 required
ApiErrorNotFound
object
3 properties 2 required
Attachment
object
Attachment metadata.
7 properties 6 required
ApiErrorTicketNotFound
object
3 properties 3 required
ApiErrorForbidden
object
3 properties 2 required
TicketRequestType
string
The type of support ticket.
TicketCommentInput
object
1 property 1 required
SortDirection
string
Specifies the order in which to sort the list of tickets.
AttachmentUploadStatus
string
The current status of an attachment upload.
ApiErrorUnauthorized
object
3 properties 3 required
AttachmentDownloadResponse
object
The response with the download URL.
2 properties 2 required
TicketListResponse
object
2 properties 2 required
AttachmentListResponse
object
Response containing list of attachments.
1 property 1 required
TicketSeverity
string
The severity level for incident tickets.
TicketCreateResponse
object
7 properties 4 required
TicketType
string
The type of support ticket.
TicketComment
object
3 properties 3 required
ApiErrorAccountInactive
object
3 properties 3 required
EmptyResponse
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lambda-labs-support-tickets-api-openapi.yml Raw ↑

Other APIs Lambda publishes across the network.

Lambda Cloud API
Lambda 1-Click Clusters
Lambda Cloud Filesystems
Lambda Inference API
Lambda Audit Events API
Lambda Fabric API
Lambda Filesystems API
Lambda Firewalls API
Lambda Images API
Lambda Instances API
Lambda Regions API
Lambda SSH keys API
Where this information came from

This is an independent, third-party profile of Lambda Support Tickets 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.