This is the one integration that reaches out over the network while a ticket is being resolved. It exists so that lost key and activation tickets can be answered with real data instead of a request for more information.
Adding a server:
- Open Integrations and find the License Servers table.
- Give the server a name, which is what appears as the product name in the reply, for example WCT.
- Enter its base URL and a shared secret.
- Use Add License Server for as many as you need, then save.
What the lookup sends:
For each configured server, the plugin posts a small JSON body containing the customer's email address to a license-lookup endpoint under that base URL. The body is signed with an HMAC-SHA256 signature built from your shared secret and sent in a signature header, so your server can reject anything that is not from you.
What it expects back:
A JSON response containing a list of keys. For each key the desk reads the key itself, its status, its expiry date and the seats used and seats allowed. Servers that do not answer, or that answer with no keys, are skipped quietly and the other servers still run.
How the result is used:
The collected keys are handed to Claude alongside the recorded purchases, with an instruction to use only that data, to invent nothing, and to list each key clearly against its product. If neither the sales table nor any license server returns anything, the resolver refuses to reply and leaves you a private note instead.
This is a generic contract rather than a lock-in. Any endpoint of yours that accepts the signed email and returns keys in that shape will work.