Instructions for connecting Zalo Cloud

To use Zalo Cloud services on eTelecom, partners/customers must link the application (app) with cs.etelecom.vn

Note : eTelecom recommends that you use 2 separate applications for 2 sandbox and prod environments for convenience in API integration.

Step 1 : Access the Zalo developers page

Step 2: Access the application you previously created

Select your Zalo account avatar icon as shown.

Go to the application you want to connect to eTelecom

Note : If you don't have one, you can select " Add new application "

Enter the required information. For details, please refer to this document .

Step 3: Proceed to "Domain authentication"

The purpose of domain authentication is so that you can configure the webhook link provided by eTelecom.

After accessing the application -> Domain authentication -> Depending on the environment you are using, fill in the following domain information:

• Sandbox : api-sandbox.etelecom.vn and etelecom.vn

• Prod : api.etelecom.vn and etelecom.vn

You select " Verify now " to proceed with authentication.

Select "Add meta tag to your website homepage" -> copy the meta tag in "Step 1" and send it to eTelecom.

Note : The verification process may take up to 72 hours for Zalo to review. If the domain status is still Unverified, please select Verify again.

Successfully approved domains will be displayed in the "Verified Domain List" section.

Step 4: Configure webhook

Configuring "Webhook URL" will help eTelecom receive Zalo events returned to build reports, message sending history, ... accurately, serving your needs.

After successfully verifying the domain , you access " Webhook " -> Copy the " OA Secret Key " information and send it to eTelecom.

eTelecom will update the "Secret Key" for the webhook and then notify you to change the " Webhook URL " information.

• Sandbox: https://api-sandbox.etelecom.vn/v1/zalo/Callback
• Prod: https://api.etelecom.vn/v1/zalo/Callback

In case you do not have " OA Secret Key " information, you proceed to change the "Webhook URL" according to the following information:

• Sandbox: https://api-sandbox.etelecom.vn/v1/zalo/Callback
• Prod: https://api.etelecom.vn/v1/zalo/Callback

After successful update, please provide eTelecom with the " OA Secrect Key " information.

After successful update, please provide eTelecom with the " OA Secrect Key " information.

Note : In case your "Update webhook url" fails -> the system displays a message as shown, please " Proceed to verify domain " until the domain is displayed in the " List of verified domains " section.

Note: If you reset or perform any operation that results in "OA Secret Key", please provide it to eTelecom.

In the " Webhook event list " section:

• If you use ZNS feature: you just need to enable " Message received event " and " ZNS notification received user event " as shown

• If you use ZNS Journey: you need to enable the events " Journey Expired Notification " and " Journey Charged Notification".

• If you use ZCC feature : you need to enable " OA event sends call request to user / request expired " and " User event responds to call request from OA "

• To see the list of interested people , you need to enable the events " User interested Official Account " and " User uninterested Official Account ".

• To use the " OA chat " feature, you need to enable events related to " Official Account " and " User".

Step 5: Set up the path to request permission

The purpose of this step is for eTelecom to have information to link your application with the eTelecom system.

Note :

• In case the customer wants to " Link Official Account " on etelecom.vn , it is necessary to reset the permission request path in the "Official Account Callback Url" section according to the following information:

  • Prod environment: https://api.etelecom.vn/v1/zalo/OAuth
  • Sandbox Environment: https://api-sandbox.etelecom.vn/v1/zalo/OAuth
• In case customers want to integrate Zalo Cloud API into existing software, they can use their own Callback URL. The Callback URL is where processing is performed to receive the authorization code and the state returned after performing OA authorization for the App.