Intelex

Built, not certified Built and tested against recorded and synthetic responses (version 1.0.0, 10 November 2026). Not yet run against the vendor's sandbox or a client environment.

Reads incidents, audits, findings and actions from the Intelex objects you name, read-only, inside your deployment, with reporters left out.

At a glance

Collector	Intelex, version 1.0.0
Reads	Intelex Technologies: Intelex REST API (v2) (the vendor's documentation)
Family	Aviation
Kind	Quality
Ways to connect	Access token
Scopes	Read:
Read only	Yes
Vendor's API can move money	No
Personal data	Identity, Contact
Hosts it may contact	Only the hosts on your deployment's allow-list (*: the host is the one you give it)
Vendor API versions	Intelex REST API v2 (/api/v2/object)
Lowest engine version	0.46.0

What it reads

• For each object you name (objects, such as IncidentsObject; each system’s names are listed in Intelex’s System Administration): its records modified since the last run (on the first run, within the last days_back days: 1 to 3650, default 365), through GET /api/v2/object/{Object} with $filter=DateModified ge ....
• One record per Intelex Id, keyed <object>/<id>, with its DateModified.
• Pages of up to 500 (page_size) follow @odata.nextLink.

How to connect

1. Create a dedicated integration user in Intelex, make an API key for it, and tell your Intelex Customer Success Manager about the integration first (Intelex asks this).
2. In LightHouse, open Setup and admin, Connectors, choose Intelex, and leave the access level at Read.
3. Name base_url (your Intelex system, https) and the objects.
4. Paste the API key. Your browser seals it to your deployment, which hands it to the collector as INTELEX_API_KEY.

Permissions

• GET only, with Authorization: ApiKey <key>. The integration user’s rights in Intelex are the permission: give it read access to the objects you name.
• Intelex asks that its API not be driven by autonomous agents. This is a scheduled, read-only sync on a dedicated integration user, not an agent; onboarding includes the conversation with your Customer Success Manager.
• Your deployment refuses to store this credential at read and write.

Limits

• Intelex limits a tenant to 20 reads a second and 20,000 a day, shared with every other use of the tenant, and answers 429 with Retry-After beyond them. The default pace is two reads a second (delay_s 0.5).
• Incremental by DateModified, from the previous run.
• An object is read up to max_pages pages (400); more fails the run.
• A @odata.nextLink to another host is refused.

Data handling

• Records are read and indexed inside your deployment. LightHouse receives ids, hashes and counts, never an incident or a reporter.
• Reporters are protected by default: reporters’ names, who submitted or created a record, and everyone’s email, phone and contact details are left out of every record before it is written, as are travel document numbers and dates of birth. Just culture and data protection both need a reporter kept from anyone who does not need them. Names are matched whatever the case, spacing, _ or -, so reporterName also catches an export’s Reporter Name.
• exclude_fields adds paths (for example **.contact); keep_fields takes a default back by its exact name, and that choice is your record of the decision. Free-text narratives are indexed as written and may still name people: add the fields that hold them to exclude_fields.
• Nothing is cached raw, and a failure names the host and the status, never the URL.

Troubleshooting

What you see	What it means	What to do
credential variable 'INTELEX_API_KEY' is not set	The deployment has not been given the key	Connect the credential again
GET host: HTTP 401	Intelex refused the key	Check the key belongs to an active integration user
GET host: HTTP 429	The tenant’s rate limit, after the retries	Read fewer objects, or less often
GET host: a next page on another host was refused	A next link pointed away from your Intelex	Report it to us; nothing was followed
intelex: more than 400 pages of X	An object has more records than max_pages allows	Narrow days_back, or raise max_pages
base_url is the client's Intelex system, https	base_url is not https	Use the https address
objects are Intelex object system names, at least one	No object, or a name with a space	Use the object’s system name
page_size is 1 to 500 and days_back 1 to 3650	A setting is out of range	Correct it

Certification

Each entry is a run by Atlantic Agentic Labs, newest first. Only a run against the vendor’s sandbox or a client environment certifies a collector; a certification lasts six months, or less if the vendor publishes an API version the collector does not list. See How collectors are certified.

Date	Collector	Engine	Vendor API	Method	Expires
10 November 2026	1.0.0	0.47.0	Intelex REST API v2	Fixtures only: built, not certified	Not applicable

Security posture

From the collector’s last scan on the default branch. What each line means, and what blocks a release: Security posture.

Last scanned	10 November 2026
Critical findings	0
High findings	0
Medium findings	0
Low findings	0
Info findings	0
Release blocked	No
Network allow-list check	Pass
Read-only behavioural test	Pass
SBOM (CycloneDX)	Produced
Dependency licences	Pass
Scanners	bandit 1.9.4, semgrep 1.181.1, pip-audit 2.10.1, osv-scanner 2.7.0, cyclonedx-py 7.5.0, pip-licenses 5.5.5, gitleaks repository job aal-secrets, hosts_check tools/hosts_check.py, read-only test pytest -m read_only