anchor.diff:  
   `GET /v2/service_usage_events`
   
  -For documentation on the response information, see the [api docs](http://apidocs.cloudfoundry.org/latest-release/service_usage_events/list_service_usage_events.html).
  +For documentation about the response information, see the [API documentation](http://apidocs.cloudfoundry.org/latest-release/service_usage_events/list_service_usage_events.html).
   
   #### Event States
   
  
positive.code: 
  `GET /v2/app_usage_events`
  
  For documentation on the response information, see the [api docs](http://apidocs.cloudfoundry.org/latest-release/app_usage_events/list_all_app_usage_events.html).
  
  #### Event States
  App Usage Events have the following valid states: 'STARTED', 'STOPPED', 'TASK\_STARTED', 'TASK\_STOPPED', and 'BUILDPACK_SET'.
  
negative.code: 
  |Event Type| Endpoint | Documentation |
  |---|---|---|
  | App Usage Events | `/v2/app_usage_events/destructively_purge_all_and_reseed_started_apps`| [API documentation](http://apidocs.cloudfoundry.org/latest-release/app_usage_events/purge_and_reseed_app_usage_events.html) |
  | Service Usage Events | `/v2/service_usage_events/destructively_purge_all_and_reseed_existing_instances` | [API documentation](http://apidocs.cloudfoundry.org/latest-release/service_usage_events/purge_and_reseed_service_usage_events.html) |
  
  The purge endpoints are used to create initial events for all apps or service instances. The seeded events will all have the current timestamp, rather than the time the app was actually started.
  
  