API v2

Welcome to Daftra API V2, the next-generation API designed for enhanced flexibility, precision, and control over your business data. This upgraded version introduces advanced filtering capabilities, multi-level data access, and optimized performance for modern integrations.

What's New in V2

Discover the key improvements that make API V2 more powerful, scalable, and data-rich than ever before.

Enhanced Data Retrieval for accessing richer, more detailed, and relational information across entities.

Advanced filtering system with dynamic query capabilities

Multi-level data access (up to 4 levels of related data)

Expanded data scope with comprehensive record relationships

Better data structuring to reduce API calls

Base URL

Understand how to access the API and securely authenticate each request.

Base URL: https://your-domain.daftra.com/v2/api

For more details on how to authenticate your API requests, please refer to the Authentication guide.

Core Endpoints Structure

Learn how to list, fetch, and explore core entities using consistent URL patterns.

List Entities

Retrieve lists of records with a specified level of detail:

Get Single Entity

Fetch a specific record by its ID with level-based detail:

Common Entities

Explore the most commonly used entities, their endpoints, and supported levels.

Entity	Entity Name	Levels	Description
Invoices	`/invoice`	1-4	Sales invoices with items, clients, payments
Clients	`/client`	1-3	Customer records with contacts, addresses
Products	`/product`	1-3	Product catalog with categories, pricing
Orders	`/sales_order`	1-4	Sales orders with items and fulfillment
Payments	`/invoice_payment`	1-3	Payment records with invoices, methods
Expenses	`/expense`	1-3	Expense tracking with categories, receipts
Quotes	`/estimate`	1-4	Price quotes with items, conversions

Multi-Level Data Access

Daftra V2 introduces a 4-level tiered data structure allowing you to control the depth of related data in your responses.

Level Structure

Understand what each level of data includes and when to use it.

Level	Description	Use Case
Level 1	Basic entity data only	Quick listings, minimal data
Level 2	+ Directly related data	Standard operations
Level 3	+ Nested relationships	Detailed views
Level 4	+ Deep context & connections	Full data analysis

Examples

Pagination & Sorting

Manage large datasets with page-based navigation and sorting options.

Pagination Parameters

Sorting

Response with Pagination

{
  "data": [...],
  "meta": {
    "current_page": 1,
    "total": 250,
    "last_page": 5,
    "from": 1,
    "to": 50
  },
  "links": {
    "first": "/.../list/2?page=1",
    "last": "/.../list/2?page=5",
    "prev": null,
    "next": "/.../list/2?page=2"
  }
}

Performance Best Practices

1. Choose Appropriate Levels

Use Level 1 for listings and quick data

Use Level 3-4 only when you need the related data

Higher levels = more processing time

2. Pagination

Always use pagination for large datasets

Use total count to determine if more pages exist

What's New in V2#

Base URL#

Core Endpoints Structure#

List Entities#

Get Single Entity#

Common Entities#

Multi-Level Data Access#

Level Structure#

Examples#

Pagination & Sorting#

Pagination Parameters#

Sorting#

Response with Pagination#

Performance Best Practices#

1. Choose Appropriate Levels#

2. Pagination#

What's New in V2

Base URL

Core Endpoints Structure

List Entities

Get Single Entity

Common Entities

Multi-Level Data Access

Level Structure

Examples

Pagination & Sorting

Pagination Parameters

Sorting

Response with Pagination

Performance Best Practices

1. Choose Appropriate Levels

2. Pagination