Manage Portal Applications

Overview

Applications are the credential-bearing objects portal consumers use to call APIs. Each application has a clientId / clientSecret pair and can hold multiple contracts against published APIs. This workflow covers the application lifecycle from a portal-consumer perspective: inventory, name-availability check, create, update, secret rotation, and deletion.

What you'll build: A clean application portfolio with the credentials you need to consume portal APIs.

Prerequisites

Before starting, ensure:

1. Authentication ready

   • Valid portal-consumer Bearer token
   • Membership in the portal

2. Portal context known

   • targetOrganizationId — Anypoint organization hosting the portal
   • portalId — the portal you are a member of