Troubleshoot NudgeForMe API and MCP connections
Diagnose authentication, scope, region, idempotency and rate-limit errors.
REST and MCP troubleshooting
Which endpoint should I use?
Global REST origin: https://app.nudgeforme.com. EU REST origin: https://europe.nudgeforme.com. Append /api/v1/....
Global MCP: https://app.nudgeforme.com/mcp. EU MCP: https://europe.nudgeforme.com/mcp.
Credentials are regional.
REST returns 401
Check that the header is Authorization: Bearer YOUR_KEY, the key is not revoked/expired, and the request is going to the correct region. Keep the key private.
REST returns 403
The credential may lack the endpoint's permission scope, or your organization/workspace membership may not authorize the requested mailbox or thread. Creating another key does not bypass workspace permissions.
The assistant has no MCP tools
MCP connections use OAuth with PKCE, not developer API keys. Reconnect the AI client using the remote MCP endpoint. Confirm it completed authorization and was granted sufficient scopes.
A POST returns a conflict
Nudge expects a unique idempotency identifier for each write operation. If you reused a key for a different action, generate a fresh ID. If a request timed out or is still processing, check the thread status first before retrying.
429 rate limited
Developer keys are limited to 60 authenticated requests per minute per key. Reduce concurrency, batch read operations carefully and back off instead of retrying in a tight loop.
My Outlook provider request fails
If OAuth authorization to Nudge succeeded but fetching Outlook messages fails, first check the mailbox provider connection inside Nudge. A Microsoft tenant/token problem is a different class of error from Nudge's OAuth login.