# Help understanding Upsert - How to Commit Mutations/Upserts

**URL:** <https://discuss.dgraph.io/t/help-understanding-upsert-how-to-commit-mutations-upserts/9566>\
**Category:** Dgraph\
**Tags:** status:accepted, area:documentation, area:upsert\
**Created:** [August 19, 2020, 6:55pm UTC](https://discuss.dgraph.io/t/help-understanding-upsert-how-to-commit-mutations-upserts/9566 "2020-08-19T18:55:48Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![dmai](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/dmai/32/1254_2.png) [@dmai](https://discuss.dgraph.io/u/dmai)\
**Post date:** [August 19, 2020, 7:58pm UTC](https://discuss.dgraph.io/t/help-understanding-upsert-how-to-commit-mutations-upserts/9566/7 "2020-08-19T19:58:28Z")

</div>

Over the HTTP API, you can set `/mutate?commitNow=true` for the /mutate endpoint.

For txns with multiple mutations, you can call /commit separately with the appropriate timestamp and txn keys/preds: [https://dgraph.io/docs/clients/raw-http/#committing-the-transaction](https://dgraph.io/docs/clients/raw-http/#committing-the-transaction)

When you commit, you’ll see the `commit_ts` in the extensions in the response, e.g.:

```
{
    "data": { ... },
    "extensions": {
        "txn": {
          "start_ts": 200460131, **"commit\_ts": 200460132,**...
        }
    }
}
```

---

_[View the full topic](https://discuss.dgraph.io/t/help-understanding-upsert-how-to-commit-mutations-upserts/9566)._
