Developer Portal

Choose an API surface

Partner Publishing API — obtaining access

The Partner Publishing API is for approved organisations operating a trusted server. It is not a browser API, and credentials must never be placed in HTML, client-side JavaScript, iframe URLs, logs, or public MCP configuration.

1. Open the private, single-use application invitation supplied by an administrator. Invitations expire within seven days and are not publicly discoverable.
2. Enter the short-lived code sent to that organisation mailbox. Verification submits the application for manual review; it does not create a credential.
3. If approved, the verified mailbox receives a one-time retrieval link. Open it within 15 minutes and copy the credential immediately; the raw credential is shown once and cannot be recovered later.
4. Store the credential in a server-side secret manager and send it as Authorization: Bearer …. Start with GET /api/partner/v1/me to confirm the partner identity, key ID, allowed portal IDs, scopes, and expiry. It returns no personal account data and never returns the raw credential.
5. Use a unique Idempotency-Key for each publication request. A credential can call only the endpoints, portals, and scopes explicitly approved for it.

Version 1 endpoints

Credentials expire after 180 days unless revoked earlier. Rotation creates a new credential through the same one-time mailbox retrieval process; the previous credential remains active until explicitly revoked so integrations can switch safely. Application, verification, and API traffic are rate-limited.

What you can build

Venue assistant for pub groups

A managed pub group can let venue staff describe the entertainment or supplier they need in a conversational assistant, then hand them a completed Open Call Portal form to review and publish.

Recommended rollout

1. The pub user chats about venue, location, date, opportunity type, genres, budget, equipment, and other portal-specific fields.
2. The partner backend converts the conversation into the canonical portal contract and creates a short-lived review draft.
3. The pub user opens the hosted review form, corrects anything needed, supplies their contact details, and verifies their email.
4. The pub user publishes; the resulting open call enters the normal moderation, canonical URL, search, and response workflow.
5. After a successful pilot, an approved-domain iframe can replace the partner-hosted chat while preserving the same server-side credential and human-review boundaries.

MCP — Claude, ChatGPT, Perplexity, Gemini, Copilot & Grok

The platform exposes a stateless Model Context Protocol server over Streamable HTTP. Public MCP access needs no Open Call Portal API key and exposes seven PII-free discovery and safe, no-write form-preparation tools. It cannot create drafts, send email, verify codes, submit responses, or publish.

{
  "mcpServers": {
    "open-call-portals": {
      "url": "https://opencallportal.com/mcp"
    }
  }
}

Or in any MCP client: endpoint POST https://opencallportal.com/mcp, protocol Streamable HTTP / JSON-RPC 2.0; supported versions 2025-11-25, 2025-06-18, and 2025-03-26.

Inspect the server manifest: GET https://opencallportal.com/.well-known/mcp.json

Google Gemini (Gemini CLI)

Add this server under mcpServers in Gemini CLI's settings.json. Gemini CLI uses httpUrl for Streamable HTTP:

{
  "mcpServers": {
    "open-call-portals": {
      "httpUrl": "https://opencallportal.com/mcp"
    }
  }
}

Google's Gemini CLI MCP documentation

Microsoft Copilot (Copilot Studio)

In Copilot Studio, open the MCP onboarding wizard, choose to connect an existing server, and enter https://opencallportal.com/mcp. The public Open Call Portal MCP server requires no credentials and exposes seven no-write discovery and editable form-handoff tools.

Microsoft's Copilot Studio MCP documentation

Grok (xAI)

For the Grok CLI, add the remote server with:

grok mcp add --transport http open-call-portals https://opencallportal.com/mcp

xAI's native SDK and Responses API also support remote MCP using server_url; allow only the seven public tools listed below when configuring a broader client.

xAI's Grok CLI MCP documentation · xAI's Remote MCP API documentation

Available tools

Authenticated integration MCP

Approved partners connect server-to-server at POST https://opencallportal.com/mcp/integration using an issued bearer credential. Tools appear only when the credential has the matching scope and portal entitlement. Credentials must never enter browser or iframe code.

For direct versioned publication instead of human-review drafts, use the separate Partner Publishing API. Onboarding begins with a private administrator-issued invitation, continues through organisation-mailbox verification and manual approval, and ends with one-time credential delivery. Verify the issued credential with GET /api/partner/v1/me. The public MCP server never accepts or exposes Partner API credentials.

Agent API — safe form handoff

Use the agent API to validate a versioned, portal-specific prefill and return the correct editable Create form. This endpoint never stores a draft, sends email, verifies a code, responds to a listing, or publishes content.

• Validate the prefill
  POST /api/agent/prepare-listing-form with version, a canonical portalId, and only fields declared by GET /api/agent/schema.
• Open the returned form
  Give the returned formUrl to the person. They add contact details, review the values, complete normal email verification, and choose whether to submit.

Full no-write handoff with curl:

# ── Step 1: validate a safe no-write form prefill ─────────────────────
curl -s -X POST https://opencallportal.com/api/agent/prepare-listing-form \
  -H "Content-Type: application/json" \
  -d '{
    "version": 1,
    "portalId": "dj",
    "location": "London",
    "fields": {
      "userRole": "venue-manager",
      "date": "2026-10-15",
      "openCallTypes": ["paid-fixed"],
      "genres": ["techno","house"]
    }
  }'
# → {"formUrl":"https://djopencall.com/DJ?tab=create&prefill=<base64url-packet>"}

# ── Step 2: open the editable form for the person ─────────────────────
# The person enters their own contact details, reviews every value,
# completes email verification, and decides whether to submit.
# No data was created by the validation request.

Full field spec (GET /api/agent/schema) Location IDs (GET /api/locations)

AI safety boundary

The public AI surface intentionally has no draft, verification, response, publication, or webhook tools. Keep the form editable and leave email entry, verification, review, and submission to the person using the hosted portal.

Canonical portal parameter reference

This server-rendered reference is generated from the canonical publication contract. It covers every demand, availability, and live-event schema.

Open a portal to inspect canonical values. Required fields are scoped to the selected draft or publish operation.

Demand portals

Availability portals

Live event

GPT Actions & OpenAPI

The safe handoff API is published as an OpenAPI 3.1.0 spec for ChatGPT custom GPTs, Semantic Kernel, LangChain, n8n, and any OpenAPI-compatible agent framework:

OpenAPI spec (GET /api/agent/openapi.json) · ChatGPT plugin manifest