Hi John, I has a use case where I had turned on tracking for a specific field and learned that I had to report this out via the API. Someone in the community (name escapes me) posted a great suggestion that led me to an API query that would return the old and new value for the field. In my example, I'm looking for the old and new value for a specific field that was changed, and who made the change. Here is the API query that I used: "https://YOUR_DOMAIN.my.workfront.com/attask/api/v9.0/jrnle/search?fields=fieldName,oldDateVal,newDateVal,editedBy:name&projectID=YOUR_PROJECT_ID&projectID_Mod=in&fieldName=plannedCompletionDate&fieldName_Mod=in&apiKey=YOUR_API_KEY&method=get">https:// YOUR_DOMAIN .my.workfront.com/attask/api/v9.0/jrnle/search? fields=fieldName,oldDateVal,newDateVal ,editedBy:name&projectID= YOUR_PROJECT_ID &projectID_Mod=in& fieldName=plannedCompletionDate &fieldName_Mod=in&apiKey= YOUR_API_KEY &method=get Here is the post that I used to arrive at the solution: If you're handy with the API you can actually query the journal object and get all the data. A sample query is as follows (of course, add in the relevant object ID or search parameters and your API key): "https://yourinstance.my.workfront.com/attask/api/v7.0/jrnle/search?project:ID=aaa123&fields=*&apiKey=bbb456"> yourinstance.my.workfront.com/attask/api/v7.0/jrnle/... We use this type of query to source the data so we can send alerts to users when certain kinds of changes are made to particular fields by particular people on particular kinds of tasks/projects. We use Azuqua to run the queries on schedule and send the alerts. An example of the JSON-formatted data returned for one of these journal entries is as follows. You can see the fieldName which was changed, along with the changeType and what the oldTextVal and newTextVal were for this example of a custom field edit on a task.