The LeanIX connector retrieves data from the LeanIX GraphQL API using a user-defined query. The connector authenticates via the OAuth2 token endpoint and executes the query against the GraphQL endpoint. The following endpoints are used during each connector run:
Endpoint |
Description |
<instance-url>/services/mtm/v1/oauth2/token |
OAuth2 token endpoint. The connector exchanges the API token for a short-lived bearer access token used to authorize GraphQL requests. |
<instance-url>/services/pathfinder/v1/graphql |
LeanIX GraphQL endpoint. The connector submits the configured query and receives the data in JSON format. |
The connector derives the output table structure automatically from the GraphQL query response. The number of output tables and their column definitions depend on the query submitted. The following rules apply to the output data:
•The query must return data using an edges / nodes structure. The connector uses this structure to identify individual records and map them to output rows.
•Each distinct entity type in the query response produces a separate output table. The table name is derived from the entity type name in the query.
•Each connector run executes the configured query once. Pagination is handled internally by the connector.
•Relation fields within a query response are mapped to additional tables, with foreign key columns linking related records.
|
Note: If the query response does not contain an edges or nodes element, the connector cannot derive a schema and will raise an error. Verify the query structure before running a collection. |
