Upload app logs from S3 without a session (internal)

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://docs.usehearsay.com/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "integrations MCP server": {
    "url": "https://docs.usehearsay.com/mcp"
  }
}

Close
POST /extraction/device/app-general-logs/v2

Desktop plumbing: same as app-general-logs, but the log file is one the app already uploaded to S3 (fileProviderId); it is downloaded, zipped with the request details, stored again and announced on Slack.

application/json

Body Required

  • systemId string Required
  • date string Required

    ISO date string

  • appVersion string

    App version

  • message string

    Message

  • osDetails object
  • extractionCode string
  • deviceId string
  • deviceType string
  • fileProviderId string Required

Responses

  • 200 application/json
    Hide response attributes Show response attributes object
    • data object Required
      Hide data attributes Show data attributes object
      • message string Required
      • isSuccess boolean Required
    • statusCode number Required
    • timestamp string(date-time) Required
POST /extraction/device/app-general-logs/v2
curl \
 --request POST 'http://api.example.com/extraction/device/app-general-logs/v2' \
 --header "Authorization: Bearer $ACCESS_TOKEN" \
 --header "Content-Type: application/json" \
 --data '{
  "systemId": "string",
  "date": "string",
  "appVersion": "string",
  "message": "string",
  "osDetails": {},
  "extractionCode": "string",
  "deviceId": "string",
  "deviceType": "string",
  "fileProviderId": "string"
}'
Request examples
{
  "systemId": "string",
  "date": "string",
  "appVersion": "string",
  "message": "string",
  "osDetails": {},
  "extractionCode": "string",
  "deviceId": "string",
  "deviceType": "string",
  "fileProviderId": "string"
}
Response examples (200)
{
  "data": {
    "message": "Done",
    "isSuccess": true
  },
  "statusCode": 200,
  "timestamp": "2026-01-15T10:15:00.000Z"
}