x_api_create_direct_messages_by_conversation_id
Create a direct message in an existing X conversation using its ID. Sends a new DM to the specified conversation thread.
Instructions
Create DM message by conversation ID. Use when: Create DM message by conversation ID. Do not use when: a more specific auth/configuration tool is required before the API call or you are only exploring; prefer x_schema_discovery or x_query_suggestion first. Risk: mutating, high-risk. Required permissions and prerequisites: OAuth 2 user token with scopes dm.write, tweet.read, users.read; OAuth 1a user token Environment-selection behavior: scopeTenantId plus exactly one of scopeUserId or scopeAccountId choose the Vault/Postgres tenant principal used for auth resolution. credentialKey selects a non-default stored credential profile when present. Parameter formats and constraints: dm_conversation_id (path, string, required); body is used for the documented request payload. Expected response shape: { ok, status, data: { method, path, url, status, contentType, authType, data } } Common failure conditions: missing scoped credentials in Vault, missing required API parameters, X API auth failures, rate limits, or unsupported multipart/body shape. Recommended prerequisite and follow-up tools: x_connection_info, x_schema_discovery, x_auth_upsert_principal_credentials, x_api_request. Safety warnings: This mutates X state. Validate scope, payload, and authorizationKey before use. Example: {"name":"x_api_create_direct_messages_by_conversation_id","arguments":{"scopeTenantId":"default","scopeUserId":"default","dm_conversation_id":"","body":{}}}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | ||
| scopeUserId | No | ||
| credentialKey | No | ||
| scopeTenantId | No | ||
| scopeAccountId | No | ||
| authorizationKey | No | ||
| preferredAuthType | No | ||
| dm_conversation_id | Yes |