Zuplo

API logs can expose sensitive data if not secured properly, leading to compliance violations and data breaches. Protecting this data is critical! Here are three key strategies to safeguard sensitive information in API logs: - Encryption: Converts data into unreadable formats using AES-256 or RSA, ensuring only authorized parties can access it. - Data Masking: Hides sensitive data by replacing it with fictitious values, preserving usability without exposing the original data. - Access Controls: Limits who can view or interact with log data using role-based or attribute-based permissions. You can learn about these techniques and other strategies in our latest blog ?? ??

Should you deploy your APIs to "the Edge"? I would argue at least some portion of your API infrastructure should be deployed to Edge servers, namely your compute-heavy tasks like request validation. Essentially all of the functionality that is in your API gateway or middleware that doesn't require a database lookup can be run at the Edge. Why? Well - you don't really have control over where your customers are going to integrate your API - especially geographically. If their end-users are in Japan, but your only datacenter is in US_EAST - they are going to have horrible latency. To remedy this, performing as much work as possible as close to the user as possible is ideal - much of an API's job consists of validation, auth, and traffic control. Check out this clip of a talk I gave on building APIs at the Edge - full version ??

Do you know what "the Edge" is? Maybe a better question might be "where is the edge". If you've ever used serverless infra like AWS Lambda before - you might be familiar with the idea of your code being distributed to multiple regions to minimize latency. Edge computing takes this to the next level, distributing your code to "Edge servers" - essentially devices that run your code as close as possible to your users. Many CDN providers like Akamai and Cloudflare let you run your code at the CDN-level, which is typically much closer to your users than some regional AWS datacenter (CF has over 300+ edge locations). This provides the lowest latency connections to your users, but comes with some tradeoffs, explained in the video below: This is actually an excerpt from a talk on the Edge and building APIs at the Edge - you can find the full talk ??

LLM generated OpenAPI documents should be scored and validated as part of your prototyping lifecycle. More on this, and a full prototyping lifecycle demo in our latest video with Martyn Davies Emmanuel Paraskakis: https://lnkd.in/epa4WNtj

Another week, another batch of wonderful updates for Zudoku! ? Here's a selection of what's new: New & Improved: ?? You can now authenticate users using Supabase! ?? New config option to control the visibility of the version selector in the UI Docs: ?? How to set up and configure Pagefind Bug Fixes: ?? Fixed an issue with the OIDC redirect logic Zudoku is an open-source, OpenAPI-powered, customizable API documentation framework for building quality developer experiences. ?? Get started building (or contributing) at https://lnkd.in/eK34W6Ng ???

Are you debating between using Deepseek or Gemini for your next vibe-coding session? The capabilities of their models and APIs are quite different - so you need to be careful when choosing. Some important considerations include: - Cost - Data Security - Customizability - Latency/Performance Luckily for you, we just produced guides for both of these APIs: Gemini API Guide: https://lnkd.in/eSefQxDa DeepSeek API Guide: https://lnkd.in/eNEU6hGT

Prototyping an API with an LLM and free tools such as Rate My OpenAPI, Mockbin and Swagger Editor can get get you from idea to actionable developer feedback in minutes. API industry veteran Emmanuel Paraskakis demonstrates the API lifecycle workflow he's developed to get actionable feedback on APIs, fast. Including: - The prompt engineering needed to generate a high quality OpenAPI Initiative document - Validation and how to hit a high score on Rate My OpenAPI - Mocking the API for developer consumption and feedback Take a few minutes out of your lifecycle to check this out: https://lnkd.in/epa4WNtj

We had a great time at Fintech Meetup, helping Fintechs and Financial Institutions understand the power of building high-performance APIs that developers love. Here's some of our takeaways - Build vs Buy: Many fintechs and FI's prefer to build solutions in-house for privacy or security reasons, but this approach faces challenges as maintenance costs and adaptation to regulation proves challenging. Many are transitioning to secure cloud solutions. - Open Banking: Section 1033 will likely drive many community banks to adopt APIs, which is a huge shift given only 21% of them currently offer APIs. For banks that already offer APIs, new standards will provide an opportunity to look at their APIs and capabilities relative to competitors. - API Developer Platforms: For more mature FI's and Fintechs, having an API is no longer enough. Banks like JP Morgan are building out full API developer platforms to position themselves as market leaders and drive innovation in the fintech space. Many fintechs are also directly monetizing their APIs, providing solutions like cross-border payments and fraud detection. Overall, we expect API development and usage to grow substantially in the US over the next few years - so expect to see us at more fintech conferences in the future!

Zudoku update time! It's been a busy week. Here's SOME of what's new: New Features & Improvements: ?? Added a new Pagefind search plugin ?? Vastly improved prerender performance, significantly reducing build time for extremely large projects (Like, really huge ones. Try it, we dare you!) API Playground Enhancements: ?? Added ability to ask users to sign in if required ?? Prompt users for their API key when submitting requests without one ?? Ability to cancel a request once it's been made ? Disable code highlighting for large responses to speed up the UI Bug Fixes: ?? Fixed auth redirect for the Clerk.com plugin Zudoku is an open-source, OpenAPI powered, customizable API documentation framework for building quality developer experiences. Get started building (or contributing) at https://lnkd.in/eK34W6Ng

More chip than salsa? The latest episode of The API & Anchor is all about Model Context Protocol. Watch the full episode here: https://lnkd.in/gBEXGpDY