What We Learned Asking 5 Dev Agencies to Build a Python SDK for Our API

We asked five dev agencies to quote and build a Python SDK for our API. Here’s what we learned so you can skip some of the mistakes we almost made.

Two agencies gave us quotes that were all over the place. The fix: we wrote a short spec. We listed endpoints to cover, auth (API key in header), target Python versions, and that we wanted type hints, a README, and publish to PyPI. Once we sent that, quotes aligned and we could compare apples to apples. Don’t skip the spec.

One agency said “we do Python” but their “SDK” was a thin wrapper with no error handling or docs. We asked: “Have you published a package to PyPI or built an SDK for a REST API?” and asked for a link. Two couldn’t provide one; we dropped them. Always ask for proof.

We’re in the US; two agencies were in India. The one we chose had a clear process: async updates, a weekly call at a time that worked for us, and a single point of contact. The other was slow to reply and we had to chase. Agree on response times and overlap before you sign.

We wanted the repo in our org and PyPI under our account (or a clear transfer). One agency wanted to “deliver a zip” and keep the repo. We passed. Define handover and ownership in the contract so you’re not stuck later.

We asked each finalist: “Build one endpoint (e.g. get_resource) and a README. Paid pilot.” Two did it; we picked the one whose code and docs we liked. The full SDK then felt low-risk. If you can, do a paid pilot before the full build.

We ended up with a team in Bengaluru (Hendoi Technologies) that had shipped Python SDKs before. Clear spec, proof of experience, and a pilot made the difference. If you’re looking for a Python (or TypeScript) SDK for your API, get a spec in place and ask the right questions. We’re happy to share more—contact us.

📞 +91-9677261485 | 📧 support@hendoi.in | Contact us