curl --request POST \
--url https://api.gigstack.io/v2/invoices/{id}/send \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"emails": [
"accounting@example.com"
]
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({emails: ['accounting@example.com']})
};
fetch('https://api.gigstack.io/v2/invoices/{id}/send', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/{id}/send"
payload = { "emails": ["accounting@example.com"] }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"message": "Invoice email sent successfully",
"data": {
"recipients": [
"contabilidad@ejemplo.com"
],
"uuid": "B0C3E4F2-1A2B-4C5D-9E8F-0123456789AB",
"attachments": [
"Yx7Kp2Lm9Qw4Rt6Bn1Vc.pdf",
"Yx7Kp2Lm9Qw4Rt6Bn1Vc.xml"
]
}
}Resend invoice email
Resend an invoice email (PDF + XML attachments) to the client and/or additional recipients.
The client’s email on the invoice is always included. Extra recipients can be added via the emails field.
gigstack Connect: Send other teams’ invoice emails using the team parameter.
curl --request POST \
--url https://api.gigstack.io/v2/invoices/{id}/send \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"emails": [
"accounting@example.com"
]
}
'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({emails: ['accounting@example.com']})
};
fetch('https://api.gigstack.io/v2/invoices/{id}/send', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/{id}/send"
payload = { "emails": ["accounting@example.com"] }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"message": "Invoice email sent successfully",
"data": {
"recipients": [
"contabilidad@ejemplo.com"
],
"uuid": "B0C3E4F2-1A2B-4C5D-9E8F-0123456789AB",
"attachments": [
"Yx7Kp2Lm9Qw4Rt6Bn1Vc.pdf",
"Yx7Kp2Lm9Qw4Rt6Bn1Vc.xml"
]
}
}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
Invoice UUID or gigstack 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
Body
Additional email recipients beyond the client email on the invoice
["accounting@example.com"]