curl --request GET \
--url https://api.gigstack.io/v2/invoices/download/schedule/history \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/invoices/download/schedule/history', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/download/schedule/history"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"data": {
"history": [
{
"id": "satreq_Ab12Cd34",
"rfcType": "received",
"startDate": "2026-01-01",
"endDate": "2026-01-31",
"status": "completed",
"invoiceCount": 143,
"processedCount": 143,
"source": "manual",
"latestIssueDate": "2026-01-30",
"earliestIssueDate": "2026-01-02",
"createdAt": 1767225600000,
"completedAt": 1767312000000
}
]
}
}Get download request history
Returns the last 20 download requests for your team, ordered by most recent first.
Live status check: Any pending requests (accepted, processing, pending) are checked against the SAT in real time before the response is returned, so you always get up-to-date statuses in a single call.
Statuses:
| Status | Meaning |
|---|---|
pending | Request queued, being sent to SAT |
accepted | SAT accepted the request, processing started |
processing | SAT is generating the package |
completed | Done — invoice metadata is available in the response |
failed | SAT rejected the request (see statusMessage) |
expired | Package expired before it was downloaded |
curl --request GET \
--url https://api.gigstack.io/v2/invoices/download/schedule/history \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/invoices/download/schedule/history', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/download/schedule/history"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"data": {
"history": [
{
"id": "satreq_Ab12Cd34",
"rfcType": "received",
"startDate": "2026-01-01",
"endDate": "2026-01-31",
"status": "completed",
"invoiceCount": 143,
"processedCount": 143,
"source": "manual",
"latestIssueDate": "2026-01-30",
"earliestIssueDate": "2026-01-02",
"createdAt": 1767225600000,
"completedAt": 1767312000000
}
]
}
}Authorizations
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.
Query Parameters
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