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

Vaquill AI Uploads API

Getting files in. One presigned multipart flow at every size, with the bytes going straight to storage and never through this API. Initiate, PUT each part, then complete.

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

This API exposes 18 JSON Schema definitions.

Tagged areas include Uploads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, a changelog, and 18 JSON Schemas.

This API exposes 6 operations across 5 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.vaquill.ai/workspace, /workspace.

6 operations 5 paths 16 schemas 1 DELETE3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.vaquill.ai/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Vaquill AI Uploads API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (vq_ws_*) (WorkspaceAuth). By default, every request must be authenticated.

  • WorkspaceAuth — Workspace credential issued from the automation console at /automation. Send it as Authorization: Bearer vqws.... This is NOT a Data API key: a vqkey credentia…

Paths & Operations 6

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

Uploads 6

Getting files in. One presigned multipart flow at every size, with the bytes going straight to storage and never through this API. Initiate, PUT each part, then complete.

POST
/v1/uploads
Start an upload
uploads.initiate body → 201422401403429500503
GET
/v1/uploads
List upload sessions
uploads.list 3 params → 200422401403429500503
GET
/v1/uploads/{uploadId}/parts/{partNumber}
Re-sign one upload part
uploads.presignPart 2 params → 200422401403404429500503
POST
/v1/uploads/{uploadId}/complete
Finish an upload and start ingesting
uploads.complete 1 param body → 202422401403404429500503
GET
/v1/uploads/formats
List supported upload formats
uploads.formats → 200401403422429500503
DELETE
/v1/uploads/{uploadId}
Abort an upload
uploads.abort 1 param → 204422401403404429500503

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Operation (10 properties), UploadSummary (9 properties), ValidationProblem (7 properties), UploadInitiateRequest (6 properties). Each schema is shown below with its type and property counts.

OperationError
object
Why a failed operation failed, in terms a customer can act on. code is stable and machine-readable. message is sanitized: the internal job tables store stack t…
2 properties 2 required
OperationResource
object
What the operation produced, or is producing. url is a path on this API rather than an absolute URL, because the service is mounted today and gets its own host…
3 properties 2 required
UploadSession
object
An open upload, and every URL needed to fill it. Two things are deliberately not here. The R2 object KEY. It is inside each presigned URL and cannot not be, si…
5 properties 5 required
UploadPartLink
object
Where to PUT one part, and how long that stays true. expiresAt is on every part rather than on the session, because a large upload outlives a single signature:…
3 properties 3 required
ValidationProblem
object
A problem document for a schema rejection. errors lists the fields that were refused. The value you submitted is deliberately not echoed, so a validation failu…
7 properties 6 required
UploadInitiateRequest
object
Ask for somewhere to put a file. sizeBytes is required and is not advisory: it decides the part size and the part count, both of which are fixed for the life o…
6 properties 4 required
Page_UploadSummary_
object
2 properties 2 required
UploadCompleteRequest
object
Assemble the parts into the final object and start ingesting it.
1 property 1 required
CompletedPart
object
One uploaded part, as R2 acknowledged it.
2 properties 2 required
Pagination
object
Where the caller is, and whether there is more. total is the count of rows matching the filter, not the count returned, so a caller can size a job before runni…
4 properties 4 required
UploadSummary
object
One upload session as a LIST publishes it: no URLs, ever. UploadSession carries a presigned URL per part, and a list that returned it would mint parts x page s…
9 properties 7 required
Operation
object
One long-running operation, whatever kind of work it is. Readable for OPERATIONRETENTIONDAYS after creation, per AIP-151.
10 properties 4 required
OperationStatus
string
The public five. There is no sixth, and there are no synonyms. Internal vocabularies spell terminal success completed, ready, extracted, succeeded and fresh; t…
OperationProgress
object
How far along, and in what units. The unit is not decoration. A workflow run stores only a percentage while a matrix run stores cell counts, so {done: 43, tota…
3 properties 3 required
UploadFormats
object
What this API will accept, and how it will cut it into parts. Derived from adapters/uploadmedia, which is itself derived from app.core.filevalidation, rather t…
5 properties 5 required
Problem
object
An RFC 9457 problem document. Branch on type, which is stable; title and detail are written for people and may be reworded. Some problems carry extra members (…
6 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vaquill-ai-uploads-api-openapi.yml Raw ↑

Other APIs Vaquill AI publishes across the network.

Vaquill AI Board Watches API
Vaquill AI Chronology API
Vaquill AI Clients API
Vaquill AI Comparisons API
Vaquill AI Compliance API
Vaquill AI Credits API
Vaquill AI Documents API
Vaquill AI Drafting API
Vaquill AI Facts API
Vaquill AI Folders API
Vaquill AI India Credits API
Vaquill AI India Pricing API
Where this information came from

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