Skip to main content
POST
/
api
/
v1
/
inter-company
/
post-due-to-due-from
cURL
curl -sS -X POST "$FLUIDE_BASE_URL/api/v1/inter-company/post-due-to-due-from" \
  -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.

Body

application/json
​
fromCompanyId
string<uuid>
required
​
toCompanyId
string<uuid>
required
​
dueToAccountId
string<uuid>
required
​
dueFromAccountId
string<uuid>
required
​
fromOffsetAccountId
string<uuid>
required

Offset account in from-company books (e.g. expense or AP).

​
toOffsetAccountId
string<uuid>
required

Offset account in to-company books (e.g. revenue or AR).

​
amount
number
required
Required range: x >= 0.01
​
date
string
required
​
description
string
​
idempotencyKey
string

Response

Post mirrored due-to / due-from journal entries (stub) — created

​
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