Monitor API availability and service status. Use these endpoints to verify connectivity and check if the API is operational.
DualEntry Public API (1.0.0)
Request
Retrieve a paginated list of paper checks with filtering options.
Paper checks represent physical checks that can be printed for vendor payments, direct expenses, vendor prepayments, or customer refunds.
Common use cases:
- List all queued checks ready to print:
?record_status=not_printed - List checks for a specific vendor:
?vendor_id=123 - List checks within a date range:
?start_date=2024-01-01&end_date=2024-01-31
- Production environmenthttps://api.dualentry.io/public/v1/paper-checks/
- Development environment (for testing)https://api-dev.dualentry.io/public/v1/paper-checks/
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.dualentry.io/public/v1/paper-checks/?id=0&record_status=string&company_id=0&transaction_type=direct_expense&vendor_id=0&customer_id=0&account_id=0&start_date=2019-08-24&end_date=2019-08-24&limit=100&offset=0'OK
Date when the paper check was created (returned as date only)
Date of the underlying transaction
Type of the source record (e.g., 'direct_expense', 'vendor_payment', 'customer_refund')
ID of the source record (e.g., the VendorPayment ID)
Number of the source record (e.g., vendor payment number)
The check number printed on the physical check
Name of the company issuing the check
Memo or description for the check
Amount of the check
Amount of the check
ISO 4217 currency code for the check amount
Number of the bank account the check is drawn from
Name of the bank account the check is drawn from
Name of the payee (vendor or customer receiving the check)
ID of the customer if this is a customer refund check
Name of the customer if this is a customer refund check
ID of the vendor if this is a vendor payment check
Name of the vendor if this is a vendor payment check
{ "items": [ { … } ], "count": 0 }
Request
Create and immediately print a paper check for a transaction.
This endpoint creates a paper check record and generates the PDF in a single operation. The check is immediately marked as PRINTED.
When to use:
- When you need to print a single check right away
- For on-demand check printing workflows
Alternative: Use POST /print-later/ to queue checks for batch printing.
Supported transaction types:
- Direct expenses
- Vendor payments
- Vendor prepayments
- Customer refunds
Returns: The created paper check details along with the PDF content encoded in base64.
ID of the transaction to print a check for. Must be a printable transaction type (direct expense, vendor payment, vendor prepayment, or customer refund).
- Production environmenthttps://api.dualentry.io/public/v1/paper-checks/print-now/
- Development environment (for testing)https://api-dev.dualentry.io/public/v1/paper-checks/print-now/
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api.dualentry.io/public/v1/paper-checks/print-now/ \
-H 'Content-Type: application/json' \
-d '{
"transaction_id": 12345,
"template_id": 1
}'OK
The created paper check details
Date when the paper check was created (returned as date only)
Date of the underlying transaction
Type of the source record (e.g., 'direct_expense', 'vendor_payment', 'customer_refund')
ID of the source record (e.g., the VendorPayment ID)
Number of the source record (e.g., vendor payment number)
The check number printed on the physical check
ID of the company issuing the check
Name of the company issuing the check
Memo or description for the check
Amount of the check
Amount of the check
ISO 4217 currency code for the check amount
Number of the bank account the check is drawn from
Name of the bank account the check is drawn from
Name of the payee (vendor or customer receiving the check)
ID of the customer if this is a customer refund check
Name of the customer if this is a customer refund check
ID of the vendor if this is a vendor payment check
Name of the vendor if this is a vendor payment check
{ "paper_check": { "id": 12345, "created_at": "2024-01-15", "transaction_date": "2024-01-15", "source_record_type": "direct_expense", "source_record_id": 789, "source_record_number": 1001, "check_number": "10542", "company_id": 456, "company_name": "Acme Corporation", "memo": "Payment for Invoice #1234", "amount": "1500.00", "currency_iso_4217_code": "AED", "account_number": 321, "account_name": "Operating Account", "payee_name": "ABC Suppliers Inc.", "customer_id": 567, "customer_name": "John Smith", "vendor_id": 890, "vendor_name": "ABC Suppliers Inc.", "record_status": "printed" }, "pdf_content": "string" }
Request
Create paper checks for transactions that will be printed later in a batch.
This endpoint creates paper check records with status NOT_PRINTED. These checks can then be printed together using the PUT /print-batch/ endpoint.
When to use:
- When you want to accumulate checks before printing
- For batch check printing workflows
- When check numbers need to be assigned in sequence
Alternative: Use POST /print-now/ to print a single check immediately.
Workflow:
- Queue checks:
POST /print-later/with transaction IDs - Review queued checks:
GET /paper-checks/?record_status=not_printed - Print batch:
PUT /print-batch/with paper check IDs
Returns: List of created paper checks with status 'not_printed'.
- Production environmenthttps://api.dualentry.io/public/v1/paper-checks/print-later/
- Development environment (for testing)https://api-dev.dualentry.io/public/v1/paper-checks/print-later/
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api.dualentry.io/public/v1/paper-checks/print-later/ \
-H 'Content-Type: application/json' \
-d '{
"transaction_ids": [
12345,
12346,
12347
]
}'OK
Date when the paper check was created (returned as date only)
Date of the underlying transaction
Type of the source record (e.g., 'direct_expense', 'vendor_payment', 'customer_refund')
ID of the source record (e.g., the VendorPayment ID)
Number of the source record (e.g., vendor payment number)
The check number printed on the physical check
Name of the company issuing the check
Amount of the check
Amount of the check
ISO 4217 currency code for the check amount
Number of the bank account the check is drawn from
Name of the bank account the check is drawn from
Name of the payee (vendor or customer receiving the check)
ID of the customer if this is a customer refund check
Name of the customer if this is a customer refund check
Name of the vendor if this is a vendor payment check
Status of the paper check: 'not_printed' (queued), 'printed', or 'archived'
[ { "id": 12345, "created_at": "2024-01-15", "transaction_date": "2024-01-15", "source_record_type": "direct_expense", "source_record_id": 789, "source_record_number": 1001, "check_number": "10542", "company_id": 456, "company_name": "Acme Corporation", "memo": "Payment for Invoice #1234", "amount": "1500.00", "currency_iso_4217_code": "AED", "account_number": 321, "account_name": "Operating Account", "payee_name": "ABC Suppliers Inc.", "customer_id": 567, "customer_name": "John Smith", "vendor_id": 890, "vendor_name": "ABC Suppliers Inc.", "record_status": "printed" } ]