The connection also runs the other way. Give another site you own a read key and it can ask the desk about a customer, so a membership site or a mailer can show 3 tickets, 1 open next to the person without anybody logging in to the desk.
Creating a key:
- Open Integrations and find Let Your Other Sites Read Support History.
- Type a label that says where the key will be used, for example Membership site, and click Create Read Key.
- The key is shown once in a green box with a Copy button. Copy it then. Afterwards only a short hint is kept, such as the first and last few characters, so you can tell your keys apart.
Keys are stored as a one-way hash, never in the clear, so nobody who can read your database can recover them.
Revoking a key:
Each key has its own Revoke button. Revoking takes effect immediately and only affects that key, so you can cut off one site without touching the others. The table also shows when each key was last used, which makes an unused or forgotten key easy to spot.
What a key can read:
For one email address: the customer's name, how many tickets they have in total, how many are open and how many are resolved, a count per status, the first and last ticket dates, and the subject, status, priority, product and category of their ten most recent tickets. Spam tickets are counted separately and never as open. A second route returns desk totals for a dashboard tile: open tickets, new tickets in the last seven days and how many of those the AI resolved on its own.
What is never sent:
Message text, private notes, internal drafts, and anything about other customers. Keys are read-only, so nothing can be created, changed or deleted with one. Requests are limited to 120 a minute per address.
For your developer:
Send the key in the X-ASD-Key header. The customer route is /wp-json/asd/v1/customer with an email parameter, and the totals route is /wp-json/asd/v1/stats. A customer with no tickets returns 404, a missing or wrong key returns 403, and too many requests returns 429. The exact URL for your site is printed under the key table.