# Order.add payload example needed

**URL:** <https://integration.keap.com/t/order-add-payload-example-needed/12168>\
**Category:** API Q&A\
**Created:** [August 24, 2017, 12:07pm UTC](https://integration.keap.com/t/order-add-payload-example-needed/12168 "2017-08-24T12:07:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eric\_D](https://avatars.discourse-cdn.com/v4/letter/e/b487fb/32.png) [@Eric\_D](https://integration.keap.com/u/Eric_D)\
**Post date:** [August 24, 2017, 12:07pm UTC](https://integration.keap.com/t/order-add-payload-example-needed/12168/1 "2017-08-24T12:07:47Z")

</div>

Trying to locate the **order.add** json payload example output for my infusionsoft customer.

We didn’t find it referenced in the API docs.

---

<div class="post-metadata">

**Author:** ![TomScott](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/tomscott/32/67_2.png) [@TomScott](https://integration.keap.com/u/TomScott)\
**Post date:** [August 24, 2017, 4:55pm UTC](https://integration.keap.com/t/order-add-payload-example-needed/12168/2 "2017-08-24T16:55:03Z")

</div>

If you are referring to the RESThook “order.add” subscription, the payload should contain only the id of the added object and the timestamp of the change. You could then query the /orders/{id} endpoint to get the details of the object, which would be as described [in the REST documentation](https://developer.infusionsoft.com/docs/rest/#!/E-Commerce/loadOrderUsingGET).

---

<div class="post-metadata">

**Author:** ![John\_Borelli](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/john_borelli/32/11880_2.png) [@John\_Borelli](https://integration.keap.com/u/John_Borelli)\
**Post date:** [August 24, 2017, 6:36pm UTC](https://integration.keap.com/t/order-add-payload-example-needed/12168/3 "2017-08-24T18:36:17Z")

</div>

Yes, like @TomScott said, the hook payload contains the relevant contact/object id’s involved. They may come in a series inside of an array but that’s all that comes is notification it happened (by the hook being called) and the id’s. It would be easy enough to just create a trap at your endpoint to write the json string to a file and look at it with your own eyes.