Skip to main content
PUT
A lookup key is your word for a product you sell — meses, quincenas — pointed at one version of one configuration. Your code holds the key; the platform answers which configuration and version it names. The configuration keeps the identifier the platform composed for it: a key is a tag beside it, not a new name. A key names a version, not a configuration in general. Writing a new version sells nothing until you point a key at it.
Moving a key changes what the next borrower is offered. A key that already names another version moves only when the body states transfer: true. On a live Tenancy an agent cannot point or remove a key — a person or your own key does.

Path parameters

string
required
The Tenancy pointing the key.
string
required
Your word: 1 to 64 letters, digits, - and _, case-sensitive, unique within your Tenancy. A word shaped like an identifier the platform composes (inst-000001) or mints (a UUID) is refused.

Body

string
required
The configuration the key sells.
integer
required
The version of it the key sells.
boolean
true to move a key that names another version. Absent or false, that key is refused lookup_key_taken.

Response

The key as it now stands — the same answer as reading it. Every pointing is recorded and none is rewritten, so what a key named on any past day is on record. The key is in the path, so a retry is safe by itself: it finds the key where the first attempt left it. An Idempotency-Key is ignored.

Refusals