Manually confirm the outcome of a pending cancellation
curl --request POST \
--url https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"outcome": "aceptada"
}
'import requests
url = "https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve"
payload = { "outcome": "aceptada" }
headers = {
"X-API-Key": "<api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {'X-API-Key': '<api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({outcome: 'aceptada'})
};
fetch('https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS => json_encode([
'outcome' => 'aceptada'
]),
CURLOPT_HTTPHEADER => [
"Content-Type: application/json",
"X-API-Key: <api-key>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"strings"
"net/http"
"io"
)
func main() {
url := "https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve"
payload := strings.NewReader("{\n \"outcome\": \"aceptada\"\n}")
req, _ := http.NewRequest("POST", url, payload)
req.Header.Add("X-API-Key", "<api-key>")
req.Header.Add("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.post("https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve")
.header("X-API-Key", "<api-key>")
.header("Content-Type", "application/json")
.body("{\n \"outcome\": \"aceptada\"\n}")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Post.new(url)
request["X-API-Key"] = '<api-key>'
request["Content-Type"] = 'application/json'
request.body = "{\n \"outcome\": \"aceptada\"\n}"
response = http.request(request)
puts response.read_body{
"id": "<string>",
"invoiceId": "<string>",
"motivo": "01",
"requiresApproval": true,
"cancellationStatus": "pendiente",
"createdAt": "2023-11-07T05:31:56Z",
"folioSustitucion": {},
"respondBy": {},
"requestedBy": {},
"resolvedBy": {},
"resolvedAt": {}
}Invoices
Resolve Cancellation
Timbrix cannot query SAT in real time for the receptor’s response — call this once you’ve confirmed the outcome via the SAT portal.
POST
/
invoices
/
{uuid}
/
cancellations
/
{cancellationId}
/
resolve
Manually confirm the outcome of a pending cancellation
curl --request POST \
--url https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"outcome": "aceptada"
}
'import requests
url = "https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve"
payload = { "outcome": "aceptada" }
headers = {
"X-API-Key": "<api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)const options = {
method: 'POST',
headers: {'X-API-Key': '<api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({outcome: 'aceptada'})
};
fetch('https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS => json_encode([
'outcome' => 'aceptada'
]),
CURLOPT_HTTPHEADER => [
"Content-Type: application/json",
"X-API-Key: <api-key>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"strings"
"net/http"
"io"
)
func main() {
url := "https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve"
payload := strings.NewReader("{\n \"outcome\": \"aceptada\"\n}")
req, _ := http.NewRequest("POST", url, payload)
req.Header.Add("X-API-Key", "<api-key>")
req.Header.Add("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.post("https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve")
.header("X-API-Key", "<api-key>")
.header("Content-Type", "application/json")
.body("{\n \"outcome\": \"aceptada\"\n}")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.example.com/invoices/{uuid}/cancellations/{cancellationId}/resolve")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Post.new(url)
request["X-API-Key"] = '<api-key>'
request["Content-Type"] = 'application/json'
request.body = "{\n \"outcome\": \"aceptada\"\n}"
response = http.request(request)
puts response.read_body{
"id": "<string>",
"invoiceId": "<string>",
"motivo": "01",
"requiresApproval": true,
"cancellationStatus": "pendiente",
"createdAt": "2023-11-07T05:31:56Z",
"folioSustitucion": {},
"respondBy": {},
"requestedBy": {},
"resolvedBy": {},
"resolvedAt": {}
}Manually confirms the outcome of a cancellation that required receptor approval (
See Cancel Invoice for the full field reference on this
requiresApproval: true, cancellationStatus: "pendiente"). Timbrix cannot query the SAT in real time for the receptor’s response — call this endpoint once you’ve verified the actual outcome on the SAT portal.
This is a flat route, same pattern as Cancel Invoice — no /organizations/{organizationId}/ prefix.
Authentication
Accepts either:- A Supabase Bearer session (
Authorization: Bearer <token>) — the authenticated user must be an owner or admin of the invoice’s organization. Plain members can request a cancellation via Cancel Invoice, but cannot resolve one, mirroring the same restriction in the Timbrix dashboard, since resolving can flip a CFDI’sstatustocancelado. - An API key (
X-API-Key: sk_...) with thewrite:invoicesscope — the key’s own organization must match the invoice’s organization. API keys are scoped by thewrite:invoicesscope rather than per-member roles, so the owner/admin restriction only applies to session-authenticated callers.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
uuid | string (UUID) | Yes | Folio fiscal UUID of the invoice |
cancellationId | string (UUID) | Yes | ID of the cancellation request to resolve — the id returned by Cancel Invoice or List Invoice Cancellations |
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
outcome | string | Yes | aceptada or rechazada — the confirmed result you observed on the SAT portal |
What happens
outcome: "aceptada"— the invoice’sstatustransitions tocancelado. The cancellation is now final.outcome: "rechazada"— the invoice staysvigente. A rejected attempt does not block retries — you can request a new cancellation for the same invoice via Cancel Invoice.
Example Request
cURL
curl -X POST https://api.timbrix.mx/invoices/d3bfbc57-44af-4390-a064-f0afab85e5df/cancellations/6a1b2c3d-4e5f-4890-9abc-def012345678/resolve \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-d '{
"outcome": "aceptada"
}'
TypeScript
// Not yet available in @timbrix/sdk — call the REST endpoint directly
// until SDK support for cancellations ships.
const response = await fetch(
"https://api.timbrix.mx/invoices/d3bfbc57-44af-4390-a064-f0afab85e5df/cancellations/6a1b2c3d-4e5f-4890-9abc-def012345678/resolve",
{
method: "POST",
headers: {
Authorization: "Bearer <your_token>",
"Content-Type": "application/json",
},
body: JSON.stringify({ outcome: "aceptada" }),
}
)
const cancellation = await response.json()
console.log(cancellation.cancellationStatus)
Example Response
{
"id": "6a1b2c3d-4e5f-4890-9abc-def012345678",
"invoiceId": "0f2a1c3e-1a2b-4c3d-9e8f-1234567890ab",
"motivo": "02",
"folioSustitucion": null,
"requiresApproval": true,
"respondBy": "2026-08-12T15:50:03.412Z",
"cancellationStatus": "aceptada",
"requestedBy": "9f8e7d6c-5b4a-3210-fedc-ba9876543210",
"resolvedBy": "9f8e7d6c-5b4a-3210-fedc-ba9876543210",
"resolvedAt": "2026-08-11T10:15:00.000Z",
"createdAt": "2026-08-09T15:50:03.412Z"
}
InvoiceCancellationDto shape.
Common Errors
400 Bad Request
The cancellation was already resolved (cancellationStatus is not pendiente).
{
"statusCode": 400,
"message": "Esta solicitud de cancelación ya fue resuelta",
"error": "BAD_REQUEST"
}
401 Unauthorized
Missing or invalid Bearer token / API key.403 Forbidden
The authenticated user is not a member of the invoice’s organization, is a member but not an owner/admin, or the API key does not have thewrite:invoices scope / belongs to a different organization than the one that owns the invoice.
404 Not Found
uuid does not match any invoice, or cancellationId does not match a cancellation request for that invoice.Authorizations
apiKeybearer
API Key for authentication (format: sk_...)
Body
application/json
Resultado confirmado manualmente por el usuario tras verificar el estatus real en el portal del SAT — Timbrix no puede consultarlo en tiempo real (ver docs/superpowers/specs/2026-08-10-cfdi-cancelacion-design.md).
Available options:
aceptada, rechazada Example:
"aceptada"
Response
Available options:
01, 02, 03, 04 Available options:
pendiente, aceptada, rechazada