curl --request POST \
--url https://api.gigstack.io/v2/invoices/download/request \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"start_date": "2024-01-01",
"end_date": "2024-01-31",
"rfc_type": "received"
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({start_date: '2024-01-01', end_date: '2024-01-31', rfc_type: 'received'})
};
fetch('https://api.gigstack.io/v2/invoices/download/request', 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/request"
payload = {
"start_date": "2024-01-01",
"end_date": "2024-01-31",
"rfc_type": "received"
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"success": true,
"message": "2 solicitud(es) creada(s) para 2 período(s) mensual(es)",
"data": {
"created": [
"satreq_Ab12Cd34",
"satreq_Ef56Gh78"
],
"duplicates": [],
"chunks": 2,
"duplicate": false
}
}Create bulk download request
Submit a bulk download request to the SAT. The SAT processes these asynchronously — use GET /invoices/download/schedule/history to poll for status updates.
Prerequisites: FIEL uploaded (fiel_uploaded: true) + business registered (registered: true) + Descarga Masiva activated.
Date range: SAT limits each request to a maximum of 1 month. For longer periods, submit one request per month.
Once the request reaches completed status, the invoice metadata is available in the history response (invoiceCount, processedCount, latestIssueDate, earliestIssueDate).
curl --request POST \
--url https://api.gigstack.io/v2/invoices/download/request \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"start_date": "2024-01-01",
"end_date": "2024-01-31",
"rfc_type": "received"
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({start_date: '2024-01-01', end_date: '2024-01-31', rfc_type: 'received'})
};
fetch('https://api.gigstack.io/v2/invoices/download/request', 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/request"
payload = {
"start_date": "2024-01-01",
"end_date": "2024-01-31",
"rfc_type": "received"
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"success": true,
"message": "2 solicitud(es) creada(s) para 2 período(s) mensual(es)",
"data": {
"created": [
"satreq_Ab12Cd34",
"satreq_Ef56Gh78"
],
"duplicates": [],
"chunks": 2,
"duplicate": false
}
}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
Body
Start of date range (YYYY-MM-DD)
"2024-01-01"
End of date range (YYYY-MM-DD)
"2024-01-31"
Direction of invoices to download (default: received)
issued, received Download XML files (cfdi) or metadata only (default: cfdi)
cfdi, metadata Filter by CFDI type: I=income, E=expense, P=payment, N=payroll, T=transfer
I, E, P, N, T Filter by invoice status (default: all)
active, cancelled, all Filter by counterparty RFC
Minimum invoice amount
Maximum invoice amount