Integrating with the Enact API enables seamless interaction with Enact's suite of services, facilitating efficient data management and operational workflows. This guide provides an overview of key integration aspects, including creating leads, understanding organisational hierarchy, setting up organisations, navigating sandbox and production environments, adhering to rate limits, and accessing support contacts.

Enact API References

To initiate a new project within Enact or update a project or fetch data or assets from proposals, you can utilize the API endpoints. Detailed documentation and examples for this endpoint are available at Enact API Reference.

Organisational Hierarchy

Enact's organisational hierarchy is structured to enhance reporting, analysis, and data visibility control. Proper configuration of this hierarchy ensures that users have appropriate access to data relevant to their roles. More information on configuring the corporate hierarchy can be found as below

Setting Up an Organization

When integrating with the Enact API, it's essential to set up your organization's structure correctly to ensure seamless data flow and user access. This involves defining the various levels of the hierarchy and assigning processes accordingly. 

Sandbox and Production Environments

Enact provides two distinct environments for API integration:

• Sandbox: A testing environment that allows developers to simulate and validate their integrations without affecting live data. This environment is ideal for initial development and troubleshooting.

• Production: The live environment where real data transactions occur. Once integrations are thoroughly tested in the sandbox, they can be deployed to the production environment.

Understanding the differences between these environments ensures that testing and deployment processes are conducted smoothly and without unintended consequences. 

Rate Limits

To maintain system performance and prevent abuse, Enact enforces rate limits on API requests. Rate limiting controls the number of API calls that can be made within a specific timeframe. Exceeding these limits may result in temporary restrictions or throttling. It's crucial to design your integration to handle rate limiting gracefully, implementing strategies such as exponential backoff and request queuing.