EPepilot
erp

processErpUpdatesEventsV2

Changed on

Handles updates from ERP systems using integration_id directly. This is the v2 version that simplifies the API by accepting integration_id instead of app_id and component_id.

Requires the integration:ingest grant on integration_id; the wildcard grants integration:* and * (the owner role) include it. Without it the request is refused with 403 before any event is processed. Being rolled out: until a stage enforces it, a missing grant is logged and the request is still processed.

post/v2/erp/updates/events

Request

  • Base URL
    https://integration-toolkit.sls.epilot.io
  • URL
    https://integration-toolkit.sls.epilot.io/v2/erp/updates/events
  • Auth
    HTTP bearer

Request body

integration_idstring uuid required

UUID that identifies the integration configuration to use

correlation_idstring

Optional ID that identifies the specific request for debugging purposes

Example request

{
  "events": [
    {
      "deduplication_id": "evt-2025-05-01-12345-create-bp",
      "correlation_id": "bp-8f3a2c-7d4e-4b1a-9c2f-1e6d5a4b3c21"
    }
  ]
}

Response

Some events failed to process

correlation_idstring

The request's correlation id, echoed, or the one generated for it when the caller omitted it. This is the id to pass to GET /v3/erp/updates/events?correlation_id=... to wait for these events. v3 and v2 generate one when the request has none, so they always return it, except that v2 omits it for an empty correlation_id. v1 never generates one: it echoes a non-empty meta.correlation_id and otherwise omits the field.

Changes

  • ef6bbb0d5a31Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

  • 53e2cdce2751Revision changes
    • info

      added the non-success response with the status