curl --request POST \
--url https://api.gigstack.io/v2/invoices/eom/run \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/invoices/eom/run', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/eom/run"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"success": true,
"message": "The end-of-month global invoicing process has been triggered successfully.",
"timestamp": 1767225600000,
"data": {
"global_invoice_time": "31/01/2026 23:59:00"
}
}Trigger end-of-month global invoicing
Manually trigger the end-of-month (EOM) global invoicing process for your team, which groups pending receipts into global invoices.
Two hard preconditions:
- The API key must be livemode. Test keys are rejected with
403. - The call must happen on the last calendar day of the month (America/Mexico_City).
Any other day is rejected with
400. - The call must happen before 23:00 America/Mexico_City. From 23:00 on, the automatic
end-of-month run takes over and manual calls are rejected with
400.
The request body is ignored.
The response is returned as soon as the process is triggered — it does not wait for the run to finish. A validation pass runs asynchronously afterwards; failures there are logged server-side and are not reflected in this response.
curl --request POST \
--url https://api.gigstack.io/v2/invoices/eom/run \
--header 'Authorization: Bearer <token>'const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/invoices/eom/run', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/eom/run"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text){
"success": true,
"message": "The end-of-month global invoicing process has been triggered successfully.",
"timestamp": 1767225600000,
"data": {
"global_invoice_time": "31/01/2026 23:59:00"
}
}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
Response
EOM process triggered.
Standardized success envelope emitted by sendSuccessResponse.
true true
The operation payload.
Show child attributes
Show child attributes
Server time in epoch milliseconds (Luxon.now().toMillis()).
1767225600000
Human-readable summary. Present only when the handler supplies one.
"Operation completed successfully"