Skip to main content

Overview

Every question and answer across your workspace is available through a single paginated endpoint. Each record carries the question, the answer, who asked it, the source channel, and a timestamp, so you can pull Wolfia activity into your own reporting, monitoring, and governance systems.

The conversation insights endpoint

URL: GET https://api.wolfia.com/v1/insights/conversations Authentication: API key required (see API overview for setup) A restricted key needs the Questionnaires: read scope.

Request format

Query parameters

Understanding source types

Conversations in Wolfia come from multiple sources, each tracked and returned by the API:

web_ui

Conversations where users interact with Wolfia through the web application interface.

slack_dm

Conversations from direct messages with the Wolfia bot in Slack.

browser_extension

Conversations initiated through the Wolfia browser extension on vendor portals and web forms.
Source type filtering: The current API returns all source types. Contact support if you need source-specific filtering for your use case.

Response format

Success response (200 OK)

Response fields

Timestamps: The answered_at field uses microseconds since Unix epoch. Divide by 1,000,000 to convert to seconds for most programming languages.

Error responses

Integration examples

Python: Export conversations to CSV

Export all conversations to a CSV file for analysis:

Python: Real-time conversation monitoring

Monitor new conversations in real-time and send alerts:

JavaScript: Filter by source type

Retrieve and filter conversations by source type:

Best practices

Pagination strategies

Always use the maximum page size (100) to minimize API calls:
For very large conversation histories, process pages as you fetch them:
Cache conversation data to reduce API calls:

Timestamp handling

Conversation timestamps use microseconds since Unix epoch. Here’s how to work with them:

Error handling and retry logic

Retry failed requests with increasing delays:
Maintain detailed logs of API interactions:

Data privacy and compliance

When working with conversation data:
  • PII handling: Conversation data contains personally identifiable information (user emails, names). Handle according to your privacy policies.
  • Data retention: Implement appropriate data retention policies for exported conversation data.
  • Access control: Restrict access to conversation insights to authorized personnel only.
  • Audit logging: Log all API access and data exports for compliance auditing.

Use cases

Analytics and reporting

Build custom dashboards to track:
  • Conversation volume trends over time
  • Most active users and teams
  • Source type distribution (web UI vs Slack vs agents)
  • Peak usage hours and days

Quality assurance

Monitor AI performance by:
  • Reviewing conversation quality across different source types
  • Identifying common user questions
  • Analyzing response patterns
  • Tracking user satisfaction

Compliance and auditing

Export conversation history for:
  • Regulatory compliance requirements
  • Security audits
  • Legal discovery
  • Data governance

Integration monitoring

Track integration health:
  • Monitor Slack app usage
  • Verify agent conversation flows
  • Analyze cross-channel performance
  • Identify integration issues

Rate limits and quotas

The conversation insights API follows standard Wolfia API rate limits:
  • Default rate limit: 100 requests per minute per API key
  • Burst allowance: Short bursts above the limit are allowed
  • Quota reset: Rate limit window resets every minute
If you hit rate limits:
  • Implement exponential backoff
  • Spread requests over time
  • Cache results when appropriate
  • Contact support for higher limits if needed

Getting help

If you encounter issues with the conversation insights API:
  • Check authentication: Verify your API key is active in API settings
  • Review pagination: Ensure page and page_size parameters are valid
  • Validate permissions: Confirm you have admin role for API access
  • Check timestamps: Verify you’re handling microsecond timestamps correctly
  • Contact support: Email support@wolfia.com with your API key ID (never share the full key)

Next steps

API overview

Learn about API authentication, rate limits, and best practices

Invite users

Automate user onboarding with programmatic invitations