Tenderen API and MCP connector

• Search tenders and read their documents and extracted requirements
• Manage saved tenders, bids, alerts, teams and consortiums
• Upload and download documents in your library
• Run AI analysis, match scoring and gap analysis
• Read market data: statistics, contract awards and competitors
• Generate an ESPD response and a compliance matrix

1. Make sure your company is on the Enterprise plan and that you are an Owner or Admin.
2. Go to Developers → API keys and create a key. New keys are read-only (tenders:read) until you add scopes.
3. Copy the key straight away. It is shown once; Tenderen stores only a hash of it.
4. Send it as a Bearer token in the Authorization header to endpoints under https://tenderen.com/api/v1.

1. Add a custom connector in your AI assistant with the URL https://tenderen.com/api/mcp/sse.
2. Sign in to Tenderen when the assistant asks. The connector uses OAuth with PKCE and supports dynamic client registration; clients that cannot do OAuth can send an API key as a Bearer token instead.
3. Ask the assistant to search tenders, read requirements or update an alert. It can only do what the key or sign-in allows.

Each API key may make 1,000 requests per hour by default. Going over returns HTTP 429 RATE_LIMIT_EXCEEDED until the hourly window resets. The MCP endpoint has its own limit of 1,000 requests per hour per token.

• API keys can only be created on the Enterprise plan, by an Owner or Admin.
• Webhook endpoints can be registered, but event delivery is not live yet. Poll the API for changes in the meantime.
• The Zapier app and the Word add-in are not yet publicly listed.

Is there a sandbox?

No. Use a key with read-only scopes while you build, and add write scopes when you are ready.

Where is the full endpoint list?

In the developer docs, which list every endpoint with the scope it needs, the error codes and the webhook format.