In the estimate workspace, open the History tab in the right panel; it reloads each time you open it, so it includes the edits you just made. From the estimates list, History on an estimate's row opens the same timeline in a dialog. It looks like an approval's History tab: newest activity first, each event with its icon, the person or source and a date and time. Only signed-in members of the workspace can open this history in the app. A designer link has no History tab and does not grant access to the timeline.
Read the timeline#
The Last activity card at the top shows two times. Last modified shows the latest recorded change and who made it. Last requested shows the most recent API read of the estimate and whose key made it. They are separate: reading an estimate does not by itself count as changing it. The estimates list's Updated column shows the modification date, time and timezone, with the most recently modified estimates first.
Use All, Changes, or GET requests to filter the timeline, and the reload button beside History to fetch new events. Older and Newer move through pages of 30 events. Expand a change to inspect its fields and their before and after values. A request entry shows the endpoint, response status, and output choice when supplied.
The source distinguishes a signed-in user, an API key's owner, a designer link, and a system update. A designer link is identified by its label and ID; its secret token is not displayed or saved in history. The label identifies the link that was used, not the individual person holding that link.
What is recorded#
Changes cover the estimate header, quote settings and totals, artwork records, scales, parts and drawing geometry, production settings and results, allowed materials, and designer-link settings. Creating and deleting these records also produces activity. Background calculations appear as System unless they complete within an authenticated request. Saving the same values again does not add a change event.
GET requests are recorded only when they are made with an API key, so the timeline shows when an integration read the estimate. Opening the estimate in the app, or through a designer link, adds no GET events, even though the workspace loads its data from the same endpoints. Recorded GETs include the estimate detail, materials output, drawing state, parts, quote, production, document and history endpoints. An API list request is recorded against each estimate returned on that page. Denied requests and requests for missing estimates do not appear in an estimate's timeline.
GET events are added when the response completes, so a history response or Last requested value shows requests completed before the current request. Reload to see that request. Reading can sometimes start a calculation that changes saved data; that actual change is recorded separately.
History begins when tracking is introduced. Earlier edits cannot be reconstructed: existing estimates retain their previous update timestamp as a starting point, without an invented modifier. Credentials and raw request URLs are not retained. Metadata and return-URL changes are recorded with redacted values.
For the integration fields and the paginated history endpoint, see Materials and history API.