API reference › Finance › Pro formas

Retrieve pro formas for the authenticated user

GET /v1/finance/my-proformas

Scope
finance:read
Roles
admin, client, scheduler

Fetches a paginated list of pro formas for the current user (client) based on their role.

Parameters

Query parameters

NameTypeDescription
searchstring

Search query to filter pro formas by pro forma number, client name, or email.

Example PRF-001.

statusstring

Filter pro formas by status.

One of: draft, sent, approved, rejected, converted. Example sent.

typestring

Filter by document generation type (manual or system_generated). Same as proformaType; takes precedence if both are sent.

One of: manual, system_generated. Example manual.

proformaTypestring

Filter by manual vs system_generated. Ignored if type is set.

One of: manual, system_generated. Example manual.

startDatestring (date)

Filter pro formas created on or after this date (YYYY-MM-DD).

Example 2025-01-01.

endDatestring (date)

Filter pro formas created on or before this date (YYYY-MM-DD).

Example 2025-12-31.

sortBystring

Sort pro formas by a specific field (e.g., 'created_at', 'total').

Example created_at.

sortOrderstring

Sorting order: ascending ('asc') or descending ('desc').

One of: asc, desc. Example desc.

perPageinteger

Number of pro formas to retrieve per page.

Example 10.

Every call also sends Authorization and X-Tenant-ID; see Getting started.

Example request

Shell
curl "https://api.fetchfido.ai/v1/finance/my-proformas" \
  -H "Authorization: Bearer $FIDO_API_KEY" \
  -H "X-Tenant-ID: $FIDO_TENANT_ID"

Try it

Responses

200 Pro formas retrieved successfully

Pro formas retrieved successfully

JSON
{
  "success": true,
  "data": [
    {
      "is_paid": true,
      "paid_label": "Paid in pro forma",
      "client": {
        "id": "CLT-12345",
        "name": "John Doe",
        "email": "user@example.com"
      },
      "issueDate": "2026-01-15",
      "dueDate": "2026-01-15",
      "paymentTerms": {
        "id": 1,
        "label": "Example label"
      },
      "taxPercentage": 0,
      "discountAmount": 0,
      "subtotal": 0,
      "balanceDue": 0,
      "expiryDate": "2026-01-15",
      "isExpired": true,
      "invoiceIds": [
        {
          "id": "INV-ABC123",
          "portal_accessible": false
        }
      ],
      "assignmentIds": [
        null
      ],
      "shiftIds": [
        null
      ]
    }
  ],
  "meta": {
    "currentPage": 1,
    "lastPage": 5,
    "perPage": 10,
    "total": 50
  }
}
Response fields (29)

3 top-level fields; 2 hold nested fields, listed below.

FieldTypeDescription
successboolean

Example true.

dataarray of object (22 nested)
metaobject (4 nested)

Nested fields

data 22 fields
FieldTypeDescription
data[].is_paidboolean

Example true.

data[].paid_labelstring or null

Example Paid in pro forma.

data[].clientobject
data[].client.idstring

Example CLT-12345.

data[].client.namestring

Example John Doe.

data[].client.emailstring

Example user@example.com.

data[].issueDatestring or null

Example 2026-01-15.

data[].dueDatestring or null

Example 2026-01-15.

data[].paymentTermsobject or null
data[].paymentTerms.idinteger

Example 1.

data[].paymentTerms.labelstring

Example Example label.

data[].taxPercentagenumber or null

Example 0.

data[].discountAmountnumber

Example 0.

data[].subtotalnumber

Example 0.

data[].balanceDuenumber

Example 0.

data[].expiryDatestring or null

Example 2026-01-15.

data[].isExpiredboolean

Example true.

data[].invoiceIdsarray of object

Selected invoices on the pro forma with per-item portal linkability

data[].invoiceIds[].idstring

Example INV-ABC123.

data[].invoiceIds[].portal_accessibleboolean

When false, hide View in client portal and render inline from selectedInvoicesSummary on detail

Example false.

data[].assignmentIdsarray of any
data[].shiftIdsarray of any
meta 4 fields
FieldTypeDescription
meta.currentPageinteger

Example 1.

meta.lastPageinteger

Example 5.

meta.perPageinteger

Example 10.

meta.totalinteger

Example 50.

401 Not signed in

Unauthorized - Authentication required

JSON
{
  "success": false,
  "message": "Invalid API key. Org and user tier keys must send an X-Tenant-ID header naming the organization the key was issued for.",
  "errors": null,
  "code": "API_KEY_MISSING"
}
Response fields (4)
FieldTypeDescription
successboolean

Example false.

messagestring

Example Invalid API key. Org and user tier keys must send an X-Tenant-ID header naming the organization the key was issued for..

errorsany or null

Null on this status.

codestring

Machine-readable reason, for branching on in client code.

One of: API_KEY_MISSING, API_KEY_INVALID, API_KEY_EXPIRED. Example API_KEY_MISSING.

403 Not allowed

Scope, tenant, IP allow-list or RBAC check failed.

JSON
{
  "success": false,
  "message": "You don't have permission to access this endpoint. This API key is missing the 'finance:read' scope.",
  "errors": null,
  "code": ""
}
Response fields (4)
FieldTypeDescription
successboolean

Example false.

messagestring

Example You don't have permission to access this endpoint. This API key is missing the 'finance:read' scope..

errorsany or null

Null on this status.

codestring

Always empty on this status.

Example .

429 Too many requests

Rate limit exceeded. See Retry-After.

JSON
{
  "success": false,
  "message": "You've exceeded this API key's rate limit of 120 requests per minute. Try again in 37 seconds.",
  "errors": null,
  "code": "RATE_LIMITED"
}
Response fields (4)
FieldTypeDescription
successboolean

Example false.

messagestring

Example You've exceeded this API key's rate limit of 120 requests per minute. Try again in 37 seconds..

errorsany or null

Null on this status.

codestring

Machine-readable reason, for branching on in client code.

One of: RATE_LIMITED. Example RATE_LIMITED.

500 Server error

Internal Server Error

JSON
{
  "success": false,
  "message": "An unexpected error occurred."
}
Response fields (2)
FieldTypeDescription
successboolean

Example false.

messagestring

Example An unexpected error occurred..