Troubleshooting
Common setup issues and quick fixes.
API key rejected
- API key starts with
fm_live_ - You copied the latest key after regeneration
- Header name is exactly
X-Api-Key
MCP token rejected
- Token starts with
fm_dev_ - Authorization header is
Bearer <token> - MCP URL points to
/mcp
No data in dashboard
- Requests are created against the right app key
- Your user is signed into the correct account
- App key wasn't rotated unexpectedly
Requests not visible in SDK
SDK submissions start as Pending Review. They are only visible to the original submitter until a developer approves them in the dashboard.
To approve: open the app detail page, find the request with the Pending Review badge, click the checkmark icon.
Changing the status (except to Declined) also auto-approves.
See Approval & Review.
Cannot vote on a request (403)
Voting is blocked on unapproved requests. Approve the request first in the dashboard.
The SDK automatically disables the vote button for pending requests.
Vote conflict (409)
Voting on a request you already voted on returns 409 Conflict.
The SDK handles this automatically via toggleVote() — it catches the 409 and removes the vote instead.
If using the REST API directly, call DELETE /api/public/requests/{id}/vote to remove the vote.
Email collection issues
No email field in SDK: Ensure the project's email collection setting is set to optional or required in Dashboard Settings.
Request fails with "email is required": The project has email collection set to required and the request is missing a valid email address.
Comments not loading
Comments require the request to be approved. If the request is pending review, only the original submitter can see and add comments.
Need help
- Review Getting Started
- Check SDK Setup
- Validate MCP Agent Token