Bind logins to recipients
Binds the logins you send and leaves every other one alone. Despite the verb this is NOT a full replacement: the map keeps filling itself while you work, and replacing it wholesale would erase logins that arrived between reading and writing. Send null as the value to unbind a login.
A login that is not in the map yet is created by this call, so bindings can be set before the first event names that person. Spelling is on you: the login must match what the source sends, and a typo binds a person who will never be named. Comparison ignores case.
A recipient uuid from another company, a system recipient or a deleted one is refused with 422 — a binding that silently stored nothing would read as done and page nobody.
The response is the whole map, not the part you sent, so one call both binds and shows who is still unbound.
Request
- Base URL: https://wardenpoint.com (the document declares no server; this is the origin it was published from)
- URL: https://wardenpoint.com/api/v1/observability/integrations/{integration}/login-map
- Auth: API key in header X-API-Key
Path parameters
Integration UUID.
Request body
Example request
{
"logins": {
"sjones": "0a5f1f6c-6f0a-4a0e-9d2e-6d1d1a2b3c4d",
"bwayne": null
}
}Response
The whole map after the change, unbound logins first.
Example response
{
"data": [
{
"username": "sjones"
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.