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 the Pro plan (and during the trial).

​
What the API does

The API is a small, customer-centric surface:
  • Create feedback: send feedback into Lane, linked to the customer it came from. Name the company by its website domain (or its name), and the person by their email. Feedback counts for the right company even when the person writes from a personal address like gmail.com.
  • Keep the date it was given: loading older feedback, such as last year’s survey answers, send the date each piece was given. Your trends then show when customers said it, not the day you imported it.
  • 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.
If Lane can’t use something you send, like a misspelled domain or a date it can’t read, the feedback is still created and the response says what was skipped. 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 label so you can recognize it later, and click Create Key.
  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.
  • Delete a key anytime: hover over it in the list and choose Delete. Anything using that key stops working.

​
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 (linked to a company by its domain or name and to a person by their email, with the date it was given if you have it), read your signals, and verify a key. See the API reference for details. Q: How do I make sure feedback lands on the right company?
A: Send the company’s website domain. A domain identifies a company exactly; a name may match more than one, and an email from gmail.com or similar doesn’t name a company at all. Q: How is this different from the MCP server?
A: The API is for programmatic integrations. The MCP server lets AI apps like Claude, ChatGPT and Cursor work with your workspace in a conversation.