> ## Documentation Index > Fetch the complete documentation index at: https://docs.contazen.ro/llms.txt > Use this file to discover all available pages before exploring further. # Export Expenses > Export expense data to CSV or PDF format with all filtering options available ## Overview The Export Expenses endpoint allows you to download your expense data in structured formats for external analysis, reporting, or archival purposes. You can export all expenses or use the same filtering options available in the List Expenses endpoint. This endpoint returns file data directly rather than JSON, so the response format differs from other API endpoints. ## Query Parameters Export format: * `csv` - Comma-separated values file (Excel compatible) * `pdf` - Portable Document Format (currently not implemented) ### Filtering Parameters All filtering parameters from the [List Expenses](/api-reference/endpoints/expenses/list) endpoint are supported: Filter by supplier CzUid Filter by expense category ID Filter by payment status (paid, unpaid, overdue, registered) Filter by currency code Filter by payment type ID (1-7) Start date for filtering expenses End date for filtering expenses Sort field (created\_at, date, due\_date, amount) Sort order (asc, desc) ## Response Formats ### CSV Export (`format=csv`) The CSV export includes the following columns: | Column | Description | | ------------------ | ------------------------------------------ | | Reference | Reference number or invoice number | | Date | Expense date | | Due Date | Payment due date | | Supplier | Supplier name | | Category | Expense category name | | Description | Expense description | | Amount | Total amount | | Currency | Currency code | | VAT % | VAT percentage | | Amount without VAT | Amount excluding VAT | | VAT Amount | VAT amount | | Status | Payment status (Paid/Unpaid) | | Payment Date | Date when expense was paid (if applicable) | | Payment Type | Payment method name (if paid) | **File characteristics:** * UTF-8 encoding with BOM for Excel compatibility * Comma-separated values * Headers included in first row * Filename format: `expenses_YYYY-MM-DD.csv` ### PDF Export (`format=pdf`) PDF export is currently not implemented. The endpoint will return a JSON error message indicating this feature is not yet available. ## Response Headers ### CSV Export ``` Content-Type: text/csv; charset=utf-8 Content-Disposition: attachment; filename="expenses_2024-01-20.csv" ``` ### Error Responses ``` Content-Type: application/json ``` ## Pagination Behavior Unlike the List Expenses endpoint, the export endpoint **does not use pagination**. It will export all expenses matching your filter criteria in a single file. Be mindful when exporting large datasets. ## Use Cases ### Accounting Integration Export expenses for import into accounting software: ```javascript theme={null} const exportUrl = 'https://api.contazen.ro/v1/expenses/export?format=csv&start_date=2024-01-01&end_date=2024-01-31'; // Download and import into accounting system ``` ### Monthly Reporting Generate monthly expense reports: ```javascript theme={null} const currentMonth = new Date().toISOString().slice(0, 7); // YYYY-MM const exportUrl = `https://api.contazen.ro/v1/expenses/export?format=csv&start_date=${currentMonth}-01&end_date=${currentMonth}-31`; ``` ### Audit Preparation Export all expenses for a specific period for auditing: ```javascript theme={null} const auditExport = 'https://api.contazen.ro/v1/expenses/export?format=csv&start_date=2024-01-01&end_date=2024-12-31&sort=date&order=asc'; ``` ### Category Analysis Export expenses by category for detailed analysis: ```javascript theme={null} const categoryExport = 'https://api.contazen.ro/v1/expenses/export?format=csv&category_id=1'; ``` ```bash cURL theme={null} # Download CSV export with filtering curl -X GET "https://api.contazen.ro/v1/expenses/export?format=csv&start_date=2024-01-01&end_date=2024-01-31&status=paid" \ -H "Authorization: Bearer YOUR_API_KEY" \ --output expenses_january_2024.csv # Download all unpaid expenses curl -X GET "https://api.contazen.ro/v1/expenses/export?format=csv&status=unpaid" \ -H "Authorization: Bearer YOUR_API_KEY" \ --output unpaid_expenses.csv ``` ```javascript JavaScript theme={null} const exportExpenses = async (filters = {}) => { // Build query parameters const params = new URLSearchParams({ format: 'csv', ...filters }); const response = await fetch(`https://api.contazen.ro/v1/expenses/export?${params}`, { method: 'GET', headers: { 'Authorization': 'Bearer YOUR_API_KEY' } }); if (response.ok) { // Get filename from Content-Disposition header const contentDisposition = response.headers.get('Content-Disposition'); const filename = contentDisposition ? contentDisposition.split('filename=')[1].replace(/"/g, '') : 'expenses_export.csv'; // Get the CSV content const csvContent = await response.text(); // Create download link (browser environment) const blob = new Blob([csvContent], { type: 'text/csv' }); const url = window.URL.createObjectURL(blob); const a = document.createElement('a'); a.href = url; a.download = filename; a.click(); window.URL.revokeObjectURL(url); } else { const error = await response.json(); throw new Error(error.error.message); } }; // Usage examples exportExpenses({ start_date: '2024-01-01', end_date: '2024-01-31' }); exportExpenses({ status: 'unpaid', currency: 'RON' }); exportExpenses({ supplier_id: 'sup_abc123' }); ``` ```php PHP theme={null} $filters = [ 'format' => 'csv', 'start_date' => '2024-01-01', 'end_date' => '2024-01-31', 'status' => 'paid' ]; $url = 'https://api.contazen.ro/v1/expenses/export?' . http_build_query($filters); $curl = curl_init(); curl_setopt_array($curl, [ CURLOPT_URL => $url, CURLOPT_RETURNTRANSFER => true, CURLOPT_HTTPHEADER => [ 'Authorization: Bearer YOUR_API_KEY' ] ]); $response = curl_exec($curl); $httpCode = curl_getinfo($curl, CURLINFO_HTTP_CODE); $contentType = curl_getinfo($curl, CURLINFO_CONTENT_TYPE); if ($httpCode == 200 && strpos($contentType, 'text/csv') !== false) { // Success - save CSV file $filename = 'expenses_export_' . date('Y-m-d') . '.csv'; file_put_contents($filename, $response); echo "Export saved to: {$filename}"; } else { // Error response $error = json_decode($response, true); echo "Export failed: " . $error['error']['message']; } curl_close($curl); ``` ```csv CSV File Content theme={null} Reference,Date,Due Date,Supplier,Category,Description,Amount,Currency,VAT %,Amount without VAT,VAT Amount,Status,Payment Date,Payment Type INV-2024-001,2024-01-15,2024-02-15,Office Depot SRL,Office Expenses,Office supplies purchase,238.00,RON,19,200.00,38.00,Paid,2024-01-20,Bank transfer INV-2024-002,2024-01-16,2024-02-16,Marketing Pro,Marketing & Advertising,Social media campaign,1190.00,RON,19,1000.00,190.00,Unpaid,, EXP-2024-003,2024-01-17,2024-02-17,Travel Agency,Travel & Transportation,Business trip accommodation,595.00,RON,9,545.87,49.13,Paid,2024-01-25,Card ``` ```json Error Response (Invalid Format) theme={null} { "success": false, "error": { "message": "Invalid format. Use csv or pdf", "type": "invalid_request_error", "code": "invalid_format" } } ``` ```json Error Response (PDF Not Implemented) theme={null} { "success": false, "error": { "message": "PDF export not yet implemented", "type": "not_implemented", "code": "feature_not_available" } } ``` ## Best Practices ### File Management 1. **Naming conventions**: Use descriptive filenames with dates 2. **Storage**: Store exported files securely with appropriate access controls 3. **Cleanup**: Regularly clean up old export files to save storage space ### Data Integrity 1. **Filtering**: Use appropriate filters to export only needed data 2. **Sorting**: Sort by relevant fields for easier analysis 3. **Validation**: Verify exported data matches your expectations ### Performance Considerations 1. **Large exports**: For very large datasets, consider using date ranges to split exports 2. **Scheduling**: Schedule exports during off-peak hours for better performance 3. **Monitoring**: Monitor export file sizes and processing times ### Security 1. **Access control**: Ensure only authorized users can export sensitive financial data 2. **Audit logging**: Log export activities for security auditing 3. **Data handling**: Follow your organization's data protection policies for exported files ### Integration Tips 1. **Automation**: Automate regular exports for recurring reporting needs 2. **File processing**: Build workflows to automatically process exported CSV files 3. **Error handling**: Implement proper error handling for failed exports 4. **Notifications**: Set up notifications for successful or failed export operations ## OpenAPI ````yaml GET /expenses/export openapi: 3.1.0 info: title: Contazen API version: 1.2.0 description: > Build powerful integrations with the Contazen invoicing platform. The Contazen API is organized around REST, has predictable resource-oriented URLs, accepts JSON request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. ## Authentication The API uses Bearer token authentication. Include your API key in the Authorization header. ### Getting your API Key 1. Log in to your Contazen account 2. Navigate to Settings > API 3. Generate or copy your API key (starts with `sk_live_` for production or `sk_test_` for testing) ### Using the API Key Include your API key in the Authorization header: ``` Authorization: Bearer sk_live_YOUR_API_KEY ``` ### Example Request with cURL ```bash curl --request GET \ --url https://api.contazen.ro/v1/clients \ --header 'Authorization: Bearer sk_live_YOUR_API_KEY' \ --header 'Accept: application/json' ``` ## Rate Limiting - 1000 requests per hour per API key - 100 create operations per minute per API key Rate limit information is included in response headers: - `X-RateLimit-Limit`: Maximum requests allowed - `X-RateLimit-Remaining`: Requests remaining - `X-RateLimit-Reset`: Reset time (Unix timestamp) ## Pagination All list endpoints return paginated results with the following format: ```json { "success": true, "data": { "object": "list", "data": [...], "has_more": true, "total": 245, "page": 1, "per_page": 50, "total_pages": 5 }, "meta": { "version": "v1", "request_id": "req_1a2b3c4d", "response_time": "23.45ms" } } ``` ## Multi-Work-Point Access API keys belong to a specific work point but can access data from all work points within the same parent company. ## Error Handling The API uses conventional HTTP response codes to indicate success or failure. In general: 2xx codes indicate success, 4xx codes indicate an error due to the information provided, and 5xx codes indicate an error with Contazen's servers. ## Expanding Nested Objects Many endpoints support the `expand` parameter to include related objects in the response. This follows the Stripe API pattern. For example: - `expand[]=lines` - Include invoice line items - `expand[]=payments` - Include payment records - `expand[]=client` - Include full client object ## Localization The API supports multiple languages through: - `locale` query parameter (en, ro) - `Accept-Language` header - Default: English contact: name: Contazen Support email: support@contazen.ro url: https://contazen.ro license: name: Proprietary url: https://www.contazen.ro/termeni-si-conditii-de-utilizare/ servers: - url: https://api.contazen.ro/v1 description: Production API server security: - bearerAuth: [] tags: - name: Authentication description: API authentication and test endpoints - name: Clients description: Manage your customers (B2B and B2C) - name: Invoices description: Create and manage invoices, proformas, and receipts - name: Products description: Manage your product and service catalog - name: Expenses description: Track and manage business expenses - name: Expense Categories description: Organize expenses with categories - name: Suppliers description: Manage expense suppliers and vendors - name: Settings description: API settings and configuration - name: Payments description: Payments received against invoices - name: Receipts description: Cash receipts (chitanțe) — standalone or paired with an invoice - name: Company Lookup description: Romanian company lookup (ANAF / VIES) - name: Invoice Series description: Manage invoice numbering series - name: Bank Accounts description: Manage IBAN bank accounts - name: E-Factura description: Romanian e-invoicing status and configuration - name: Supplier Bills description: Supplier invoices imported from the ANAF SPV inbox - name: VAT Rates description: Firm-scoped custom VAT rates on top of the Romanian catalog - name: Currencies description: Currencies enabled for the firm's bill templates - name: Languages description: Languages enabled for the firm's bill templates - name: Conta description: | Public ANAF data for the firm's CUI: fiscal profile (TVA scope, RTVAI, split TVA, status, e-Factura registration, CAEN) and annual balance sheets (cifra de afaceri, profit, capitaluri, datorii, salariați). Powered by the public ANAF webservices (no OAuth required for these endpoints). The data is cached locally and refreshed on demand via the `/sync` actions. paths: /expenses/export: get: tags: - Expenses summary: Export expenses to CSV description: Export expenses to CSV format with optional filters operationId: exportExpenses parameters: - name: supplier_id in: query schema: type: string description: Filter by supplier CzUid - name: category_id in: query schema: type: integer description: Filter by category ID - name: start_date in: query schema: type: string format: date description: Start date (Y-m-d format) - name: end_date in: query schema: type: string format: date description: End date (Y-m-d format) - name: status in: query schema: type: string enum: - paid - unpaid - overdue description: Filter by payment status responses: '200': description: CSV export file content: text/csv: schema: type: string format: binary examples: csv_export: summary: CSV file with expense data description: >- Returns a CSV file with all expense data matching the filters '400': $ref: '#/components/responses/ValidationError' '401': $ref: '#/components/responses/UnauthorizedError' components: responses: ValidationError: description: Request validation failed content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' UnauthorizedError: description: API key is missing or invalid content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' schemas: ErrorResponse: type: object required: - success - error properties: success: type: boolean default: false error: type: object required: - message - type - code properties: message: type: string description: Human-readable error message type: type: string enum: - api_error - authentication_error - invalid_request_error - rate_limit_error - permission_error - validation_error code: type: string description: Machine-readable error code param: type: string description: The parameter that caused the error doc_url: type: string format: uri description: URL to relevant documentation meta: $ref: '#/components/schemas/ResponseMeta' ResponseMeta: type: object properties: version: type: string default: v1 request_id: type: string format: uuid description: Unique request identifier for debugging response_time: type: string example: 23.45ms securitySchemes: bearerAuth: type: http scheme: bearer description: Use your API key (sk_live_xxx or sk_test_xxx) ````