Batch Imports

Submit source data through the normal product API batch endpoints. There is no separate ingest surface: batches use the same host, credentials, validation, locks, and dry-run behavior as every other operation.

POST https://api.vrplatform.app/reservations/batch
x-api-key: <team-api-key>
x-team-id: <team-uuid>

Available Batch Operations

• Reservations
• Contacts
• Listings
• Transactions
• Bank accounts
• Bank records

The exact request schema and per-entity fields live on each generated page.

Identity and Idempotency

Send a stable uniqueRef per item. Resubmitting the same uniqueRef updates the existing record instead of creating a duplicate, so to retry safely, resend the batch. The rules for stable identity, conflict handling, and irreversible side effects live in Integration-sourced data.

Outcomes

A batch responds with per-item results and structured issues:

{
  "data": [
    {
      "id": "11111111-1111-4111-8111-111111111111",
      "uniqueRef": "pms-res-1042",
      "sourceId": null
    }
  ],
  "issues": []
}

Process data and issues item by item; a batch is not all-or-nothing. Validate risky batches first with dry run where the operation declares the dryRun parameter.

Related

• Connections for continuously synced sources
• Historical statements and historical journal entries for pre-go-live history