Persist a buffer as a managed file (service-to-service)

Used by fluide-capital-core and similar services. Requires FLUIDE_INTERNAL_FILE_TOKEN on caller and callee.

POST /api/v1/app/internal/files/buffer

cURL

cURL

curl -sS -X POST "$FLUIDE_BASE_URL/api/v1/app/internal/files/buffer" \
  -H "Authorization: Bearer $FLUIDE_ACCESS_TOKEN" \
  -H "X-Fluide-Api-Key: $FLUIDE_API_KEY" \
  -H "X-Fluide-Client-Id: fluide-developer" \
  -H "X-Workspace-Id: $FLUIDE_WORKSPACE_ID" \
  -H "X-Acting-Company-Id: $FLUIDE_COMPANY_ID" \
  -H "Content-Type: application/json" \
  -d '{}'

201

{
  "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.

Headers

X-Workspace-Id · string<uuid>

Partner / ISV only: UUID of the workspace that owns the client company. Required together with X-Acting-Company-Id when scoping product APIs to a merchant. See /getting-started/multi-tenancy.

X-Acting-Company-Id · string<uuid>

Partner / ISV only: UUID of the client company to act on. Must belong to the workspace in X-Workspace-Id.

Body

application/json

organizationId · string<uuid> · required

uploadedBy · string<uuid> · required

originalName · string · required

Required string length: 1 - 512

mimeType · string · required

Required string length: 3 - 120

Pattern: /^[\w/+.\-]+$/

contentBase64 · string · required

Base64-encoded file bytes (keep exports reasonably small until async chunking lands).

Required string length: 4 - 25000000

Response

201

application/json

Created successfully

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