API Integration | texlytics

07/08/ 2026

Your Warehouse Is the Index the API Won’t Give You

A pull I had run cleanly for months started dying. Same endpoint, same code, same credentials. It would page through tens of thousands of AP registered invoices and then, somewhere north of 19,000 records, fall over. The frustrating part was the consistency. It did not fail randomly. It failed at the same place every time. That consistency turned out to be the whole story. By the time I was done, the ceiling had moved on me twice, and the most dangerous version of the failure was the one…

05/08/ 2026

Article V — Human Intelligence and texlytics Intelligence Systems

The texlytics Charter Series The Multiplication Principle Artificial intelligence is changing the way organizations work. Too often, however, the conversation begins with the wrong question. “How can AI replace this person?” At texlytics, we believe there’s a better question. “How can AI multiply this person’s impact?” People possess qualities that technology cannot replicate. Intelligence Systems possess strengths that people cannot match. The future isn’t choosing one over the other. The future is designing systems where each contributes what it does best. Our Guiding Question Before recommending any Intelligence…

26/06/ 2026

Stop Writing One Pipeline Per Source

This article was originally published on LinkedIn and is archived here on texlytics.com. Every data engineer hits this moment. You’ve integrated three systems, you’re proud of it, and then a fourth source shows up. So you do what you did the last three times: copy the previous notebook, find-and-replace the table names, tweak the date logic, adjust the pagination, ship it. It works. You now have four notebooks that are 80% identical and 20% subtly different — and that 20% is where every future bug will live. Then…

19/06/ 2026

The Bug That Reported Success

This article was originally published on LinkedIn and is archived here on texlytics.com. One of our customers didn’t exist. Not deleted, not archived — simply absent. A real company, with real invoices, that should have been sitting in our analytics layer like everyone else. It wasn’t. And the system responsible for bringing it in had run cleanly every night for weeks. Green checkmark after green checkmark. No errors, no warnings, no failed jobs. The whole time, it was quietly wrong. This is a story about why the bugs…

12/06/ 2026

Our ERP’s API returned different results for the same query. Here’s how we dealt with it.

This article was originally published on LinkedIn and is archived here on texlytics.com. Run the query at 9:00 AM. You get 4,812 rows. Run the exact same query at 9:01 AM. You get 4,797. Run it a third time and you get 4,812 again — the exact count you started with. Relief. Except that run is the most dangerous of the three, and I’ll come back to why. No data changed. No filter changed. Same endpoint, same parameters, same everything. Fifteen rows just evaporated, and they were different…

07/06/ 2026

How I Solved CMiC’s 429 Rate Limit Challenge

This article was originally published on LinkedIn and is archived here on texlytics.com. If you have ever built an integration against the CMiC Cloud APIs, you already know where this story is going. HTTP 429. Too Many Requests. Over and over. I pull CMiC ERP data into our Microsoft Fabric Lakehouse on a schedule, Bronze through Gold. The pipeline ran clean for months. Then one morning I walked in to find it already in full meltdown, runs failing on throttling across the board. Nothing had changed on our…

Category API Integration