x_api_get_direct_messages_events_by_conversation_id
Retrieve direct message events for a conversation by ID. Use pagination and event type filters to target specific DM history.
Instructions
Get DM events for a DM conversation. Use when: Get DM events for a DM conversation. 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: read-only. Required permissions and prerequisites: OAuth 2 user token with scopes dm.read, 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: id (path, unknown, required); max_results (query, integer); pagination_token (query, unknown); event_types (query, array). 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_get_scope_credentials, x_api_request. Safety warnings: This is read-only, but responses can still include sensitive account data depending on granted scopes. Example: {"name":"x_api_get_direct_messages_events_by_conversation_id","arguments":{"scopeTenantId":"default","scopeUserId":"default","id":""}}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| event_types | No | ||
| max_results | No | ||
| scopeUserId | No | ||
| credentialKey | No | ||
| scopeTenantId | No | ||
| scopeAccountId | No | ||
| authorizationKey | No | ||
| pagination_token | No | ||
| preferredAuthType | No |