Skip to main content
Operation grouping is optional metadata you can send when one user action or backend job takes multiple API calls. It lets you follow the trail later in the ZangTable admin panel: what calls happened, in what order, which one failed, and how long the whole action took. 
X-Operation-Key: edit-profile-email
X-Operation-Run-Id: oprun_client_20260602_001
  • X-Operation-Key is the human-readable operation label, such as edit-profile-email, checkout-submit, or daily-report-export.
  • X-Operation-Run-Id is the tracking ID for one specific run of that operation. Generate one ID at the start of a multi-step action and send it with each related API call.
  • These headers are recommended for multi-step project actions/events that use multiple API calls, which is common.
  • If a task only needs one API call, you can still include an operation run ID if you want that call to be easier to find later. Otherwise, a normal single API call is fine.
  • Interactive operation groups have a 420-second idle window.
  • After 7 minutes without activity, a later call with the same operation identity may appear as a separate API journey group with a new unique Operation Run ID generated to continue the grouping if needed. Make sure your code can notice Operation Run ID changes if you use them for your own tracking or alerting.