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

Lilt Uploads API

The Uploads API from Lilt — 7 operation(s) for uploads.

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

Tagged areas include Uploads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 8 operations across 7 paths, and defines 1 schema. It is described by OpenAPI 3.0.3, at version v3.0.3.

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

8 operations 7 paths 1 schemas 1 DELETE4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v3.0.3
Base URL
https://api.lilt.com
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Lilt Uploads API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuth). An API key is passed in the query as key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 8

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

Uploads 8
GET
/v2/upload
Get All Pending Uploads or specific list of uploads by ids or statuses
getPendingUploads 2 params → 200default
GET
/v2/upload/{uploadId}
Get Upload by ID
getUploadById 1 param → 200default
GET
/v2/upload/s3/params
Get S3 Upload Parameters
getS3UploadParams 6 params → 200default
POST
/v2/upload/s3/params
Initiate File Upload to Cloud Storage
initiateS3Upload body → 200default
POST
/v2/upload/s3/multipart
Initiate Multipart Upload
initiateMultipartUpload body → 200default
POST
/v2/upload/s3/multipart/{uploadId}/complete
Complete Multipart Upload
completeMultipartUpload 2 params body → 200default
GET
/v2/upload/s3/multipart/{uploadId}/{partNumber}
Sign Upload Part
signUploadPart 4 params → 200default
DELETE
/v2/upload/s3/multipart/{uploadId}
Cancel Multipart Upload
cancelMultipartUpload 2 params → 200default

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (1 property). Each schema is shown below with its type and property counts.

Error
object
Response in the event of an unexpected error.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lilt-uploads-api-openapi.yml Raw ↑

Other APIs Lilt publishes across the network.

Lilt Create API
Lilt Documents API
Lilt Domains API
Lilt Files API
Lilt Jobs API
Lilt Languages API
Lilt Memories API
Lilt Projects API
Lilt Segments API
Lilt Translate API
Lilt Webhook Configuration API
Lilt Workflows API
Where this information came from

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