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

Sapien Upload Sessions API

The Upload Sessions API from Sapien — 6 operation(s) for upload sessions.

Sapien Upload Sessions API is one of 5 APIs that Sapien publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, /developer/v1.

6 operations 6 paths 14 schemas 2 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://sapien-poq.up.railway.app/developer/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — Developer API key using the Authorization: Bearer poqlive... header.

Paths & Operations 6

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

Upload Sessions 6
POST
/projects/{projectId}/upload-sessions
Create an upload session
createUploadSession 1 param body → 201default
GET
/projects/{projectId}/upload-sessions/{uploadId}
Get an upload session
getUploadSession 2 params → 200default
PUT
/projects/{projectId}/upload-sessions/{uploadId}/file
One-shot file upload (307 redirect)
uploadFileRedirect 4 params → 307default
POST
/projects/{projectId}/upload-sessions/{uploadId}/files
Declare files / refresh upload URLs
declareUploadFiles 2 params body → 200default
POST
/projects/{projectId}/upload-sessions/{uploadId}/process
Process an upload session
processUploadSession 2 params body → 202default
GET
/projects/{projectId}/upload-sessions/{uploadId}/status
Get processing status
getUploadSessionStatus 2 params → 200default

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are IngestRunResource (10 properties), GetUploadSessionOutputBody (9 properties), ProcessUploadSessionOutputBody (6 properties), CreateUploadSessionOutputBody (5 properties). Each schema is shown below with its type and property counts.

DeclaredUploadFile
object
2 properties 2 required
CreateUploadSessionOutputBody
object
5 properties 4 required
DeclaredFileResource
object
2 properties 2 required
DeclareUploadFilesOutputBody
object
4 properties 3 required
CreateUploadSessionInputBody
object
2 properties 1 required
GetUploadSessionStatusOutputBody
object
4 properties 3 required
PresignedUploadResource
object
3 properties 3 required
ProcessUploadSessionInputBody
object
3 properties
DeclareUploadFilesInputBody
object
2 properties 1 required
GetUploadSessionOutputBody
object
9 properties 8 required
ProcessUploadSessionOutputBody
object
6 properties 5 required
DeveloperStatusError
object
3 properties 1 required
ErrorEnvelope
object
4 properties 3 required
IngestRunResource
object
10 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sapien-upload-sessions-api-openapi.yml Raw ↑

Other APIs Sapien publishes across the network.

Sapien Datapoints API
Sapien Projects API
Sapien System API
Sapien Validators API
Where this information came from

This is an independent, third-party profile of Sapien Upload Sessions 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.