Skip to main content

Greetings, community members!
If by chance you didn't catch our July update, we'd like to take a moment to draw your attention 🔍 to a series of upcoming changes concerning our APIs. We believe these changes will significantly improve your experience with our services and provide you with more efficient, robust tools for your projects.

While we had initially communicated these alterations in our newsletter, we understand that not everyone may have had the chance to read it in detail. Therefore, we'd like to provide a brief rundown here, along with the corresponding links for your convenience.

We will introduce API updates that align with the latest GraphQL standards to maintain our high security 🔐 and compliance standards. The planned API changes will take effect on January 15th, 2025.

This will mainly focus on stricter validation of GraphQL queries, such as the introduction of token limits, which may impact integrations you've built for your workspace.

You can learn more about the upcoming changes in our documentation.

We encourage you to take the time to familiarize yourself with these changes, as they are designed to enhance your engagement with our platform.

Hi @Kostas-LeanIX,

Thanks for the heads-up. Especially for the token limit, we will need very close alignment to ensure that LeanIX Automation Platform will not break.

Let‘s align after the holidays. I will need details on the exact token limit, so that we can work around any potential issues, especially for our major customers with overly complex data models (I think you know who I am talking about ;-)

 Thanks a lot.

 

When will we start seeing the new warnings (in the new extensions block) so we can start testing our code and warning/error handling? For example, running the https://docs-eam.leanix.net/reference/graphql-api-changes#stricter-validation-of-unconsumed-tokens example query does not return the described warning for me today.

Also, to the point made above, can you provide more details about the planned token limits? If the exact details are unknown or subject to changes, can you tell us the order of magnitude (e.g. are we talking 100s of tokens, or 1,000s of tokens, or 10,000s of tokens)?

Thanks

Hello @geoffrey.lowney,
Thanks for the response!  Our engineering teams identified a problem with the release introducing the warnings, which necessitated a temporary rollback of the recent update.

Rest (or GraphQL 😎) assured, our teams are diligently working towards a resolution and we anticipate deploying this fix really soon. Once these changes are implemented. I will make sure to update this thread once we roll out the changes!

Apologies for any inconvenience caused!

Reply


Terms & ConditionsCookie settings