Makini
v4 (Latest)
  • v4 (Latest)
  • v3 (Legacy)
User Guide
API ReferenceMCPPlatforms
User Guide
API ReferenceMCPPlatforms
Website
v4 (Latest)
  • v4 (Latest)
  • v3 (Legacy)
v4 (Latest)
  • v4 (Latest)
  • v3 (Legacy)
  1. Working with the API
  • Getting Started
    • On-premise systems
    • Authentication
    • Testing with API Tools
    • Account setup
    • Connection Credits
  • Core Concepts
    • Connections
    • Unified Data Model
    • Custom mappings
    • Data mappings
    • Sync schedules and history
  • Admin API
  • Account & Team
    • Team access and SSO
  • Makini Link
    • Embedded connection settings
    • Launching Makini Link
    • Magic links
  • Management API
    • Management API authentication
    • Managing connections
    • Managing your application
  • Webhooks
    • Signatures and retries
    • Webhook events
  • Working with the API
    • Access tokens
    • Errors
    • Filtering
    • Makini Query Language
    • Raw data and passthrough
    • Reading data
    • Relations and expand
    • Writing data
  1. Working with the API

Relations and expand

Records in a connected system point at each other: a work order at its asset, a purchase order line at its order. Makini returns every such relation as a small link object, and one expand parameter swaps it for the full related record, so you get both in a single request.
Request
Response
The expanded asset is the full record, while location, and the asset's own location, stay links.

Read a link object#

{
  "id": "0192f3…",
  "_idValue": "4711",
  "_displayValue": "Pump P-101",
  "rel": "assets",
  "href": "https://…/v4/assets/0192f3…"
}
id is the related record's Makini id, and href is its single-record endpoint.
rel is the related entity's endpoint name.
A relation with no counterpart is null.

Expand relations#

expand takes a comma-separated list of relation names, such as ?expand=asset,location. Each named relation is returned as the full related record instead of a link. The relations each endpoint can expand are listed on its expand parameter, and an unknown name is a 400.
Expansion is one level deep
In an expanded record, its own relations stay links. In the API Reference that expanded shape is the related entity's …Core schema, filed under its group's Expanded folder.
If the related record isn't available (it was deleted, or hasn't synced yet), an expanded relation stays a link. Its href then answers 404.

Work with many-relations#

Some relations hold several records, such as a work order's assignees. They are arrays of links, [] when empty and never null, and a member is never null. With expand, each member becomes the full related record.

Handle polymorphic relations#

Some relations can point at more than one entity. A comment's target can be a work order, an asset, an invoice and more. The link's rel tells you which entity it points at.
When expanded, the related record carries an extra _entity field naming its entity. Its schema is <Entity>CoreTagged, the …Core schema plus _entity.

Reference#

Relations in the schemas

Next steps#

Reading data
Lists, single records and the record envelope.
Filtering
Narrow a list to the records you need.
Modified at 2026-10-16 14:20:56
Previous
Reading data
Next
Writing data
Built with