Interface: PairingRequest
@kortexya/reasoninglayer / PairingRequest
Interface: PairingRequest
Section titled “Interface: PairingRequest”Defined in: src/types/pairing.ts:63
A DM pairing request: an unknown sender who wrote a direct message to one
of the caller’s channels while its policy was pairing.
Properties
Section titled “Properties”channelId
Section titled “channelId”channelId:
string
Defined in: src/types/pairing.ts:73
Channel the message arrived on.
createdAt
Section titled “createdAt”createdAt:
string
Defined in: src/types/pairing.ts:79
When the request was filed (RFC 3339).
id:
string
Defined in: src/types/pairing.ts:65
Request id; the key the approve and reject calls take.
pairingCode
Section titled “pairingCode”pairingCode:
string
Defined in: src/types/pairing.ts:77
The 6-character code the sender was given.
platform
Section titled “platform”platform:
string
Defined in: src/types/pairing.ts:71
Platform the message arrived on (slack, discord, telegram, email, webhook).
senderId
Section titled “senderId”senderId:
string
Defined in: src/types/pairing.ts:67
The sender’s platform id.
senderName?
Section titled “senderName?”
optionalsenderName?:string|null
Defined in: src/types/pairing.ts:69
The sender’s display name, or null when the platform supplied none.
status
Section titled “status”status:
string
Defined in: src/types/pairing.ts:75
Request status (Pending for every listed request).