MuleSoft

Are you looking at all the new AI tools and wondering how you can connect them to your powerful, battle-tested APIs? You’re in the right place! In this walkthrough, we’ll enhance an existing Salesforce System API by implementing the Dual-Exposure Pattern. This is a fancy way of saying we’ll make your API “AI-ready” by adding a new, smart entry point for AI agents without breaking your existing RESTful interface. We will expose three core operations—create a case, get case details, and update a case—as discoverable AI tools, all from the comfort of Anypoint Code Builder. ...

Imagine a world where your AI applications can effortlessly connect to and use any tool or data source… without needing a deep dive into complex, custom API documentation every single time. Right now, connecting Large Language Models (LLMs) to the tools they need often looks like a tangled web of custom, brittle integrations. 🕸️ Every new tool requires another piece of unique code, creating a bottleneck that’s complex and prone to errors. ...

In REST APIs, we often need to get a single resource. In this article, we explore how to structure those GET requests properly. 🧍‍♂️ Get a Single Account by ID To get one specific account, use: /accounts/{id} Example: /accounts/adoe This will return the account with ID adoe. You can apply the same idea to other resources, like: /applications/872233 🧠 Get Resource(s) by Field Value Sometimes you want to retrieve a resource or a small list of resources based on a specific field, like email or region. Instead of creating multiple endpoints, use query parameters. ...

When designing APIs, the GET method is one of the most commonly used HTTP methods. It’s used to retrieve data, either as a full list or a single resource. In this article, we focus on getting collections of resources. 🔍 Use Case Let’s say we’re building a service that allows users to manage accounts. We want to allow users to: List all accounts 📄 Designing the Endpoint Use a plural noun for the resource name: ...