Send Message
Send a direct message. Target an existing conversation_id or a user_id (starts/reuses a 1-on-1). When encryption_code (your XChat PIN — the code you set when enabling encrypted chats on X) is supplied with a conversation_id, the message is sent end-to-end encrypted (so it can later be deleted for everyone); otherwise it uses X’s reliable legacy path (delete-for-self only).
Authorizations
Your OmniX API key, e.g. omnix_live_.... Billed per call.
Body
The X account auth_token cookie the action runs as.
"YOUR_X_AUTH_TOKEN"
The message text.
"hello from the API"
An existing conversation (from the inbox). Provide this or user_id.
"1000000000000000001:2000000000000000002"
A numeric user id to start/reuse a 1-on-1. Provide this or conversation_id.
Your XChat encryption code — the PIN you set when enabling encrypted chats on X. Used to recover your key so messages can be decrypted and outgoing events signed.
"YOUR_XCHAT_PIN"
Optional outbound proxy for this call (http:// or https://, optionally user:pass@host:port). The X request runs through it — useful for geo-routing or spreading calls across IPs. SOCKS proxies are not supported.
"http://user:pass@host:8080"