Skip to main content
The Project Echo REST API lets you list and manage feedback programmatically. Base URL: https://api.projectecho.io/v1 Create keys under API & MCP in the Workspace nav.

​
Authentication

Send both headers on every request:

​
Members vs users

These are different people resources:
  • Members (/v1/members) — portal end-users of your product. Email can be exposed for identify/embed flows.
  • Users (/v1/users) — workspace teammates in the staff app. Email is not returned.
Resolve request authors with created_by_member_id → members, or created_by_user_id → users.

​
Common resources

With the right permissions you can work with:
  • Requests (list, get, create, update, delete)
  • Comments (public) and internal notes (staff-only)
  • Votes
  • Members and users
  • Boards and statuses
Write actions that act on behalf of a portal member typically need member_id or external_user_id in the JSON body. Internal notes require an author_user_id (teammate UUID).

​
Filters

GET /v1/requests supports filters such as board_id, status_id, created_by_user_id, plus limit and offset.

​
Tips

  • Start with a read-only key while exploring.
  • Public comments endpoints exclude internal notes — use the internal-notes paths for staff-only content.
  • Prefer MCP when you want AI tools (Claude, Cursor) to call the same capabilities through tools instead of raw HTTP.
Full permission presets are chosen when you create the key. Questions: [email protected] · Help Center.

Related topics

Create and manage API keysConnect AI tools with MCP (Claude, Cursor, and others)Embed Project Echo in your product (My app / identify users)What is Project Echo?Tour of the staff app (Requests, Roadmap, Changelog, Members, Settings)