Supernormal.com API reverse engineering and data exporting

Supernormal.com was one of my favourite new products I paid for last year – even doing a full year subscription immediately after trialling. The chrome extension for AI note taking is the best I found and works seamlessly.

However as an API nerd the lack of an accessible useful public API both perplexes, and frustrates adding Supernormal to my workflows, and thus reduces its “stickyness” – meaning if/when a similar product comes along which does have a decent public API then i’ll be sorely tempted to move.

To plug this gap, and make it possible for me to export my data should I be forced to move products we reverse engineered their private API, documented it using the OpenAPI 3.1 spec, and created an export script to backup our data.

We’ve open sourced both of these for anyone in the same situation. https://github.com/thatapicompany/supernormal.com-api-exporter

Documenting their Private API with OpenAPI spec

• Requires an Authorization Bearer token
• https://github.com/thatapicompany/supernormal.com-api-exporter/blob/main/supernormal-openapi.json

Workflows a decent public API could enable

Zapier is fine, but it’s expensive and not useful for a lot of companies, and whilst Supernormal currently has 9 integration options it doesn’t cover the more interesting workflows like:

Personalized Daily Briefing for Executives:

Use Case: Deliver daily executive summaries via email or chatbot.

• A developer could quickly put together an Integration that:
  • Gmail, Outlook API → Send daily email summaries.
  • Slack, Microsoft Teams Bot → Post daily briefs.
  • Google Sheets, Notion → Store structured meeting insights.
• Enabled by:
  • Supernormal API collects all meeting summaries from the past day.
  • AI extracts high-priority topics.
  • The executive receives a morning briefing via email/Slack.

Automating Compliance & Documentation for Legal & Finance:

Use Case: Store meeting records in secure, auditable locations for compliance.

• DocuSign, IronClad → Store compliance notes.
• AWS S3, Google Drive, OneDrive → Archive meetings securely
• SOC 2 / GDPR Compliance Tools → Log meeting records.
• Enabled by:
  • Supernormal API fetches meeting data tagged as “Legal” or “Finance”.
  • Summaries & transcripts are stored in a secure, compliant database.
  • A report is generated for auditors.

Off the top of my head, I can think of other’s we’ve done for clients like Podcast & content creation automation, or even Automated sales and intelligence & lead scoring.

So many opportunities that a decent API programme enables….

What would we recommend they do?

For companies like Supernormal that have a private API, and an extremely limited public API (albeit in this case with no way to create keys for it), we would recommend:

• Create a full API programme to encompass success metrics, product management, development needed, monetisation strategies, and support (including docs and sample code).

• Identifying the customer problem cases – in this case a customer is churning because there is no public API to export their data, and the inbuilt Integrations do not cover their workflows.

• Interview the customers to find out their use-cases and design a proper API around it.

What would some easy steps of an API programme actually look like for them?

Improve API Access & Authentication:

• Implement a proper API authentication mechanism:
  • OAuth 2.0 (Client Credentials Flow) for backend integrations.
  • API Keys for easier access in lower-security environments.
  • JWT-based authentication for session-based users.
• Allow self-service API key provisioning via a developer portal.
• Clearly define and differentiate public vs. private API access.

Open Up the Public API for Customers

• Define clear API access tiers (e.g., free, pro, enterprise).
• Offer sandbox environments for developers to test integrations.
• Create an API access request flow via the website or developer portal.

Expand API Documentation with Code Samples

• Add code samples in multiple languages (Python, JavaScript, Node.js, Go).
• Use Swagger / OpenAPI Specification to generate interactive API docs.
• Provide real-world use cases, e.g., how to:
  • Fetch posts and tasks.
  • Automate reporting with the API.
  • Sync data with external systems.

Dev Support and Community:

• Provide multiple support channels:
  • API support email (e.g., api-support@supernormal.com).
  • GitHub Issues / Discussions for bug reports and feature requests.
  • Discord / Slack community for real-time API discussions.
• Add a changelog to track API updates and fixes.
• Offer premium support for enterprise customers.

API Partner & Monetization Strategy

• Create partner API programs with early access & premium features.
• Offer API usage plans:
  • Free tier (limited requests).
  • Paid tiers with increased limits and SLAs.
• Consider developer evangelism: hosting API webinars, tutorials, and guides.

Improve API Reliability & Versioning

• Use semantic versioning (v1, v2, etc.) for API updates.
• Publish rate limits and quota policies.
• Implement webhooks for event-based notifications.

Final Thought

Supernormal has the potential to build a developer-friendly API ecosystem. By implementing secure authentication, better documentation, developer support, and monetization strategies, they can increase adoption and revenue from API users.

Remember: Good API documentation tells a story. It’s not just about what endpoints exist, but rather it’s about how to use them successfully. Our process ensures we uncover and tell that story completely.

Need to document your undocumented API? Now you know our secrets. Just remember: capture, convert, test, and polish. Works every time. Also, we are here to help, reach out for free consultation.