Skip to main content
Upload support document
This operation exists in Discovery, but a matching public API gateway route is not configured. It is not currently available through the documented base URL.

Authorizations

Authorization
string
header
required

Authentication Method: HTTP Bearer token.

The runtime requires the literal Bearer prefix — a bare token in the Authorization header is rejected with 401 unauthorized.

Header Format: Authorization: Bearer YOUR_API_KEY

Your API key is a JWT. Live keys operate on live data (livemode: true); test keys operate on isolated test data (livemode: false).

Get your key at: app.gigstack.pro/settings?tab=api

Errors: credential failures are answered by the authentication layer with a raw { "message": … } body, not the standardized envelope — 401 for a missing, malformed or expired token, 403 for a revoked key or a plan without API access. See the Unauthorized and AuthForbidden responses.

Path Parameters

id
string
required

Client ID

Query Parameters

team
string

gigstack Connect: Target team ID for multi-team access.

Requires gigstack Connect enabled on your team and shared billing account.

Also requires the multipleIssuerAccounts feature on your plan. Requests targeting a team other than the one your API key belongs to return 403 without it.

Only API keys can use it: an OAuth access token sent with another team's id is rejected with 403 Team mismatch with OAuth token.

Optional — omit it entirely unless you are acting on another team. It deliberately carries no example value so generated snippets do not emit ?team=undefined; when the parameter is absent, the team is derived from your API key.

Example: ?team=team_xyz789

Body

multipart/form-data
file
file
required

The file to upload (PDF or image, max 10MB)

documentType
enum<string>
required

Type of supporting document

Available options:
contract,
delivery_proof,
payment_proof,
communication,
payment_confirmation,
subscription_info
name
string

Optional custom name for the document

Example:

"Service Contract"

description
string

Optional description of the document

Example:

"Master services agreement for 2026"

Response

Document uploaded. Standardized envelope (timestamp in epoch ms).

success
enum<boolean>
required
Available options:
true
data
object
required
timestamp
integer<int64>
required
message
string