/tokenendpoint you will need to provide your individual Partner ID. The easiest way to find your Partner ID is to log into the 360 Partner Hub on your browser and go to the "WhatsApp Accounts" section. Then check the URL in the address bar of your browser. The Partner ID follows after the
/partner/parameter and can easily be identified by its
PAsuffix, see the image below.
/tokenendpoint needs to be made including the username (email) and password of one of your partner users in the request body. You can either use a personal user account or set up a system user specifically for the API tasks. The response from the
/tokenendpoint will include an
partnerquery parameter to the submission form URL. The value from this parameter will be stored as
partner_payloadon the 360dialog Client model.
GET /partners/<your-partner-id>/clientsendpoint you will be able to find the 360dialog Client ID as well as your identifier, that you've passed via the partner query parameter.
partner_payloadwill also be included in any webhook event that you receive.
PATCHexisting clients with your
partner_payloade.g. by matching them via e-mail or phone number.
deeplink_url, which is being used to redirect clients back to your application after they created their API key. This URL however is static.
redirect_urlquery parameter available on the submission form URL.
redirect_urlquery parameter, which will be stored locally on the client's device and will be used for redirection after the API key is created.
redirect_urlis being used instead of the
deeplink_url, we will also attach the 360dialog Client and Channel IDs as query parameters to your URL. This means by clicking the button the user will return to:
projectin your redirect URL.
GETrequests to check information regarding your 360 Partner Hub.