curl --request PATCH \
--url https://api.gigstack.io/v2/teams/{id}/integrations/zettle/connection-settings \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"automaticInvoicing": true
}
'const options = {
method: 'PATCH',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({automaticInvoicing: true})
};
fetch('https://api.gigstack.io/v2/teams/{id}/integrations/zettle/connection-settings', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/teams/{id}/integrations/zettle/connection-settings"
payload = { "automaticInvoicing": True }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.patch(url, json=payload, headers=headers)
print(response.text){
"success": true,
"timestamp": 123,
"data": {
"provider": "zettle",
"operation": "settings",
"livemode": true,
"effect_scope": "team_shared",
"data": {
"completed": true
}
}
}zettle settings
Requires a verified Firebase or active signed personal MCP user. Team API keys/OAuth cannot impersonate their creator. Current role, credential mode and target team are rechecked by the provider service; blocked users are refused. Response data carries provider, operation, livemode, effect_scope and the safe provider result.
Both settings are required. Current admin/editor or owning billing administrator authority and the configured connection mode are required. An active sync lease can return sync_busy.
curl --request PATCH \
--url https://api.gigstack.io/v2/teams/{id}/integrations/zettle/connection-settings \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"automaticInvoicing": true
}
'const options = {
method: 'PATCH',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({automaticInvoicing: true})
};
fetch('https://api.gigstack.io/v2/teams/{id}/integrations/zettle/connection-settings', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/teams/{id}/integrations/zettle/connection-settings"
payload = { "automaticInvoicing": True }
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.patch(url, json=payload, headers=headers)
print(response.text){
"success": true,
"timestamp": 123,
"data": {
"provider": "zettle",
"operation": "settings",
"livemode": true,
"effect_scope": "team_shared",
"data": {
"completed": true
}
}
}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.