curl --request POST \
--url https://api.gigstack.io/v2/invoices/draft/{id}/stamp \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"return_files": true,
"send_email": true
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({return_files: true, send_email: true})
};
fetch('https://api.gigstack.io/v2/invoices/draft/{id}/stamp', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/draft/{id}/stamp"
payload = {
"return_files": True,
"send_email": True
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)Stamp draft invoice (finalize)
Integration note: Verified staging result: HTTP 200, data.uuid, data.status valid, and no data.id. Retrieve the issued invoice using the returned UUID, not the former draft ID. The stored draft determines livemode; a test key does not convert an existing live draft into a test draft. Read shared fields and the Mexico or Colombia guide for country-specific meaning. The linked fiscal recipes and staging issuance results use a Mexican issuer.
Stamp (finalize) a draft invoice into a valid CFDI with SAT.
The draft must have all required fields before stamping:
client— a valid client with fiscal dataitems— at least one itemuse— CFDI use code (e.g.,G03gastos en general,S01sin efectos fiscales)payment_form— payment form code (e.g., 03, 99)payment_method— PUE or PPDcurrency— currency code (e.g., MXN, USD)
After stamping:
- The draft document is deleted
- A new stamped invoice document is created with a UUID from SAT
- The response follows the same format as
POST /invoices/income
gigstack Connect: Stamp other teams’ drafts using the team parameter.
curl --request POST \
--url https://api.gigstack.io/v2/invoices/draft/{id}/stamp \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"return_files": true,
"send_email": true
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({return_files: true, send_email: true})
};
fetch('https://api.gigstack.io/v2/invoices/draft/{id}/stamp', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/draft/{id}/stamp"
payload = {
"return_files": True,
"send_email": True
}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)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.
Path Parameters
Draft invoice ID
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