1
I wrote this review for Merge.dev back in 2023 and gave them a 1 star review since I felt like their API really wasn't that great. Unfortunately I wrote it with a company email, and I left that company a week after I wrote the review.
Obviously I no longer have access to the email that I wrote the review with and you can tell as well since the review user icon has a cross through it since the account was deactivated. However it seems the review was edited in January of this year to a 5 star review which is complete bs
Anyone know a way I can get in contact with G2 cause this is beyond shady and I wouldn't be surprised if they let companies pay for reviews to be edited at this point.
How is this legal and is there any way I can get this fixed?
- Their entire scheme is just possibly undefined return values - Any custom data beyond just the basics are under a remote_data key that their docs don't even explain and just says "Varies by platform". Like at least tell us what each system could return cause otehrwise we have to manually QA every single HRIS/ATS anyways.
- The system doesn't even do any ETL. You still have to ETL and paginate through the system yourself. It's the lightest API wrapper ever that doesn't have a great schema.
- Their new SDK is much better generated but they didn't provide any legacy migration guides and their old sdks required us to fork their repo and build our own solution
- Honestly it seems like the only reason I've had to use Merge's API is because our CEO was friends with the Merge CEO
Some of my complaints:
1. Hubspot released Sequences 10 years ago, and somehow they still don't have API suppport.
2. Meanwhile if I need to fetch associations between objects I have to use their V4 associations API but if I want to fetch contact lists I need to use their V1 API, and to fetch contacts themselves I sometimes have to use a V1 API and sometimes a V3 API. Who is versioning all of this
3. It's 2024 and somehow none of their APIs support sorting, ordering or filtering and to do so you need to use their /search endpoint. The problem is there's a 4 requests per second rate limit on the endpoint. That leads to my next complaint
4. A 4 rps limit is fine, if HubSpot allowed you to have an individual user go through oauth, but for some reason they suggest and push you to authenticate only 1 super admin, which means if you have 10+ users the search endpoint is pretty much useless and needs to be throttled significantly
There's so many other issues with fields that should be deprecated but aren't, fields getting deprecated and the only answers being some community message 5 years ago, lack of API support for workflows and other new features, and there's even issues where I noticed we'd get small bursts of 401's for no reason and Hubspot's response was that when they rotate the credentials used to verify tokens it can cause temporary downtime daily.