Before you connect Ordinal
Owners and admins can generate an Ordinal key in traxy. Make sure you have:- access to the traxy workspace you want to connect
- a paid workspace with API access available
- access to the Ordinal account you want to connect
- the Ordinal integration available in traxy
- a place to store the key securely
Generate the Ordinal key in traxy
- Open Integrations.
- Open Ordinal.
- Generate the Ordinal API key.
- Copy the key when traxy shows it.
- Store the key in your team’s secret manager.
Add the key in Ordinal
- Open Ordinal.
- Go to Integrations.
- Open the traxy integration.
- Paste the traxy API key into the traxy integration.
- Save or connect the integration.
What Ordinal can read
Ordinal can access aggregate audience data available through the dedicated traxy key. The integration can use:- workspace audience breakdowns by industry, title, company size, or location
- aggregate audience analytics for LinkedIn posts tracked in your workspace
- post-level engagement counts and sync counts
- audience discovery status for a LinkedIn post
API endpoint docs
Ordinal uses the dedicated traxy key as a bearer token with thehttps://api.traxy.ai/api/v1 base URL.
Use these generated endpoint docs for exact query parameters, request bodies, response schemas, and status responses.
Check readiness
GET /audience-analytics/healthGet post audience
GET /audience-analytics/linkedin-postsRequest audience discovery
POST /audience-analytics/linkedin-posts/find-audienceGet workspace audience
GET /audience-analytics/organizationRequest audience discovery
If you select Audience discovery, Ordinal can request audience discovery for a LinkedIn post that belongs to a profile monitored in your workspace. Audience discovery may return:- ready when aggregate audience data is available
- not requested when discovery has not started
- queued when discovery has been queued
- pending when discovery is running
- already available when traxy already has the aggregate audience data
Keep access safe
Treat the Ordinal API key like a password.- Store the key in a secret manager.
- Do not paste the key into docs, chat, analytics tools, or issue trackers.
- Revoke the key if Ordinal access changes or if you think the key was exposed.