Home / Product / Resource APIs

Build product experiences

Give every product surface a dependable way to work with data.

Once a record exists in your model, Daptin gives web apps, mobile apps, internal tools, and integrations a consistent way to read it, change it, and follow its relationships.

See what it changes Technical guide ↗

Resource APIs in a product

Choose the recordA project, customer, order, or article

Ask for exactly what the screen needsFilter, sort, page, and include relationships

Make a permitted changeCreate, update, connect, or remove

The API follows the product model

01Generate list, search, sort, page, create, update, delete, and relationship APIs from the model.Common data operations arrive with the model.

02Give clients a predictable contractThe same resource patterns work across the application.

03Keep access in the request pathEvery operation meets the relevant table and record rules.

Why it matters

Use generated list, search, sort, page, create, update, delete, and relationship APIs for each new screen.

Product teams often wait for bespoke backend routes before they can list records, open a detail view, save an edit, or connect two things. Those endpoints repeat the same filtering, pagination, relationship, and access work.

Daptin exposes modeled resources through a consistent JSON:API interface. A client can list, search, sort, page through, create, update, delete, and follow relationships.

When the product needs behavior beyond ordinary data changes, a named action sits beside the resource API. Routine access stays predictable; meaningful operations get a clear product name.

Build more screens from the same foundation

Web, mobile, and internal tools can share one resource contract.

Make relationships usable

Fetch related records through generated relationships and consistent resource representations.

Keep generated resource APIs behind the same record permissions and validation rules.

Authentication, table access, record ownership, and relationship rules remain part of the request.

How it fits

Part of one connected backend.

Resource APIs does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Model

A resource and its relationships define the available data shape.

Step 2Request

The client filters, sorts, pages, or includes connected records.

Step 3Authorize

Daptin establishes the caller and applies access rules.

Step 4Respond

The API returns public record identities and relationship links.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Customer self-service

Let people view and update only their own profile, requests, and files.

Operations dashboard

Filter active work, include its owner, and page through a large history.

Partner integration

Give integrations generated resource APIs with stable fields, relationships, pagination, and permission checks.

Connected by design

Give every screen and integration the same resource contract and permission checks.

These capabilities share the same application context, so each one makes resource apis more useful.

Know the boundary

What Daptin leaves in your hands.

Use generated APIs for routine record operations and named actions for product-specific behavior. Complex decisions, side effects, and multi-step workflows belong in actions or a purpose-built service.

Understand the operating responsibility →

Build from one foundation

Every modeled resource gets pagination, filtering, relationships, writes, and record-level permission checks.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities