API Design with MuleSoft | Salesforce Trailhead

#salesforce #trailhead #salesforcetrailhead #salesforcecertification API Design with MuleSoft : https://www.youtube.com/playlist?list=PLqIjn-zAqU7IMP9kCyo9M5BEJ-jMVTS5J Once your API is published in Anypoint Exchange, you can configure who has access to it. You’re still in full control. By default, published APIs are private, meaning only the owner can view and access the asset. To make an API publicly discoverable, you can change its visibility setting to public, allowing anyone with the URL to view the API portal and documentation. These settings can be adjusted at any time, which simplifies access management as your API evolves from internal testing to external collaboration. Changes take effect immediately and can be updated at any time. Note A public API doesn’t mean unrestricted access. You can still protect actual runtime access with authentication policies like client ID enforcement or OAuth—topics you’ll explore in the next badge. Create and Customize API Portals Once your API is published and visibility is set, the next step is to help others discover and use it successfully. An API portal is a web-based experience built into Anypoint Exchange. It serves as a friendly front door to your API, and it provides everything developers, partners, or teams need to understand, test, and adopt your API with confidence. A strong portal turns a technical spec into a welcoming, useful resource. It’s your API’s first impression—and often the difference between confusion and successful integration. 00:00 Introduction 00:12 Discover Application Networks 00:49 Define APIs with OAS 01:30 Explore a Mock-Ready API 02:16 Mock and Test APIs 03:18 Publish and Share APIs