Needs the customer:write scope.
Call
- Tool:
activate_license - Scope:
customer:write - Writes, and may change or remove what is there.
- Acts on a store.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
store |
string |
No | The store to act on. |
product |
object |
Yes | |
key |
string |
Yes | The key as the customer typed it. |
instance |
string |
Yes | A stable id of the device or seat, chosen by the software; only its keyed digest is kept. |
name |
string |
No | What the holder and the merchant see it as, such as the device’s name. |
{
"type": "object",
"properties": {
"store": {
"type": "string",
"description": "The store to act on."
},
"product": {
"anyOf": [
{
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 512
}
},
"required": [
"id"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"minLength": 1,
"maxLength": 512
}
},
"required": [
"slug"
],
"additionalProperties": false
}
]
},
"key": {
"description": "The key as the customer typed it.",
"type": "string",
"minLength": 1,
"maxLength": 128
},
"instance": {
"description": "A stable id of the device or seat, chosen by the software; only its keyed digest is kept.",
"type": "string",
"minLength": 1,
"maxLength": 256
},
"name": {
"description": "What the holder and the merchant see it as, such as the device's name.",
"type": "string",
"minLength": 1,
"maxLength": 480
}
},
"required": [
"product",
"key",
"instance"
],
"additionalProperties": false
}Answer
| Name | Type | Required | Description |
|---|---|---|---|
activations |
object |
Yes | |
activation |
object |
Yes | |
token |
string |
Yes | A compact JWS (EdDSA) the software checks offline against the store’s published signing keys. |
token_expires_at |
string |
Yes | When the token stops verifying: the earliest of the product’s offline window and the end of the access it carries. |
The answer’s full shape is on its API reference page.
Errors
A refused call is a tool error. Its structuredContent holds a code and its context, except for client-fault. This tool may answer:
invalid: an argument is malformed;context.pathnames it.invalidat["store"]:storeis missing while the connection reaches more than one store, or names a store it doesn’t reach.not_found: nothing matches a reference given.conflict: the call clashes with the current state;contextnames the field and, where it helps, its current value, and for afrom,live,expector version that no longer matches, the argument (path) and what it takes (reason).not_permitted: this connection may not make this call. Whencontext.reasonislimit, too many calls:retry_aftersays when to try again.internalorunavailable: the call failed inside Sherpo, and the write may have landed. This write takes no idempotency key, so read the state back before trying again.client-fault: the server failed around the call.core_answerokmeans the write landed, so don’t send it again. Whenreached_coreis false, nothing happened and the call may be made again. Otherwise, this write takes no idempotency key, so read the state back before trying again.- HTTP 403 with
insufficient_scope: the connection lacks the scope this tool needs. - HTTP 401 with
invalid_token: the access token expired or the connection ended. Refresh the token, and connect again if the refresh fails or the new token is refused too.
Any other code may come back too, such as a conflict when the state changed under the call. When the answer was already streaming, a 401 or 403 comes back as a tool error with only its text. See Errors for every code and its context.