Integration overview

The Omni CLO integration has two independent read workflows and one asynchronous write workflow.

Use the merchant and offer endpoints to synchronize the catalog available to your issuer. Every response is scoped by the issuer represented by the API token.

Issuer server -> GET /api/v1/omni/merchant -> merchant catalog
Issuer server -> GET /api/v1/omni/offer    -> offer catalog

List endpoints return currently relevant catalog data. ID endpoints support reconciliation and historical lookup, including an offer that has ended.

Issuer server -> GET /api/fileUpload -> presigned URL
Issuer server -> PUT presigned URL    -> object storage
Percents      -> validate and process -> automated and human review
Percents      -> signed webhook       -> issuer webhook receiver

Getting the presigned URL only creates an upload slot. Processing does not begin until bytes are uploaded and Percents detects the object. The final webhook is deliberately asynchronous because the workflow can include automated checks and human oversight.

Percents associates the authenticated issuer with one channel-partner network during onboarding. Merchant and offer reads are restricted to that network. Uploaded files are processed using the format and channel network enabled for the same issuer.

An issuer must be explicitly enabled for Omni API reads and for the configured upload format. A valid token alone does not grant either capability.

Credentials, source-IP allowlists, upload enablement, and webhook destinations are configured separately per environment.