# Hub Support

1. POST /api/v1/pipeline_prospect doesn't update stage on existing records. When we POST with a stage_id for a person who already exists in the pipeline (matched by email), the response returns success: true but the stage doesn't change. The changes object is empty. This effectively makes the endpoint create-only — we can't move prospects between stages via API.
2. No endpoint to update prospect metadata. There's no PUT or PATCH on /api/v1/pipeline_prospects/{id} (returns 404). This means we can't update next_contact, notes, probability, or rating on existing prospects. The GET response includes these fields, but there's no way to write to them.
3. POST /api/v1/files returns 500. We've tried both JSON and multipart form-data uploads with various field names (file, data_room_file[file]). All return {"error": "Failed to upload file"} with HTTP 500. We'd appreciate documentation on the expected request format.
4. No notes sub-endpoint. The prospect listing returns a notes array, but there's no POST endpoint to add notes (tried /pipeline_prospects/{id}/notes, /people/{id}/notes, /notes — all 404).

1. create_or_update_prospect tool — parameter mapping bug. The MCP tool schema accepts a people array, but the underlying REST API call expects prospects. Every call fails with: {"error": "param is missing or the value is empty or invalid: prospects"}. The create_multiple_prospects tool has the same issue.
2. Same limitation on updates. Even if the parameter bug were fixed, the MCP server calls the same REST API — so stage changes and note updates on existing prospects would still be silently ignored (per issue #1 above).

• A way to move existing prospects between stages via API (either fix the POST behavior or add PATCH/PUT)
• A way to add notes to prospects
• A way to update next_contact on prospects
• A working file upload endpoint with documented request format
• The MCP server people → prospects parameter mapping fixed

1. Call create_or_update_person with required fields: first_name, last_name, email
2. Observe the 400 response

HTTP 400 — {"error": "param is missing or the value is empty or invalid: people"}

• Same error occurs on create_or_update_prospect with valid pipeline_id, stage_id, and people array
• Tried both {"people": {...}} and {"person": {...}} wrapper formats via debug_api_request — both returned the account object instead of creating a record, suggesting the request body may not be reaching the endpoint correctly
• Read operations (list_pipelines, get_pipeline, list_people) work fine — issue is isolated to write/create operations