Ctrl + K
Community Member

Hi team,

We're integrating with the DecileHub API (v1) and MCP server programmatically to manage our investor pipeline. We've hit several issues — some appear to be bugs, others may be missing functionality. Wanted to flag all of them in one place.

REST API Issues:
  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).
MCP Server Issues (https://decilehubmcp.com/mcp):
  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).
What we need:
  • 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

Thanks,
Mike 
3 replies
Community Member
Hey Mike!

I have updated the POST files API to have clearer error messages when request parameters are invalid, and have updated the documentation for that API to hopefully make it a little clearer.

To update a prospect, you can use the POST api/v1/pipeline_prospect endpoint. The prospect will automatically match based on email (for a person) or name (for an organization). I understand that this is slightly obtuse and we have room for improvement on that API but in the meantime it should work OK. It does accept a `note` field that allows you to add a note.

It's been a while since we created this API, but it was an intentional decision to not change stage_id in it because bad/annoying things can happen if a prospect inadvertently changes stage. I'll figure out a clean and explicit way to allow moving a prospect through stages and will let you know when that's done 🙂
Community Member
@Mike Plichta  Check the updated API docs, hopefully the updates there cover your API needs!

Log In or Sign Up

Please Log In, or Sign Up to participate in the discussion.

Apply to VC Lab Cohort 21

Get full access to Decile Base and the Decile Hub venture platform for free by joining the VC Lab program.

Apply to VC Lab Cohort 21