← All updates
Integration API

Update Contracts through the API and AI Apps

Until now an integration or a connected AI app could read contract data but never change it. The public API gains endpoints to set one or more property values by key and to set a contract’s status, and the MCP connector gains matching update_contract_properties and set_contract_status tools. Both behave exactly like an edit made in the app: renewal dates recalculate, the timeline records the change, workflows fire and search results update.

Update Contracts through the API and AI Apps

Writes need the new contracts:write scope, chosen on the connection consent page or on an API key’s permissions. Every call runs as the connected user or key owner with their normal Pactly permissions, so it can only change contracts that person could change in the app, and only within their company. Property values are validated against the property’s type and, for conditional lists, against the parent value. The timeline attributes each change to the user and the app or key it came through.

Endpoints and scopes are on the API reference, and the MCP tools reference lists the connector’s tools.