Signi API Detail End Point Description
Discover the description of Signi API end points at Swagger service for the complete list of endpoints.
The most commonly used end points follow.
1. Your application supplies the documents or data for template to Signi:
2. Signi provides the status of documents and final documents to your application actively, your application IS exposed to internet, webhooks are provided while document creatin is called, Signi calls webhooks when document state is changed.
Webhooks provided as a part for document creation call
3. Signi provides the documents and their status up to your request, your application is not exposed to internet:
List of Documents of the particular author - usually workspace owner resp. API key owner
4. Other operations