HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
poozlehq
poozle
TypeScript2023–2023
poozlehq / poozle

poozle

A single API for product integrations

5Distinct people
10Mentions
0Explicit recommenders
606GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A single API for product integrations

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 5:04:15 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week10 dated mentions

Observed mentions: 2023-04-11 14:59:51 UTC to 2023-08-18 20:41:46 UTC. Weeks start Monday, UTC.

01232023-04-10 00:00:00 UTC to 2023-04-17 00:00:00 UTC (exclusive): 3 mentions; 3 submissions, 0 commentsApr 102023-04-17 00:00:00 UTC to 2023-04-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-24 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-05-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-08 00:00:00 UTC to 2023-05-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-15 00:00:00 UTC to 2023-05-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-22 00:00:00 UTC to 2023-05-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-29 00:00:00 UTC to 2023-06-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-05 00:00:00 UTC to 2023-06-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-12 00:00:00 UTC to 2023-06-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 122023-06-19 00:00:00 UTC to 2023-06-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-26 00:00:00 UTC to 2023-07-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-03 00:00:00 UTC to 2023-07-10 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-07-10 00:00:00 UTC to 2023-07-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-17 00:00:00 UTC to 2023-07-24 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-07-24 00:00:00 UTC to 2023-07-31 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-07-31 00:00:00 UTC to 2023-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-07 00:00:00 UTC to 2023-08-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-14 00:00:00 UTC to 2023-08-21 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsAug 14

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 102023-04-10 00:00:00 UTC2023-04-17 00:00:00 UTC330
Apr 172023-04-17 00:00:00 UTC2023-04-24 00:00:00 UTC000
Apr 242023-04-24 00:00:00 UTC2023-05-01 00:00:00 UTC110
May 12023-05-01 00:00:00 UTC2023-05-08 00:00:00 UTC000
May 82023-05-08 00:00:00 UTC2023-05-15 00:00:00 UTC000
May 152023-05-15 00:00:00 UTC2023-05-22 00:00:00 UTC000
May 222023-05-22 00:00:00 UTC2023-05-29 00:00:00 UTC000
May 292023-05-29 00:00:00 UTC2023-06-05 00:00:00 UTC000
Jun 52023-06-05 00:00:00 UTC2023-06-12 00:00:00 UTC000
Jun 122023-06-12 00:00:00 UTC2023-06-19 00:00:00 UTC000
Jun 192023-06-19 00:00:00 UTC2023-06-26 00:00:00 UTC000
Jun 262023-06-26 00:00:00 UTC2023-07-03 00:00:00 UTC000
Jul 32023-07-03 00:00:00 UTC2023-07-10 00:00:00 UTC211
Jul 102023-07-10 00:00:00 UTC2023-07-17 00:00:00 UTC000
Jul 172023-07-17 00:00:00 UTC2023-07-24 00:00:00 UTC110
Jul 242023-07-24 00:00:00 UTC2023-07-31 00:00:00 UTC110
Jul 312023-07-31 00:00:00 UTC2023-08-07 00:00:00 UTC000
Aug 72023-08-07 00:00:00 UTC2023-08-14 00:00:00 UTC000
Aug 142023-08-14 00:00:00 UTC2023-08-21 00:00:00 UTC211

What Hacker News says

3 sources

Show HN: Integrate third party APIs with ease using GraphQL

We built Poozle (an open source platform) to simplify API integrations. Instead of dealing with multiple providers with different syntax and requirements, our platform offers a standardised interface through GraphQL. Why we built this: 1. In our previous jobs, we did many integrations and found no standardisation to the process. 2. Existing Unified API solutions lack customizability and only work for integrating multiple integrations from one vertical. Our beta version includes: 1. Plug n Play Integrations: Choose an integration from our pre-built list and start using it. 2. Playground: Write a GraphQL query to retrieve a response from the API. The playground includes API documentation for easy discovery and testing. 3. Integrate with your codebase: Seamlessly talk to all the APIs from your codebase using a unique URL provided by Poozle.
Read the rest
4. Observability: Our monitoring dashboard tracks API usage, latency, and error rates for quick incident detection. We're still early, so we would love your feedback and opinion. Also, let us know if you need a specific API integrated. Main Website: https://www.poozle.dev Product Demo: https://www.loom.com/share/1d93d082e97f4ef0be5035644e9823dc
9 points · Open discussion

Show HN: Open-source platform to Standardise API Integrations using GraphQL

Founder here, Poozle integrates different APIs [Gmail, JIRA, Github, Salesforce, Pipedrive, Slack etc.] and provides a single GraphQL layer to integrate third party APIs and perform CRUD operations. In our previous jobs, we did many integrations, but we found that there is no standardization to the process. We had to write separate authentication code for each application, and for some applications, we had to integrate via APIs because the SDKs were stale. We also found that some integrations were completed quickly, while others took longer. Started working full time on this idea from Jan’23 but the real progress have happened in the last 7 weeks.I strongly believe open source is the only way to create standardisation for API integrations.
6 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.