What authentication does the Precisely Public API use?

The Precisely API supports two authentication methods: bearer token authentication using a JWT obtained from the POST /authenticate endpoint, and API key authentication using the X-API-KEY header. Through Jentic, credentials are stored encrypted and agents receive scoped access without managing tokens directly.

What are the rate limits for the Precisely Public API?

The Precisely API allows up to 30 requests per minute per organization. Rate limit status is returned in response headers: X-Ratelimit-Limit shows the maximum, X-Ratelimit-Remaining shows requests left in the current window, and X-Ratelimit-Reset shows when the window resets in UTC epoch seconds.

Can I create contracts from templates with the Precisely API?

Yes. Use GET /organizations/{orgId}/templates/{templateId}/references to retrieve the questions defined in a template, then POST /organizations/{orgId}/templates/{templateId}/projects with your answers to create a new project. The project generates one or more documents based on the template configuration.

How do I send a document for e-signature through Jentic?

Install the Jentic SDK with pip install jentic, then search for 'send document for electronic signature'. Jentic returns the Precisely signature-request operation. First add signees via POST /organizations/{orgId}/documents/{docId}/signees, then trigger the signing via POST /organizations/{orgId}/documents/{docId}/signature-request.

Does the Precisely API support webhook notifications?

Yes. The API supports resthook-style webhook subscriptions for events like document status changes. Callbacks include a Precisely-Signature header for payload verification using HMAC-SHA256. Failed deliveries are retried 3 times, and subscriptions are disabled after 10 consecutive failures.

Can I limit what my agent is allowed to do with the Precisely API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Precisely operations and credentials the agent may use. Since Precisely puts the organization and document ids in the URL path, such as /organizations/{organizationId}/documents/{documentId}, a rule can pin the agent to a single organization so it only reads and creates that organization's content. You also choose the specific operations it may call, so an action like sending a signature request via POST /organizations/{organizationId}/documents/{documentId}/signature-request is available only if you explicitly allow it.