Integrations / Cleo
Cleo
Cleo is an EDI and integration platform for B2B communications and supply chain management
API key
Indexes
Actions
What Telara does
Capability matrix
Before you connect
Prerequisites
A Cleo account you can administer.
A role that can open the developer or API settings and issue a key.
Vendor setup
Get the credential
1
Open API keys
Sign in to Cleo. Open Settings → API (or the developer console your tenant uses).
2
Create a key
Click Create API Key. Name it for Telara. Copy it immediately if Cleo shows it once.
3
Paste in Telara
Settings → Integrations → Cleo. Paste the key into the field Telara shows.
In Telara
Connect in Telara
API key
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
Fields Telara asks for
- API key
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Document | Partial — not every record the vendor holds is synced |
| Transfer | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Document | Up to 1 day | Removed records disappear on the next full sync |
| Transfer | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Document, Transfer.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
A sandbox key does not cover production trading partners.
If Connect fails, confirm you copied an API key and not an SSO session cookie.