Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Info

For sending this request, you have to be authorized. See the Authorization page for more details.

If you want to start using webhooks with your external system and already have some resources in your doo account, you may need to initialize your system with all these existing resources.

After you make the following API request, we will send a webhook request to your external system for each specified resource item that already exists in your doo account. For example, if you chose to initialize all the events from doo, we will send a separate webhook request for each existing event in your doo account.

We send a maximum of 100 50 initialization webhook requests per minute, so it may take some time if you want to initialize a lot of data.

...

Code Block
languagejson
{
    "response_status": 200,
    "developer_message": "Success",
    "user_message": "Success",
    "items_processed": <items_processed_count>,
    "_links": {
        "self": {
            "href": "https://rest.doo.net/v1/webhooks/init/<resource_name>"
        }

   } }

PC Team easy Guide:

To repush webhooks for 1 event use this:

open terminal and copy the edited code, press enter

Code Block
curl -X POST 'https://rest.doo.net/v1/webhooks/init/orders' \
-H 'Content-Type: application/json' \
-H 'x-api-key: doo-test-key-3306c337-4e00-43de-a63d-44c4fb122ea8' \
-H 'Authorization: Bearer <access_token>' \
-d '{
  "event_id": <EventID>,
   "webhook_configuration_id":"<webhook_id>"
}'

real Example:

Code Block
curl -X POST 'https://rest.doo.net/v1/webhooks/init/orders' \
-H 'Content-Type: application/json' \
-H 'x-api-key: doo-test-key-3306c337-4e00-43de-a63d-44c4fb122ea8' \
-H 'Authorization: Bearer acd9d531db1e30a8ba66555ed7830e066af1dde3' \
-d '{
  "event_id": 82032,
   "webhook_configuration_id":"eaf6e0e9-e116-0bbd-e121-b30716188331"
}'

How to get <access_token>:

  • go in doo manager app to your desired OID

  • open developer tool (Chrome & Firefox: F12 or fn+F12)

  • go to Network tab

  • select: Fetch/XHR

  • record network log and maybe clear once

    Image Removed
  • click on a event or booking, does not matter, just do something in doo manager

  • in the network logs is_active should appear

  • click on is_active and check the Headers for “Request Headers”

  • scroll down and search for authorization: Bearer ...

    Image Removed
  • the shown token is your <access_token>

How to get <EventID>:

  • this is just the EventID

How to get <webhook_id>:

...

go in doo manager app to your desired OID

...

go to DAT (https://dat.doo.net/auth/login )

...

login and double check if you are in the correct OID in DAT

...

go to Webhooks

you will see the <webhook_id>, if there are multiple webhook ids, choose the “correct” one that should be repushed

...