![]() ![]() OutSystems jumped on this opportunity and posted its available APIs there, including: All you need to do is put your tokens or passwords on the variables, and you’re all set. Want to connect to RESTs from Linkedin, Twilio, Facebook, OutSystems Lifetime API? It’s all in there, in one place! You can have an entire library loaded and ready to go. You have your average Jane or Joe sharing their implementations of APIs, but you also have official APIs. A buffet of APIs implemented by different people. An open-source marketplace with thousands of collections shared with everyone. Postman’s API Network has thousands of collections and workspaces that you can consume. I installed the latest desktop client version and discovered a brave new world of APIs and libraries to consume. A developer seeks these small comforts in their work.įret not, for Postman came once again to the rescue of my little annoyances with the API Network. The thrilling sensation of replacing a four-step operation with a simple combination of keys, turning a three-second action into an instant move. (I admit that I have had long discussions with developers about their favorite shortcuts on Service Studio.) ![]() Every developer loves finding the shortcut instead of clicking two or three times. I would switch back and forth between these tabs, losing service in a mess of opened pages (I’m one of those that ends the day with 30+ tabs).ĭon’t get me wrong their documentation is good, and I might sound too nitpicky, but that’s how I am with my tools. If I wanted to connect to, say, Google or Linkedin, I would have their APIs documentation spread across multiple tabs in my browser for days. Happily progressing through my career.īut once in a while, I still had to look up for services of public APIs on their respective sites. Discovering the Postman API NetworkĪnd there I was, using Postman to consume RESTs in OutSystems in more complex use cases. RESTs, the great equalizer of services - Postman, the great equalizer of documentation. Postman appeared to support, document, and test what was produced. A common language that a developer can use to expose and consume information. REST services appear as a versatile and simple solution to communicate between different systems. The steps were always the same, and everything was always in the same place. But the examples were always for very specific use cases, very customized, plus each provider had its way of showing the information.īut with Postman, the experience was always consistent. I’m sure you understand.īefore discovering Postman, I had used APIs that included examples on their homepage and even a cool JavaScript to try out the REST services in the API portal. When developing, I’ve always preferred to get my hands dirty and use a try-and-error approach than to go through lengthy documentation scrolls carefully. I found it easy to open the collection in Postman, check the services and their parameters (what headers were needed, what filters in the URL, the response payload, etc…), and implement the REST API in OutSystems. Later, I started working on POCs where the customer would share a Postman collection. But for edge cases, when something was missing or not working, Postman was a great complementary tool to better understand the requests, their headers, and payloads.īut as I soon realized, I was only scratching the surface of Postman.īeing the lazy developer I am, I would have only one collection and one service that I would change according to whatever API I was testing. Exploring an Iceberg Called Postmanįor most REST integrations, I was able to implement and test them in the OutSystems IDE. So I wasn’t surprised when I first discovered that there was a tool to test RESTs. Tools to manage time, tools to manage tasks, tools to optimize paper, tools to test code, tools to write code - tools, tools, tools! The good news is that there are tools for pretty much everything. So I had to dive into the wonderful world of REST requests.Īs a carpenter needs a hammer and an accountant needs spreadsheets, developers need their tools. ![]() Many of these POCs required us to connect to REST APIs, some with custom integrations with third-party services like Facebook or Twilio. Throughout my career, I worked on many proof of concepts (POCs) and projects for many companies. I was getting familiar with front-end and back-end, and soon enough, I was working with REST integrations. I started developing in Java and changed to OutSystems in 2015, where I began developing web applications on a path to become a full-stack developer. I have been a developer for almost a decade (est. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |