Skip to content
OriginChats

slash_call

slash_call is implemented by handleSlashCall in src/api/handlers/slash/slash_call.osl.

Handles the slash call protocol operation through the resource-specific helper and storage layers.

Access

Section titled “Access”
Gate Requirement
Authentication Required by the central API gate.
Central permission None. Resource, channel, ownership, or hierarchy checks may still apply in the handler/helpers.
Broadcast Not marked global directly by this adapter. A helper may emit focused or server-wide updates.

Request

Section titled “Request”

Every request includes cmd: "slash_call" and may include an opaque listener correlation value.

Field Validation / meaning
channel schema.string().defaultValue("")
thread_id schema.string().defaultValue("")
command schema.string().trim().minLen(1)
args schema.record(schema.any()).defaultValue({})
username schema.string().optional()
author_id schema.string().optional()
key_id schema.string().optional()
signature schema.string().optional()
timestamp schema.number().optional()
nonce schema.string().minLen(16).maxLen(128).optional()

Validator source

Section titled “Validator source”

The handler and shared validation path use these OSL schema definitions before normalization:

*schema.Schema schemaSlashCall = schema.object({
  channel: schema.string().defaultValue(""),
  thread_id: schema.string().defaultValue(""),
  command: schema.string().trim().minLen(1),
  args: schema.record(schema.any()).defaultValue({}),
  username: schema.string().optional(),
  author_id: schema.string().optional(),
  key_id: schema.string().optional(),
  signature: schema.string().optional(),
  timestamp: schema.number().optional(),
  nonce: schema.string().minLen(16).maxLen(128).optional()
})

Processing path

Section titled “Processing path”
  1. handleCmd enforces authentication.
  2. dispatchCmd routes slash_call to handleSlashCall.
  3. The adapter validates and normalizes input, then calls its domain collaborators.
  4. Durable mutations complete before the response or event is returned.
  5. onMessage adds the request listener to direct responses and performs any marked broadcast.

Direct collaborators visible in the handler: messageContext, slashResolve, slashAccessError, slashArgsError, slashSigningData, forwardSlashCall, runServerSlashCommand

Responses and events

Section titled “Responses and events”

Response/event command names visible in this adapter: slash_call.

Validation and domain failures use:

{
  "cmd": "error",
  "val": "<message>",
  "src": "slash_call",
  "listener": "<copied from request>"
}