Retrieving Invoices
Sales invoices with lines.
Use GET /api/v1/invoices to page through every record in your organization, or GET /api/v1/invoices/{id} to fetch a single record with its related data. The id is a UUID, and a 404 means it doesn't exist in your organization.
API Endpoint
GET
/api/v1/invoices
GET
/api/v1/invoices/{id}
Current Use Cases
Sync invoices to accounting
Send invoices with their lines to QuickBooks so receivables stay current.
Track unpaid invoices
Filter by status to see what's still open and follow up before it's late.
Tie invoices to orders
Filter by sales_order_id to see exactly what was billed against each order.
Close the month
Pull invoices by date range to reconcile revenue at month end.
Required Headers
Every request must include the following:
Header Key
Description
org-api-key
Your Organization API key. Contact Cloudbox Support For Access: support@cloudboxapp.com.
user-api-key
Your User API Key
Requests missing either header will return 401 Unauthorized
Example Request
bash
curl -X GET "https://app.cloudboxapp.com/api/v1/invoices?limit=100" \
-H "org-api-key: YOUR_ORG_API_KEY" \
-H "user-api-key: YOUR_USER_API_KEY" \
-H "Accept: application/json"
Response Schema
Column
Type
Description
Filters
Errors
Cloudbox uses standard HTTP status codes to indicate API success or failure:
- 200–299 – Request succeeded
- 400 – Bad request (missing parameters, invalid values)
- 401 – Unauthorized (missing or invalid API keys)
- 404 – Resource not found
- 429 – Too many requests (rate limited)