Answers: <p>The service hook will fire as part of the notifications process.  You can suppress all notifications by setting the URI parameter <code>suppressNotifications</code> to <code>true</code>.</p>
  
  <p>An example request URI might be:</p>
  
  <pre><code>PATCH https://dev.azure.com/fabrikam/_apis/wit/workitems/{id}?suppressNotifications=true&amp;api-version=5.0
  </code></pre>
  
  <p>See the <a href="https://docs.microsoft.com/en-us/rest/api/azure/devops/wit/work%20items/update?view=azure-devops-rest-5.0#uri-parameters" rel="nofollow noreferrer">work item update API documentation</a> for more information.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-04-26T14:47:17.890Z
Answers: Can you please help me with that too?
  https://devops.stackexchange.com/questions/7965/file-not-uploading-properly-in-azure-using-postman
Answers: sami ullah
Answers: CC BY-SA 4.0
Answers: 2019-04-25T02:34:22.673Z
Answers: 2019-04-25T02:34:22.673Z
Answers: Sumo
Body: <p>I wrote a service hook on work item update but I don't want to fire the service hook when work item is updated from REST API, becz its the same data that other system had and it post to ADO and now ADO is posting back that data again, and it is creating duplicates, so any workaround to not to fire service hook when work Item is updated using the REST API or can bypass integration user, ?</p>
  
Tags: <azure-devops><azure><tfs>
Title: TFS Service hook should not fire when work item is updated via REST API
UserDisplayName: sami ullah
ThreadText: # TFS Service hook should not fire when work item is updated via REST API
  
  (Asked by: username_0 on 2019-04-23)
  
  I wrote a service hook on work item update but I don't want to fire the service hook when work item is updated from REST API, becz its the same data that other system had and it post to ADO and now ADO is posting back that data again, and it is creating duplicates, so any workaround to not to fire service hook when work Item is updated using the REST API or can bypass integration user, ?
  
  **Tags:** azure-devops, azure, tfs
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-04-25. Score: 1 | Accepted answer
  
  The service hook will fire as part of the notifications process. You can suppress all notifications by setting the URI parameter `suppressNotifications` to `true`.
  
  An example request URI might be:
  
  ```
  PATCH https://dev.azure.com/fabrikam/_apis/wit/workitems/{id}?suppressNotifications=true&api-version=5.0
  
  ```
  
  See the [work item update API documentation](https://docs.microsoft.com/en-us/rest/api/azure/devops/wit/work%20items/update?view=azure-devops-rest-5.0#uri-parameters) for more information.
  
  > **Comments:**
  > **username_0**: Can you please help me with that too? https://devops.stackexchange.com/questions/7965/file-not-uploading-properly-in-azure-using-postman  
  
  ---
  
  