Your API Builds Are Boring (Until Now)


Extract. Transform. Read.

A newsletter from Pipeline: Your Data Engineering Resource

Hi past, present and future data professional!

Tired of playing with the same 3 APIs? At the end of this email you’ll find a list of 13 offbeat APIs to make ETL interesting again.

But before you make your first request, read my cautionary tale of accidentally racking up $300 in charges on 1 API. Clearly, APIs can seem like black boxes offering unlimited data; to efficiently access that data, you need to think about how you’re “talking” with your API service. If you receive one too many “unauthorized” errors, you may not be reading the docs closely; this guide tells you to approach API documentation reading like an SAT reading comprehension test.

Before Reddit started acting like a budget airline carrier nickel-and-diming customers, it offered an API perfect for beginning developers. Finally, if you want to go beyond ETL, you can do so much more with APIs, like reading and deleting emails (except this one, I hope!).

Get your offbeat API guide here!

If you’re like me and are undefeated in IT phishing tests, here are this week’s embedded links:

Thanks for ingesting,

-Zach

Extract. Transform. Read.

Reaching 20k+ readers on Medium and over 3k learners by email, I draw on my 4 years of experience as a Senior Data Engineer to demystify data science, cloud and programming concepts while sharing job hunt strategies so you can land and excel in data-driven roles. Subscribe for 500 words of actionable advice every Thursday.

Read more from Extract. Transform. Read.

Hi fellow data professional! Once thought to be a purely back office role, data engineering is undergoing a radical transformation and gaining a new responsibility: Front-end deployment. The folks already deploying applications in this capacity are known, incidentally, as forward deployed software engineers or forward deployed engineers (FDEs). Before you worry about needing to learn JavaScript or other web programming paradigms, know that I’m referring to the preparation, deployment and...

Hi past, present or future data professional! As time in 2025 dwindles, I wanted to share what I learned about optimizing design, development and troubleshooting time while working 3 days per week this fall. Quick background: If you’ve been a long-time reader, you’ll know that in March my wife and I had our first child. Consequently, through my employer, I was eligible for several months of parental leave. Anticipating my wife’s return to work (after much needed time off!) I allocated the...

Hi past, present or future data professional! As the winter holidays approach, we’re entering a period of downtime for most orgs. Assuming your employer has hit goals (or accepted losses), allocated coverage for the slew of inevitable vacation requests and maybe even entered a “code freeze”, you’re entering data & tech’s slow season. If you’re working, during this time you may be asked to do any number of “downtime” (actual free time, not data outages) tasks ranging from code refactors to...