Skip to main content
Lane’s public API lets external tools and your own systems push feedback into Lane and read your signals. You authenticate with an API key you create in your workspace. It powers integrations like Zapier and the Chrome Extension, and is available on Pro and Business plans.

​
What the API does

The API is a small, customer-centric surface:
  • Create feedback — send feedback into Lane with an optional customer email, so it’s linked to the right account automatically.
  • Read signals — pull your workspace’s signals to trigger workflows elsewhere (for example, a Zap that fires when a high-priority signal surfaces).
  • Verify — check that a key is valid.
For the full request and response details, see the API reference tab.

​
Create an API key

  1. Go to Settings → API.
  2. Click Create API Key.
  3. Give it a name so you can recognize it later, and click Generate.
  4. Copy the key and store it securely — this is the only time it’s shown in full.
Treat your API key like a password. Don’t share it publicly or commit it to a repository. 🔐

​
Manage your keys

  • Create multiple keys — one per tool or integration is good practice, so you can revoke access to one without affecting the others.
  • Revoke a key anytime from the … menu next to it.

​
FAQs

Q: I didn’t copy my key and can’t see it anymore.
A: Keys are shown only once at creation for security. Generate a new one and delete the old key. Q: Should I reuse one key everywhere?
A: Better to create a separate key per integration — it isolates access and makes revocation clean. Q: What can the API do?
A: Create feedback (optionally linked to a customer by email), read your signals, and verify a key. See the API reference for details. Q: How is this different from the MCP server?
A: The API is for programmatic integrations. The MCP server lets AI assistants read your workspace conversationally.