curl --request GET \
--url https://api.gigstack.io/v2/invoices/transfer \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/invoices/transfer', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/transfer"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"message": "Items retrieved successfully",
"data": [
{}
],
"timestamp": 1767225600000,
"next": "eyJjcmVhdGVkX2F0IjoxNjc3NjUxMjM0fQ==",
"has_more": true,
"total_results": 150,
"page": 1,
"per_page": 10,
"truncated": false
}List transfer invoices
Retrieve a paginated list of transfer invoices (CFDI type T - Traslado with Carta Porte).
gigstack Connect: Access other teams’ invoices using the team parameter.
curl --request GET \
--url https://api.gigstack.io/v2/invoices/transfer \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.gigstack.io/v2/invoices/transfer', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.gigstack.io/v2/invoices/transfer"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"success": true,
"message": "Items retrieved successfully",
"data": [
{}
],
"timestamp": 1767225600000,
"next": "eyJjcmVhdGVkX2F0IjoxNjc3NjUxMjM0fQ==",
"has_more": true,
"total_results": 150,
"page": 1,
"per_page": 10,
"truncated": false
}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
Transfer invoices retrieved successfully
Response shape of the Firestore-backed list handlers. Note this is not the
standardized envelope: data sits at the top level alongside the pagination keys and
message/success/timestamp, rather than under a data wrapper.
A few modules (clients, payments, and the income, egress, payment and transfer invoice
lists) take a second code path when the request carries metadata.* / metadata_*
filters and the team has Typesense configured: Typesense resolves the matching ids and the
documents are then re-read from Firestore. That path returns has_more, total_results,
page and per_page instead of the cursor-style next. Modules without a Typesense
branch (receipts, retentions, users, invoice drafts) only ever return the cursor form.
On those invoice lists the invoice type is checked on each matching document, and at most
2,000 documents are scanned. truncated: true means the scan stopped there: total_results
and the pages only cover what was scanned, and narrowing the metadata filter lists the rest.
Full-text /search endpoints are different again — see SearchResponse.
Metadata-filtered invoice lists only. True when the scan stopped at its 2,000-document
cap before the matches ran out: total_results and the pages cover only what was
scanned, and has_more is false on the last scanned page even though more matches
exist. Narrow the metadata filter to reach them.
false