curl --request GET \
--url https://api.gigstack.io/v2/invoices/download/schedule \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/invoices/download/schedule', 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"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"data": {
"schedule": {
"enabled": true,
"time": "06:00",
"downloadTypes": [
"received"
],
"daysBack": 3,
"lastRunAt": 1767225600000,
"lastRunStatus": "success",
"lastRunError": null
},
"sat_completed": true,
"fiel_uploaded": true,
"registered": true,
"registered_at": 1767225600000,
"sync_start_date": "2021-01-01",
"fiel": {
"rfc": "MEE200101ABC",
"expires_at": 1893456000000,
"serial_number": "00001000000712345678",
"uploaded_at": 1767225600000
},
"prodigia": null
}
}Get schedule configuration
Returns the current scheduled download configuration plus FIEL and registration status. Use this to check setup progress before configuring a schedule or submitting download requests.
fiel_uploaded: true— FIEL credentials are storedregistered: true— Business is registered with the SAT, downloads are enabledschedule— Current schedule config, ornullif not configured yetfiel— FIEL certificate metadata (RFC, expiry, serial number)
curl --request GET \
--url https://api.gigstack.io/v2/invoices/download/schedule \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/invoices/download/schedule', 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"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"data": {
"schedule": {
"enabled": true,
"time": "06:00",
"downloadTypes": [
"received"
],
"daysBack": 3,
"lastRunAt": 1767225600000,
"lastRunStatus": "success",
"lastRunError": null
},
"sat_completed": true,
"fiel_uploaded": true,
"registered": true,
"registered_at": 1767225600000,
"sync_start_date": "2021-01-01",
"fiel": {
"rfc": "MEE200101ABC",
"expires_at": 1893456000000,
"serial_number": "00001000000712345678",
"uploaded_at": 1767225600000
},
"prodigia": null
}
}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