Skip to main content

Partner List

This screen is for the technical administrator. When the clinic integrates with an outside system — a booking app, a Zalo mini app, a partner's own software — that side needs an API access account. This is where you issue, restrict and revoke it.

The Partner list screen with five areas numbered

Illustration of the Partner list screen

AreaWhat it does
1. CreateIssues access to a new partner.
2. KeywordSearch by partner name or email.
3. CompanyFilter by clinic brand.
4. The row buttonsRegenerate credentials, edit, delete for that partner.
5. The lock buttonLocks or unlocks the partner. A locked row is tagged Partner is locked.

The table holds Company, Partner name, Email, Status, IP whitelist and Expiration date.

Issuing access​

The partner form with seven areas numbered

Illustration of the partner form

AreaWhat goes in
1. Partner name (required)The integrating system, e.g. Booking app, Zalo mini app.
2. Email (required)Their technical contact.
3. Rate limitPermitted API calls; 1000 by default.
4. Expires atLeave blank for no expiry.
5. StatusActive · Inactive · Suspended.
6. Allowed IP listEmpty = allow all IPs. Give a list, e.g. ["192.168.1.1", "10.0.0.0/24"].
7. Allowed CORS originsEmpty = allow all origins. E.g. ["https://h5.zdn.vn", "https://app.partner.com"].

The Integration section of the partner form with two areas numbered

Illustration of the Integration section

AreaWhat goes in
1. Webhook URLWhere the software calls out when an event should reach the partner.
2. SaveCreates the partner and issues the credentials.

Client ID and Client Secret​

On save, a Client secret dialog appears with the Client ID and Client Secret, with buttons to copy each and Copy all.

The Client Secret is shown once

The software says it plainly: save the Client Secret now — you will not be able to see it again once this window closes. Send it to the partner's technical contact over a safe channel. If it is lost, use Regenerate credentials on the partner's row to issue a new secret — the old one stops working immediately.

Three ways to tighten access​

ControlWhen to use it
IP restrictionThe partner calls from fixed servers — list those IPs and a stolen secret is useless elsewhere.
CORS origin restrictionThe partner is a web app or mini app — allow only their domain.
Expiry dateA time-limited engagement: set the date and access switches itself off.

To stop access immediately, hit Lock partner — access cuts out while the configuration stays for later.

One partner record per integration

Don't share one Client ID/Secret across systems. Keep them separate and you can lock exactly the one causing trouble, and the logs tell you who called.