# \[#1294\] Booking source ( admin-booked v. self-booked ) in webhook

**URL:** https://tech-support.simplybook.me/t/1294-booking-source-admin-booked-v-self-booked-in-webhook/1294
**Category:** Bug Reports
**Tags:** migrated, redmine-1294
**Created:** [October 23, 2024, 10:47pm UTC](https://tech-support.simplybook.me/t/1294-booking-source-admin-booked-v-self-booked-in-webhook/1294 "2024-10-23T22:47:29Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![system](https://tech-support.simplybook.me/uploads/default/original/1X/faedac32116409149d0a20d900b3047df01a4ad0.png) [@system](https://tech-support.simplybook.me/u/system)
#### Post date: [October 23, 2024, 10:47pm UTC](https://tech-support.simplybook.me/t/1294-booking-source-admin-booked-v-self-booked-in-webhook/1294/1 "2024-10-23T22:47:29Z")

</div>

**Migrated from Redmine #1294** | _Author: Michael Wells_  
_Status: Feedback | Priority: High, I’m very impatient | Created: 2024-10-23_

* * *

Doing a lot of SBM work for clients in conversions, and we’re unable to find some data we need.  
One key factor is the origin of a booking.

Currently the webhook appears to fire on all bookings, whether made by admin or through the website widget, and we don’t see a way to differentiate?  
Even a call to retrieve that new booking by ID doesn’t seem to contain the data we need, but we can see it in SBM admin console reports.

How do we determine this?

---

<div class="post-metadata">

### Author: ![system](https://tech-support.simplybook.me/uploads/default/original/1X/faedac32116409149d0a20d900b3047df01a4ad0.png) [@system](https://tech-support.simplybook.me/u/system)
#### Post date: [October 24, 2024, 1:33am UTC](https://tech-support.simplybook.me/t/1294-booking-source-admin-booked-v-self-booked-in-webhook/1294/2 "2024-10-24T01:33:41Z")

</div>

**Michael Wells** wrote:

Ideally, we’d really like the ability to tag an individual booking widget so that the specific tag also appears as a field.  
Quite commonly we have special widget setups for specific user groups to handle different booking approaches, so we’d like to be able to determine

- It was from an online widget booking
- Any widget-specific tag like “poac” that was assigned in the config JSON

Same for API-initiated bookings, the ability to tag that booking for future traceability and reporting.

---

<div class="post-metadata">

### Author: ![system](https://tech-support.simplybook.me/uploads/default/original/1X/faedac32116409149d0a20d900b3047df01a4ad0.png) [@system](https://tech-support.simplybook.me/u/system)
#### Post date: [October 24, 2024, 7:36am UTC](https://tech-support.simplybook.me/t/1294-booking-source-admin-booked-v-self-booked-in-webhook/1294/3 "2024-10-24T07:36:25Z")

</div>

**Dmytro Bondarev** wrote:

Hi,  
you can use [API documentation | SimplyBook.me Online Scheduling](https://simplybook.me/en/api/developer-api/tab/rest_api#method_GET_/admin/bookings/%7Bid%7D) method to get booking details.  
in result you will receive [API documentation | SimplyBook.me Online Scheduling](https://simplybook.me/en/api/developer-api/tab/rest_api#type_AdminBookingDetailsEntity) , by field log you can see if it was created by user or by client.

---

<div class="post-metadata">

### Author: ![system](https://tech-support.simplybook.me/uploads/default/original/1X/faedac32116409149d0a20d900b3047df01a4ad0.png) [@system](https://tech-support.simplybook.me/u/system)
#### Post date: [October 31, 2024, 3:09am UTC](https://tech-support.simplybook.me/t/1294-booking-source-admin-booked-v-self-booked-in-webhook/1294/4 "2024-10-31T03:09:18Z")

</div>

**Michael Wells** wrote:

Thanks Dmytro,

A few questions, I’ll work backwards.

I’m currently using Zapier’s integration to log the bookings and identify the source. In the zapier event I get a Booking Code but no Booking ID.  
The /admin/bookings appears to require the ID, how do I translate the code to the ID? I’ve tried various filters on /bookings but unable to find the right way to isolate it.

Once I have the ID I can call /admin/bookings and see the log;  
In the case of a customer-created booking will the user\_login always be null? Or should I look for specific admin logins in order to determine the customer v. admin booking origin?

And third, is there a way to auth directly ( e.g. Bearer token ) using the SBM api key?  
I have the api key but have not figured out how to use it in API auth, so I’m temporarily using user login-\> token which will break when the user password changes.

Thanks!
