x_api_get_insights_historical
Fetch historical post insights for specified tweet IDs over a custom time range, with configurable granularity and metrics to analyze past performance.
Instructions
Get historical Post insights. Use when: Get historical Post insights. 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 tweet.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: tweet_ids (query, array, required); end_time (query, string, required); start_time (query, string, required); granularity (query, string, required); requested_metrics (query, array, required). 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_insights_historical","arguments":{"scopeTenantId":"default","scopeUserId":"default"}}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end_time | Yes | ||
| tweet_ids | Yes | ||
| start_time | Yes | ||
| granularity | Yes | ||
| scopeUserId | No | ||
| credentialKey | No | ||
| scopeTenantId | No | ||
| scopeAccountId | No | ||
| authorizationKey | No | ||
| preferredAuthType | No | ||
| requested_metrics | Yes |