Generate and confgure an API Client with the required permissions for the APIs you will consume.

Configure the ODC Portal Domain. There are two ways to define the ODC Portal Domain in this library:

1. Configure the ODCRestAPIs settings on your consumer app with HTTPS and no path, example:
   • https://example.outsystems.dev
2. Fill the ODCPortalDomain input parameter on the Server Action (good for dynamic use cases, eg: when you have more than one ODC Portal to manage)

The first setting overrides any value sent on the input parameter of the exposed Server Actions.

Call the GetAuthorization Server Action to retrieve the token and use it to fill the Authorization input of the Server Actions.

Consume the Server Actions, the best way to find the action that you need is by searching for the endpoint patch you want to consume, example search:

GET /application-roles

This will return the available actions that implement endpoints with that method/path:

- ApplicationRole_Query (GET /application-roles)

- ApplicationRole_QueryUsers (GET /application-roles/{key}/users)