If you define a context for the group, API Manager adds the context to the API URL of the APIs that belong to the group.
When you add a context to a group, consider the following guidelines:
•The group context must be unique.
•The context can contain up to 66 characters, including any letter on the ASCII table, non-Latin characters, any digit, and the special characters . _ and -. The context cannot contain spaces or any of the following characters: ` " ' < > & : ~ ! @ # ; % ^ * + = { } | , \ $ ? ( ) .
Note: If you use customized API URLs, use only Latin characters in the group context.
•The context cannot be identical to the name of an 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 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.