Data Ingestion

Current Status

Raw ingest is publicly hosted, but it is not a provider API key surface.

Current auth requirement:

Authorization: M2M <jwt>

Required scope:

• ingest:submit

Host

• https://ingest.edge.vrplatform.app

Routes

• POST /v1/ingest/reservations
• POST /v1/ingest/listings
• POST /v1/ingest/transactions
• POST /v1/ingest/payments
• POST /v1/ingest/bank-accounts
• POST /v1/ingest/bank-records
• POST /v1/ingest/contacts

Exact Outer Request Shape

All ingest routes use the same outer envelope.

{
  "tenantId": "uuid",
  "connectionId": "uuid",
  "triggerType": "manual",
  "requestedScope": {},
  "bootstrapFromLegacySource": true,
  "writeLegacySource": true,
  "items": [
    {
      "remoteId": "source-123",
      "payload": {},
      "sourceLastWebhookAt": "2026-04-01T12:00:00.000Z",
      "description": "optional",
      "status": "optional",
      "date": "optional",
      "reservationId": "uuid"
    }
  ]
}

Exact outer field rules:

• tenantId required, uuid
• connectionId required, uuid
• triggerType required, one of:
  • manual
  • schedule
  • webhook
  • initial
• requestedScope optional object
• bootstrapFromLegacySource optional boolean
• writeLegacySource optional boolean
• items required array with 1 to 5000 items

Exact item field rules:

• remoteId required
• payload required
• sourceLastWebhookAt optional RFC 3339 datetime string
• description optional string
• status optional string
• date optional string
• reservationId optional uuid

The payload schema depends on the entity route.

Successful Response

Successful submission returns a completed ingest run summary.

Current response fields include:

• runId
• targetRealm
• dataRegion
• submitted
• deduped
• enqueued
• skippedJobs
• rawSubmitted
• rawDeduped
• legacyBootstrapMatched
• rawSkippedByWebhook
• rawUploaded
• rawNoop
• legacySourceSubmitted
• legacySourceDeduped
• legacySourceUpserted
• status

Current status is returned as:

• completed

Recommendation

Treat raw ingest as a coordinated backend integration. Do not build partner flows around it unless your contract explicitly includes M2M ingest access.

Related

• Provider Ingest Specification