Creatio Raises $200M at $1.2B valuation to lead the enterprise no-code market

Documentation

Creatio development guide
PDF
This documentation is valid for Creatio version 7.16.0. We recommend using the newest version of Creatio documentation.

Integration with Creatio and public API

Glossary Item Box

Creatio has a wide range of integrations with custom third-party applications.

First, accessing Creatio by a third-party application requires authentication. For more information on accessing Creatio, see “External requests authentication to Creatio services”. For more information on Creatio primary authentication service, see “The AuthService.svc authentication service”.

Starting with version 7.10, authentication is protected from CSRF attacks. For more information, see “Protection from CSRF attacks during integration with Creatio”.

Brief description and comparison of Creatio basic integration methods is available in the “Choosing the method of integration with Creatio” article.

Wide range of integration capabilities is available through API provided by the DataService web service. Fore more information on create, read, update and delete operations (the CRUD operations), as well as the API, see the “DataService” article.

If the third-party system uses the OData protocol, it cal also be used for integration with Creatio. For more information, see the “Integration via OData protocol” article.

Using the iframe HTML element for integration is covered in the “Integration of third-party sites via iframe” article.

For more information on the “Web-to-Object” integrations, see the “Web-To-Object. Integration via landings and web-forms”.

Use methods of the ProcessEngineService.svc web service to trigger Creatio processes via third-party applications. Description of methods and public web service API are available in the following article: "The ProcessEngineService.svc web service". 

Contents

 

 

 

© Creatio 2002-2020.

Did you find this information useful?

How can we improve it?