Just wrapped up my mandated 30-day evaluation of ProofHub for a client who was enamored with the "flat pricing" promise. I was tasked with mapping its API and webhook capabilities against their existing marketing automation stack. Let's just say the documentation was... aspirational, and the reality is a patchwork of half-implemented features that crumble under any integration load.
The core issue is an API that feels like an afterthought, bolted onto a monolithic application. Here’s a taste of what passes for a "RESTful" endpoint to add a task, which requires you to already know the internal mapping of list IDs to project IDs—a relationship not exposed in a sane manner.
```http
POST /projects/{project_id}/tasklists/{list_id}/tasks.json
{
"task": {
"name": "API Task Creation Nightmare",
"description": "
Good luck syncing this.
",
"assignees": "user_id_1,user_id_2",
"start_date": "07/30/2024",
"due_date": "08/30/2024"
}
}
```
Notice the delightful date format and the assignees as a comma-separated string. Now, try to update that task's dependencies or custom fields via the API. I'll wait. The webhook system is equally underwhelming: a paltry six event types (`task.created`, `task.completed`, etc.), no retry logic visible on their end, and payloads that omit crucial references. We had to build a middleware layer just to re-query ProofHub for the full resource on every event—turning a simple notification into a dual call pattern.
The promised "third-party integrations" are mostly pre-built, point-to-point widgets with minimal configuration. Need to sync detailed time entries to an external ERP? Hope you enjoy screen scraping. The granularity of access controls, especially for guest users, is so coarse that you're left with an all-or-nothing choice that violates basic data governance principles.
* **Data Synchronization:** A non-starter for bi-directional sync. The `PUT` and `PATCH` operations are inconsistent across resources, and field mapping is a manual guessing game.
* **Automation Rules:** Internal "automations" are basic IF-THEN triggers with no external event listeners. You cannot trigger a workflow from an inbound webhook, which defeats the purpose of an iPaaS-centric strategy.
* **Reporting APIs:** Essentially non-existent. Want to pull a burndown chart or custom resource report into a dashboard? Your only official path is CSV export and manual upload.
In the end, we're recommending against it for any organization that requires more than a closed-loop task board. The flat fee is a siren's call for budget-conscious managers, but the integration tax you'll pay in developer hours and middleware complexity is staggering. It's a silo, and not a particularly well-constructed one.
APIs are not magic.
That comma-separated assignees field is a real red flag. I've been looking at a few project management tools for a small team and the flat pricing thing is tempting, but hearing about that API makes me wonder how much of the design is actually modern. Did you run into any issues with the rate limiting on that API? Or did it just fall over under load before you could test that?
Yeah, that API structure sounds painful. The date format alone would break any automated sync I've tried to set up. How did you even find the mapping between list IDs and project IDs? Was it just trial and error?