Table of Contents

Search

  1. Introduction to API Manager
  2. Administration
  3. API-specific policies
  4. Managed API groups
  5. Organization policies
  6. Analytics

API Manager Guide

API Manager Guide

Viewing and editing managed API groups

Viewing and editing managed API groups

Use the API Groups page to view and edit managed API groups.
To view or edit details of a managed API group, double-click the group name. The Group Details window appears and shows the managed APIs in the group in alphabetical order. The following table describes the properties that appear in the Group Details window.
Property Description
Name Name of the group. The name is case sensitive and must be unique in the organization. The name can contain up to 250 characters, including any letter on the ASCII table, non-Latin characters, any digit, and the special characters . _ and -. The name cannot contain spaces or any of the following characters: " ~ ! @ # ; : % ^ . & * + = { } ( ) | < > , ' / \ $
Context Group context. API Manager adds the context to the API URLs of the managed APIs in the group.
Note the following guidelines:
  • Group context must be unique.
  • The context cannot be identical to the name of a managed API, or to the combination of an API name and any of its versions. Also, the combination of the group context, API name, and version of any managed API that belongs to the group cannot be identical to any other URL context in the organization. For example, if you want to create a group to contain version b of managed API a, the following restrictions apply:
    • The group context cannot be /a/b.
    • If b is the default version of a, the group context cannot be /a because the API context of the default version can either include the version or not, and thus can be either /b/a or /a.
    • If b is not the default version of a, you can create a group with context /a, because the API context the non-default version always includes the version and is thus /a/b.
  • The context is case sensitive.
  • The context cannot contain a /t/ segment because this segment is reserved for Informatica internal use. For example, the context cannot be /a/t/b.
If you add a context to an existing group, API Manager adds the context to the API URL of all the managed APIs in the group. Inform API consumers of changes to the API URLs.
Description Description of the group.
JWT Access Token JSON web token for the group. You can use the token to invoke any managed API in the group that uses JWT or JWT and Basic authentication.
APIs in Group APIs that belong to the group.
If you remove a managed API from a group with a context, API Manager removes the group context from the API URL of the managed API that you remove the group. Inform API consumers of changes to the API URLs.


Updated December 31, 2019


Explore Informatica Network