Auto Reply
Manage keyword auto-replies — the automatic responses that fire when an inbound message matches a rule.
httpAuthorizationBearer <token>application/json- response
data*array<array<unknown>>meta*curl -X GET 'https://aexrux.com/api/v1/auto-replies'{ "data": [ [ null ] ], "meta": { "count": 0 }}httpAuthorizationBearer <token>application/json- body
Create a keyword auto-reply. Scramble reads these rules to document the
request body. Mirrors the input keys the existing
AutoreplyController::store accepts, exposed under public-facing names. A
"custom" reply carries one or more replies[] text variants; a "flow"
reply points at a saved flow_id.
keyword*stringTrigger keyword(s). Comma-separated phrases are allowed. Required.
length <= 255matching_method?|How the inbound message is matched against the keyword. Defaults to exact.
"fuzzy""exact""contains"fuzzy_similarity?|Fuzzy match threshold 0-100 (only used when matching_method=fuzzy).
0 <= value <= 100device_id*stringSending device id. Required.
status?|Whether the rule is active. Defaults to true.
reply_type?|Reply kind: "custom" (text variants) or "flow" (a saved flow). Defaults to custom.
"custom""flow"flow_id?|Flow id to run (required when reply_type=flow).
Scope to the caller's workspace so an auto-reply can't reference
another tenant's flow (was a bare integer with no ownership).
replies?array<>|Reply text variants (for reply_type=custom). At least one required for custom.
application/json- response
data*array<unknown>meta*stringcurl -X POST 'https://aexrux.com/api/v1/auto-replies' \ -H 'Content-Type: application/json' \ -d '{ "keyword": "string", "device_id": "string"}'{ "data": [ null ], "meta": "string"}httpAuthorizationBearer <token>id*integerapplication/json- response
data*array<unknown>meta*stringcurl -X GET 'https://aexrux.com/api/v1/auto-replies/0'{ "data": [ null ], "meta": "string"}httpAuthorizationBearer <token>id*integerapplication/json- response
data*meta*stringcurl -X DELETE 'https://aexrux.com/api/v1/auto-replies/0'{ "data": { "id": 0, "deleted": true }, "meta": "string"}httpAuthorizationBearer <token>id*integerapplication/json- body
Update a keyword auto-reply. Scramble reads these rules to document the
request body. Same shape as StoreAutoReplyRequest — the underlying
AutoreplyController::update replaces the rule's settings and appends any new
replies[] text variants.
keyword*stringTrigger keyword(s). Comma-separated phrases are allowed. Required.
length <= 255matching_method?|How the inbound message is matched against the keyword. Defaults to exact.
"fuzzy""exact""contains"fuzzy_similarity?|Fuzzy match threshold 0-100 (only used when matching_method=fuzzy).
0 <= value <= 100device_id*stringSending device id. Required.
status?|Whether the rule is active. Defaults to true.
reply_type?|Reply kind: "custom" (text variants) or "flow" (a saved flow). Defaults to custom.
"custom""flow"flow_id?|Flow id to run (required when reply_type=flow).
Scope to the caller's workspace so an auto-reply can't reference
another tenant's flow (was a bare integer with no ownership).
replies?array<>|Reply text variants (for reply_type=custom). At least one required for custom.
application/json- response
data*array<unknown>meta*stringcurl -X PUT 'https://aexrux.com/api/v1/auto-replies/0' \ -H 'Content-Type: application/json' \ -d '{ "keyword": "string", "device_id": "string"}'{ "data": [ null ], "meta": "string"}