Skip to main content
Connect your company’s Reltio tenant to Athena so each member can search and read profiles, follow their relationships, review the potential duplicates your match rules suggest, and create or update profiles as their own Reltio user. Your Reltio roles and data-access rules apply unchanged. Athena sees exactly what you can see in Reltio, nothing is shared through an integration user, and every profile Athena creates or updates is recorded under your name.
Members can connect once Athena Intelligence has registered a Reltio client for your tenant. Your Reltio administrator creates the client in the Reltio Console (step 1). Members sign in to Reltio through your company’s single sign-on.

​
Step 1 — Prepare your tenant (Reltio admin)

  1. In the Reltio Console, open Client Credentials and add a new client with the Authorization Code grant type. Copy its client ID and client secret.
  2. Ask Reltio Support to register Athena’s redirect URI for the client:
    For private or VPC deployments, replace api.athenaintel.com with your environment’s Athena API host.
  3. Send the client ID and secret to Athena Intelligence through a secure channel, together with:
    • the tenant’s environment (its host, such as test.reltio.com);
    • its tenant ID;
    • the tenant your members’ single sign-on goes through.
If your tenant accepts API calls only from allowlisted IP addresses, also allow Athena’s outbound addresses (ask Athena Intelligence for them), or Reltio refuses every request.

​
Step 2 — Athena registers the client for your workspace

Athena Intelligence adds a reltio_direct integration for your workspace. It holds the client ID, the encrypted client secret and the tenant’s coordinates. It can also hold a display name for the tenant and the Reltio source Athena’s writes go under. Secrets are encrypted at rest and never returned to the browser. Development, test and production tenants each get their own integration. Once one is saved, the Reltio card on the Integrations page is available to every member. Until then, the card says the integration isn’t set up for your workspace yet.

​
Step 3 — Connect your account (each member)

  1. Navigate to Integrations and click Connect Reltio on the Reltio card, under Data Warehousing & BI.
  2. Your company’s sign-in page opens in a popup. Sign in, and Athena confirms the connection with your Reltio username.
  3. If your workspace has more than one Reltio tenant registered, pick one before connecting. To add another tenant later, click Connect another Reltio tenant.

​
What Athena can do

Once connected, the Reltio toolkit gives agents these tools. A few behaviors to know:
  • Plain-language requests work. Ask “find Acme’s organization profile and its addresses” or “are there duplicates of this customer”. Athena can describe a type first to get attribute names right.
  • Search can trail by seconds. Search reads Reltio’s search index, which can lag a change by a few seconds. Reading a profile by its ID always shows its current values. A large result comes back in pages, and Athena reads further pages only when it needs them.
  • Operational values. Athena shows each attribute’s operational value, the one your survivorship rules picked among your sources.
  • Updates change only Athena’s values. An update changes only the attributes you approve, and only the values Athena’s own source holds. Other sources’ values stay as they are, and Athena says when your survivorship rules kept another source’s value. Athena never replaces a whole profile, and it has no delete or merge tool.
  • Data change requests. If you may only suggest changes, Reltio files a data change request for a data steward instead of writing, and Athena tells you so.
  • Several tenants. With more than one tenant connected, name the tenant you mean. Athena can list your connected tenants.
  • Reads need no approval. Read tools run without a prompt in chat and in scheduled agent runs that act as you. Write tools are available only in chat, where you can approve them. An automation’s own identity holds no Reltio connection, so automation steps cannot call Reltio.

​
Use Reltio from a computer

On a computer with your Reltio connection attached under Connected Catalogs:
  • RELTIO_API_URL holds your tenant’s API base, https://<environment>.reltio.com/reltio/api/<tenant ID>.
  • RELTIO_TENANT_ID holds the tenant ID.
  • athena-catalog-token reltio_direct prints a short-lived access token for your connection.
With more than one Reltio tenant attached, RELTIO_API_URL and RELTIO_TENANT_ID describe the first one. For another tenant, pass its catalog’s asset ID to athena-catalog-token and call that tenant’s own API base, https://<environment>.reltio.com/reltio/api/<tenant ID>. Ask Athena to list your Reltio tenants to see each one’s environment and ID.
The computer acts as you, so anyone you share it with can use your Reltio access from it: attach your connection only to a computer you don’t share.

​
Token lifecycle & troubleshooting

  • Everything is per-user. Results always reflect your Reltio access, and every change is attributed to you.
  • “Reconnect Reltio.” An access token lasts about an hour and Athena renews it. A connection ends when its refresh token expires after 28 days without use, when it is revoked, or when your identity provider ends your session. Reconnecting from the Integrations page fixes it.
  • The sign-in page refuses you. Members who sign in to Reltio with a username and password, without single sign-on, cannot connect yet.
  • “Cannot open tenant.” Your Reltio user has no access to the tenant your workspace registered. Ask your Reltio administrator.
  • “Refused this as you.” Your Reltio roles or data-access rules do not allow the request, or the tenant accepts calls only from allowlisted IP addresses. Ask your Reltio administrator; Athena cannot widen your access.
  • Rate limits. When Reltio throttles requests, Athena says how long to wait instead of retrying in a loop.

​
Disconnecting

Open the Reltio connection in Athena and click Disconnect. Athena asks Reltio to revoke your tokens, then removes them from Athena. If Reltio can’t be reached, Athena still disconnects you, but the tokens may stay valid in Reltio until they expire; ask your Reltio administrator to revoke them if you need that confirmed. Other tenants you connected stay connected.