Yasharth Mishra

Knit API - 1 to Many API for all customer-facing Integrations

byβ€’
Single API that helps you integrate with 25+ HR, chat & recruitment systems in one go πŸš€ Start with our free plan to scale your native integrations rapidly. No initial commitment required. Sign up at app.getknit.dev/signup

Add a comment

Replies

Best
Yasharth Mishra
Hello Product Hunt, I am the co-founder of Knit API along with Gaurav and Kunal. We faced the pain of 1:1 integration development while working on an HRTech venture. To remain relevant in the hypercompetitive space of HRTech, we had to scale integrations exponentially at the cost of core product enhancement. Each new ad-hoc integration requests took our engineering team’s focus away from the core product for a few weeks up to a few months. Our CX and sales teams also spent significant time addressing integration related queries. We soon recognized that this is a struggle faced by most SaaS companies out there. And SaaS founders like us are looking for a solution that solves this problem well. So, we did what we knew good founders should - make something people want πŸ™‚ In Jan 2023 we started building Knit - A unified API for B2B integrations. Today, we are excited to share with the Hunters community that in this little time, with a highly talented team, we have not only built our product from scratch, but also added 20+ integrations with various HRMS/Payroll systems, ATS, and Slack & Teams. Now, you need to integrate only once with the Knit API, and we will then build and maintain (& scale!) all your integrations for you. With our initial offering, you get to offer your customers key integrations with top HR & recruitment tools like BambooHR, Rippling, Zenefits, SAP SuccessFactors, Lever, Greenhouse and many more. You can also build interactive Slack/Teams bot with Knit. We plan to keep expanding our existing catalog as well as include other categories to our integrations portfolio based on customer requests. Our goal with Knit is simple: help SaaS businesses scale their integrations faster. We enable this with cool features like β€” βž• Webhook architecture for near real-time data syncs βž• Push based data-sync model so no polling infrastructure is needed at your end βž• Embeddable auth component which is built as a true web component for easy customizability βž• Integration management dashboards to make it easier for your CX team to solve customer issues without getting engineering involved βž• Passthrough requests to the source system for access to data fields we have not covered βž• Ability to read and map custom fields in source systems via DIY dashboards for the frontline CX teams βž• and many more… So, what makes Knit different from other unified APIs in the market? Our secret sauce is the way we have architected a 100% event-based solution that does NOT store a copy of your customer data. Employee data being PII, this method of data handling can go a long way toward building trust among your customers, And when customers feel happy, you sign more deals, you get happy, and so we get happy πŸ™‚ So if you’ve ever felt that limited integrations is a barrier to your expansion plan, or that you are stuck with limited resources to expand your integration portfolio, and are looking for a solution which has kept data security concerns at the forefront β€” you should definitely try Knit. For more information, visit our β€” βœ… Documentation: https://developers.getknit.dev/ βœ… Integration catalog: https://www.getknit.dev/integrat... Finally, the entire Knit team is here for you to get your queries solved. Feel free to ask any question you may have about the product or integrations in general.
Ozan
@yash_knit Congrats on the launch, Yashart! Exciting project.
Yasharth Mishra
@irturko Thanks so much Ozan!
Calvin KE
@yash_knit congrats for the launch waiting for more projects
Yasharth Mishra
@calvin_ke Thanks so much Calvin! We'd definitely keep you posted on all our launches
Gabe Moronta
@yash_knit congrats on the launch!
Irina Haupt
Congrats on the launch, this looks exciting! πŸš€ How do you handle data security concerns when dealing with PII of users?
Gaurav Bhawnani
Thanks @irina_haupt To take care of the security concerns - Knit doesn't store any users' data - Knit acts as a passthrough only. Knit shares data using a data pipe, also called sync. The data pipe once opened will always pump data to your system, and will never store any of the data in Knit's database. Apart from this we also have all the security compliance in place - SOC II, GDPR and ISO
Sudeshna Roy
@irina_haupt Hi Irina. Thank you for your support :) In order to ensure complete data security of user data, we have built a 100% event driven webhook based architecture. We are the only Unified API in the market at the moment that does not store a copy of customer data on its database beyond API Keys/ Access Tokens. You won't have to worry about customer data security breach with Knit at all :) Plus we are ISO27001, SOC2 type 2 and GDPR compliant.
Irina Haupt
@sudeshna_roy @guravus Thank you both for your responses and for making things clear and transparent. This should definitely alleviate your users' security concerns! Great workπŸ™Œ
Vijayanand Kailash
Go-to-market is super easy now for HR tech with Knit! Awesome @knit-api team!
Sudeshna Roy
@knit @vijay_anand5 Thank you so much for your support :)
Gaurav Bhawnani
@knit @vijay_anand5 Thanks @vijay_anand5 We wouldn't want to have anyone lose a deal for integrations :)
Kunal Mishra
@knit @vijay_anand5 Thanks Vijay! We were earlier building an HR-Tech startup, so felt this pain acutely and thought of solving for it via Knit.
Vijayanand Kailash
@knit @kunalsmishra We are facing this issue at present. Definitely, we will go with Knit in the very near future.
Vijayanand Kailash
@knit @guravus I like your vision for Knit.
Shikhar Saxena
Will it be useful for CRM & Customer Support integrations as well?
Yasharth Mishra
@shikhar0132 Definitely Shikhar. CRM integrations are in the product roadmap for May and Customer Support will follow soon. Any specific ones which are of interest to you?
Shikhar Saxena
@yash_knit Cool, we were considering FreshChat for our customer support queries.
Igor Pavlov
Amazing project! How often do you guys update the integrations, in other words, can we be sure the integrations are all up to date?
Kunal Mishra
@igorpavlov Hey Igor, we run automated checks daily on all our integrations. As soon as we identify any breakages, we get them fixed asap. So you can rest assured that integrations are always up to date on Knit.
πŸ’‘ Bright idea
Congrats on the launch. From the landing page, I think that it's a tool for developers to integrate multiple platforms with API. If incase, you're also targeting people in HR or customer-facing domains to also understand the product, a simple narrative without much jargons might help. Having clear narrative for the user persona will help your target audience if the tool is right fit for their needs.
Akshat Jain
@nithincp Thank you so much for the feedback and support! We've also found that using simple and concise narratives helps everyone understand the product better. We'll definitely incorporate your feedback!
Sudeshna Roy
@nithincp That is a really valuable feedback Nithin. Thank you so much for taking the time to share this with us. We would surely keep this in mind πŸ™
Nick Vas
πŸ’‘ Bright idea
Congratulations on your launch! Knit API seems like a great solution for SaaS companies struggling with the process of scaling native integrations for their product, without compromising data security. What are some of the key features of Knit API that make it stand out from other unified APIs in the market, and how do they ensure data security?
Yasharth Mishra
@cata Thanks so much Nick! Here are a few of Knit's key differences from competition: 1. Knit doesn't store your users' data: Knit acts as a passthrough only. Knit shares data using a data pipe, also called sync. The data pipe once opened will always pump data to your system, and will never store any of the data in Knit's database. Competition stores data in its database. When you make any API call to retrieve your users' data, the data is served to you from this database and not from the provider(HRIS/ATS/CRM etc) system. Storing your user's data with a 3rd party can lead to unwanted security concerns and affects deal closure in our past experience. 2. Push based: Knit is event driven and delivers data to your backend via webhooks. Most major read operations like syncing employee data from HRIS or job/applications data from ATS or leads data from CRMs on Knit happen via webhooks only. With a webhook driven approach, Knit's users do not need to maintain a separate polling infra. Competition is primarily operating on pull approach where the onus is on the user to make API calls to get data. With this approach, users need to maintain a separate polling infra to handle data freshness. If you compare that with Knit, you'd need to only write a new API handler for Knit in your existing backend server code and expose the API endpoint as webhook, no new infra headache. 3. We provide a highly customizable pure web front end authorization component. Since this auth component is embedded into your application, it needs to look and feel similar to your APP. Competition provides iframes which are not so customizable. 4. Modular data models: you can pick and choose the data that you need. With competition you get all the data synced, you can't control which data to sync or ignore. Other than wasting resources, this also at times leads to customer concerns around data handling.
Yasharth Mishra
@cata And by the way we are also SOC2 & ISO certified :)
Max T.Pham
Congrats on the launch, Knit API team! Your platform is a game-changer for quickly and efficiently scaling integrations. It looks like the Zapier of the Customer API world. You got my upvote, good luck!
Sudeshna Roy
@maxtpham Thanks a lot Max. We hope to make the integration game super simple! πŸš€
Gaurav Bhawnani
@maxtpham Thanks for the kind words. Means a lot! We're trying to build the most secure embedded integrations platform out there.
Doğukan Tezcan
Congrats on the launch!
Sudeshna Roy
@dogukan_tezcan Thank you for your support πŸ™‚
Akshat Jain
@dogukan_tezcan Thanks for your support, Doğukan!
Congratulations on the launch! How long have you been developing Knit API?
Yasharth Mishra
@kate_bovkunova Thanks so much Kate! We have been building Knit since Jan of this year. So almost 4 months now!
123
β€’β€’β€’
Next
Last