Skip to main content
PATCH
/
api
/
v1
/
invoices
/
{id}
cURL
curl -sS -X PATCH "$FLUIDE_BASE_URL/api/v1/invoices/string" \
  -H "Authorization: Bearer $FLUIDE_ACCESS_TOKEN" \
  -H "X-Fluide-Api-Key: $FLUIDE_API_KEY" \
  -H "X-Fluide-Client-Id: fluide-developer" \
  -H "Content-Type: application/json" \
  -d '{}'
{
  "success": true,
  "message": "Operation completed successfully",
  "data": {}
}

Authorizations

​
Authorization
string
header
required

Access token JWT. Use as Authorization: Bearer . In the API playground, paste the JWT only.

​
X-Fluide-Api-Key
string
header
default:fl_dev_your_key
required

Developer API key (fl_dev_...). Required on every API call with a machine access token.

​
X-Fluide-Client-Id
string
header
default:fluide-developer
required

First-party client audience. Must match the fluide_client_id claim on the JWT. Use fluide-developer for Connect.

Path Parameters

​
id
string
required

Body

application/json
​
lineItems
object[]
required

Full replacement line items (draft-only). Totals are re-derived.

Minimum array length: 1
​
kind
enum<string>

Invoice document kind

Available options:
STANDARD,
PROFORMA,
CREDIT_NOTE,
DEBIT_NOTE,
DOWN_PAYMENT
​
dueDate
string

Due date

Example:

"2026-04-15"

​
notes
string

Additional notes

​
projectId
string<uuid>

Project accounting dimension

​
clientId
string<uuid>

Client / sub-ledger dimension

Response

Update an invoice

​
success
boolean
required

Whether the request succeeded

Example:

true

​
message
string
required

Human-readable outcome message (localized when i18n is configured)

Example:

"Operation completed successfully"

​
data
object

Endpoint-specific payload