# Debug with REST API

**URL:** <https://forum.flowable.org/t/debug-with-rest-api/1496>\
**Category:** Flowable Engine\
**Created:** [January 25, 2018, 3:11am UTC](https://forum.flowable.org/t/debug-with-rest-api/1496 "2018-01-25T03:11:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rob](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rob](https://forum.flowable.org/u/rob)\
**Post date:** [January 25, 2018, 3:11am UTC](https://forum.flowable.org/t/debug-with-rest-api/1496/1 "2018-01-25T03:11:50Z")

</div>

Hello all,

[This](https://forum.flowable.org/t/apis-for-debugging-workflow-progress/459) thread explains how to view a process instance’s history using Java. How can I do the same using the REST API?

I am looking for a way to debug processes, i.e. to see where the errors are in the flow. Right now I can’t see any sort of audit trail to lead me in the right direction.

Thanks!

---

<div class="post-metadata">

**Author:** ![martin.grofcik](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/martin.grofcik/32/71_2.png) [@martin.grofcik](https://forum.flowable.org/u/martin.grofcik)\
**Post date:** [January 26, 2018, 4:04pm UTC](https://forum.flowable.org/t/debug-with-rest-api/1496/2 "2018-01-26T16:04:32Z")

</div>

Hi Rob,

Audit trail (old):  
there are java sources too

> **[martin-grofcik/activiti-crystalball](https://github.com/martin-grofcik/activiti-crystalball/wiki/Audit-trail-diagram)**
>
> testRunToEvent. Contribute to martin-grofcik/activiti-crystalball development by creating an account on GitHub.

History rest API:  
[http://www.flowable.org/docs/userguide/index.html#\_history](http://www.flowable.org/docs/userguide/index.html#_history)

The best source for audit trail is event log. jUnit test: org.flowable.engine.test.api.event.DatabaseEventLoggerTest#testDatabaseEvents

and managementService

```
/**
 * Returns a list of event log entries, describing everything the engine has processed. Note that the event logging must specifically must be enabled in the process engine configuration.
 * 
 * Passing null as arguments will effectively fetch ALL event log entries. Be careful, as this list might be huge!
 */
List<EventLogEntry> getEventLogEntries(Long startLogNr, Long pageSize);

```

Martin