Fresh 2026

Writing Data Flow

The meta-first pattern for safely creating and updating records across integrations that each expect different fields.

Different platforms require different fields for the same write. Instead of hardcoding per-integration logic, you ask Merge what a given Linked Account needs via the /meta endpoint, then submit the write.

flowchart TD
    A[Need to create a record] --> B[GET /model/meta]
    B --> C[Read required + optional fields]
    C --> D[Build request body to match meta]
    D --> E[POST /model]
    E --> F{Validation}
    F -- Pass --> G[Record created at source]
    F -- Fail --> H[Inspect errors, fix body]
    H --> D
    G --> I[Optional: nested + related writes in one call]

Steps

1. Call /meta. Before a POST or PATCH, call the model's /meta endpoint for that Linked Account. It returns the exact required and optional fields for that integration. See Programmatic Writes with /meta.
2. Build the body programmatically. Populate your request from the meta response so it adapts to whatever the integration demands. No per-platform branching in your code.
3. Submit the write. POST to create or PATCH to update. See Making Writes.
4. Use nested writes when relations exist. Create a record and its related records in a single request. See Related and Nested Writes.
5. Test in Postman first. Validate the shape before wiring it into your app. See Postman Testing Guide.

Key idea

The /meta endpoint is what makes one code path work across every integration in a category. The required fields vary by platform and by Linked Account; meta tells you the truth at request time.