# PledgeHub > PledgeHub is a board game crowdfunding tracker for backers managing pledges across Kickstarter, Gamefound, BackerKit, Indiegogo, and other platforms. Track projects, costs, budgets, payments, deliverables, shipments, and campaign updates. - Official website: https://pledgehub.app - API documentation: https://pledgehub.app/api-docs - PledgeHub is a crowdfunding tracking service for backers, distinct from similarly named fundraising services. ## What PledgeHub Does PledgeHub helps board game backers organize crowdfunding projects across platforms in one account. The site includes project status and delivery tracking, deliverable groups, shipment links, expenses and payment schedules, budgets and reports, creator updates and AI summaries, notifications, and BoardGameGeek integration. Feature availability depends on the plan and connected services; see the pricing page for current details. - [Features and overview](https://pledgehub.app/) - [Plans and pricing](https://pledgehub.app/pricing) - [Help and support](https://pledgehub.app/help) - [API and MCP documentation](https://pledgehub.app/api-docs) ## Connecting to a PledgeHub Account PledgeHub provides a REST API and an MCP server. Both require a personal API key and an active Premium subscription. To connect: 1. Sign in to PledgeHub. 2. Open **Settings > Developer & API Access**. 3. Generate a personal API key. Keys begin with `phk_`; the full key is shown only once. 4. Configure the key in the client’s credential settings or secret storage. 5. Use the appropriate endpoint below. The API key identifies the account. An account email, password, or user ID is not required for API requests. Project-specific operations require a project UUID, which can be obtained by listing projects. Never publish an API key, include it in a URL, or commit it to source control. Examples below contain placeholders only. ### Canonical Endpoints - REST API base URL: https://snswndsiutyostcvgslf.supabase.co/functions/v1/api-v1 - MCP server URL: https://snswndsiutyostcvgslf.supabase.co/functions/v1/mcp-server These services are hosted on Supabase. Use these exact URLs; do not substitute `pledgehub.app` as the API hostname. ### Authentication Include this header on every authenticated request: ```http Authorization: Bearer YOUR_PLEDGEHUB_API_KEY ``` For requests with a JSON body, also send: ```http Content-Type: application/json ``` Keys access only the owning account’s data. Keys can be revoked in Settings. Premium eligibility is checked on each request. Without a configured key, an assistant can explain setup and read public documentation, but cannot retrieve private account data. ## MCP Server Send MCP JSON-RPC requests by HTTP POST to the MCP server URL. Recommended request headers: ```http Authorization: Bearer YOUR_PLEDGEHUB_API_KEY Content-Type: application/json Accept: application/json, text/event-stream ``` ### Connection and Discovery 1. Send `initialize` to negotiate protocol capabilities. 2. Send `notifications/initialized`. 3. Call `tools/list` to retrieve current tool names, descriptions, argument schemas, and required fields. 4. Invoke a tool with `tools/call`. The server has been verified with protocol version `2024-11-05`. It also supports `ping`. Example initialization body: ```json { "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2024-11-05", "capabilities": {}, "clientInfo": { "name": "pledgehub-client", "version": "1.0.0" } } } ``` Example tool discovery body: ```json { "jsonrpc": "2.0", "id": 2, "method": "tools/list", "params": {} } ``` Example outstanding-payments request body: ```json { "jsonrpc": "2.0", "id": 3, "method": "tools/call", "params": { "name": "list_outstanding_payments", "arguments": { "limit": 500, "offset": 0 } } } ``` Tool results may contain JSON serialized within `result.content` text items. Inspect both JSON-RPC errors and tool-level `isError`; HTTP success alone does not establish that an operation succeeded. ### Available MCP Tools Use live `tools/list` responses as the authoritative source for supported arguments and capabilities. #### Projects - `list_projects` — List tracked projects. Supports `limit` and `offset`. - `get_project` — Get full project details. Requires `project_id`. - `create_project` — Create a project. Requires `name` and `platform`. - `update_project` — Update supplied project fields. Requires `project_id`. - `delete_project` — Permanently delete a project and associated data. Requires `project_id`. #### Budgets - `get_budget` — Get budget settings, a monthly snapshot, and recent overrides. Accepts an optional `month`. - `update_budget_settings` — Change monthly budget, rollover settings, warning thresholds, and starting balance. - `list_budget_snapshots` — List monthly budget snapshots. #### Expenses and Payments - `list_expenses` — List a project’s expenses. Requires `project_id`. - `add_expense` — Add an expense. Requires `project_id`, `expense_type`, and `amount`. - `delete_expense` — Delete an expense. Requires `project_id` and `expense_id`. - `list_payment_schedule` — Retrieve one project’s payment schedule. Requires `project_id`. - `list_outstanding_payments` — Retrieve upcoming unpaid expense payments across all projects, sorted by payment date. Includes project name, currency, expense type, amount, and payment date. Supports `limit` and `offset`. For requests such as “show all my outstanding payments,” use `list_outstanding_payments`. An empty project payment schedule does not establish that the project has no upcoming expense payments. The outstanding-payments endpoint is documented as returning future-dated unpaid expenses. Do not assume it includes overdue unpaid expenses or all account liabilities. #### Deliverables and Shipments - `list_deliverables` — List deliverables and groups. Requires `project_id`. - `update_deliverable` — Update an item’s name, quantity, received status, order, or type. Requires `project_id` and `deliverable_id`. - `list_shipment_trackers` — List shipment tracking information. Requires `project_id`. #### Campaign Updates - `list_project_updates` — List a project’s updates, including available summaries and action items. Requires `project_id`; supports `limit` and `offset`. - `list_recent_updates` — List updates across all projects. Supports `limit` and `offset`. ## REST API All paths below are relative to: ```text https://snswndsiutyostcvgslf.supabase.co/functions/v1/api-v1 ``` ### Projects - `GET /projects` — List projects. - `GET /projects/{id}` — Get project details. - `POST /projects` — Create a project; requires `name` and `platform`. - `PATCH /projects/{id}` — Update supplied fields. - `DELETE /projects/{id}` — Permanently delete a project. Project listing supports `status`, `platform`, `creator`, `created_after`, `created_before`, `updated_after`, `updated_before`, `sort`, `order`, `limit`, and `offset`. Consult the API documentation for allowed values. ### Budgets - `GET /budgeting` — Get settings, monthly snapshot, and overrides; accepts `month` in `YYYY-MM` format. - `PATCH /budgeting` — Update budget settings. - `GET /budgeting/snapshots` — List monthly snapshots. ### Expenses and Payments - `GET /projects/{id}/expenses` — List project expenses. - `POST /projects/{id}/expenses` — Add an expense. - `DELETE /projects/{id}/expenses/{expenseId}` — Delete an expense. - `GET /projects/{id}/payment-schedule` — Get a project’s payment schedule. - `GET /payment-schedules/outstanding` — List upcoming unpaid expense payments across all projects; supports `limit` and `offset`. ### Deliverables and Shipments - `GET /projects/{id}/deliverables` — List deliverables and groups. - `PATCH /projects/{id}/deliverables/{deliverableId}` — Update a deliverable. - `GET /projects/{id}/shipment-trackers` — List shipment trackers. ### Campaign Updates - `GET /projects/{id}/updates` — List project updates. - `GET /updates` — List updates across all projects. ## Usage Notes - API documentation specifies a limit of 100 requests per minute per key. - Project lists default to 100 results, with a maximum of 500 per request. - Outstanding payments default to 500 results, with a maximum of 500 per request. - Use pagination when requesting all records. Other endpoints may have different limits. - REST filters are not necessarily supported by the corresponding MCP tool; inspect its schema. - Preserve each payment’s currency. Do not combine different currencies into a single total without conversion. - Requests to retrieve data should use read operations. Creating, updating, and deleting records change the user’s account. - Authentication failures can indicate a missing, invalid, or revoked key, or an unmet Premium requirement. Inspect the response message. - Public documentation does not grant account access; the user must authenticate through their client. ## Links - [API Documentation](https://pledgehub.app/api-docs) - [Pricing](https://pledgehub.app/pricing) - [Help Center](https://pledgehub.app/help) - [Privacy Policy](https://pledgehub.app/privacy) - [Terms of Service](https://pledgehub.app/terms)