curl --request POST \
--url https://api.gigstack.io/v2/invoices/download/preview \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"start_date": "2026-01-01",
"end_date": "2026-08-31",
"directions": []
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({start_date: '2026-01-01', end_date: '2026-08-31', directions: []})
};
fetch('https://api.gigstack.io/v2/invoices/download/preview', 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/preview"
payload = {
"start_date": "2026-01-01",
"end_date": "2026-08-31",
"directions": []
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"success": true,
"message": "Sincronización encolada",
"data": {
"id": "satjob_a1b2c3d4e5",
"status": "queued",
"total_windows": 8
}
}Preview a range of SAT history before paying for it
Availability: This operation has no configured public API gateway route and is not available through the documented base URL.
Queues a metadata pull for a date range and reports how many CFDIs exist and what downloading them would cost.
Reading header data from the SAT costs nothing; only fetching an XML is billed. This endpoint uses that gap: it stores what it finds as browsable rows in the metadata stage, which you can list with GET /invoices/sat?sync_state=metadata and then selectively import.
Answers 202, not 200. One month is roughly a twelve second round trip to the SAT and a full history is dozens of them, well past any HTTP timeout. Poll GET /invoices/download/jobs/{id} for progress.
Only one job may run per team at a time.
curl --request POST \
--url https://api.gigstack.io/v2/invoices/download/preview \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"start_date": "2026-01-01",
"end_date": "2026-08-31",
"directions": []
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({start_date: '2026-01-01', end_date: '2026-08-31', directions: []})
};
fetch('https://api.gigstack.io/v2/invoices/download/preview', 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/preview"
payload = {
"start_date": "2026-01-01",
"end_date": "2026-08-31",
"directions": []
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"success": true,
"message": "Sincronización encolada",
"data": {
"id": "satjob_a1b2c3d4e5",
"status": "queued",
"total_windows": 8
}
}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