Reverted REST API endpoint deprecation

Last year's announcement about decommissioning the 'fact sheets' REST API endpoints raised varying reactions amongst our client base. Still, the general sentiment of your feedback expressed an apparent necessity of these API endpoints in your daily operations. The reactions clarified how these endpoints cater to unique use cases our recommended GraphQL API cannot cover exhaustively.

We have decided to reverse the deprecation for these API endpoints after reevaluating the situation. Our objective remains evident: to reinforce continuity in your operations and optimize the value you achieve from our products while avoiding unforeseen disruptions.

We thank those who proactively migrated their integration use cases to GraphQL API, which remains the preferred solution for most cases. In some instances, GraphQL can not meet your needs and expectations for developing integrations. Most prominently, the ease of quickly fetching all fact sheet attributes from a workspace without studying the GraphQL schema, where the 'fact sheets' endpoints offer a more straightforward experience.