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

API Registry properties

API Registry properties

The following table describes the API Registry page properties:
Property Description
Icon Identifies whether the entity is a service or managed API:
  • : Designates a service.
  • : Designates a managed API.
Name Name of the managed API. The name and version combination must be unique in the organization. The name can contain up to 50 characters, including any letter on the ASCII table, any digit, and the special characters . _ and -. The name cannot contain spaces or any of the following characters: " ~ ! @ # ; : % ^ . & * + = { } ( ) | < > , ' / \ $
The name is part of the API URL.
Version Version of the managed API. A managed API can have up to three versions.
Version can contain up to 10 characters including any letter on the ASCII table, any digit, and the special characters . _ and -. It cannot contain spaces or any of the following characters: " ~ ! @ # ; : % ^ . & * + = { } ( ) | < > , ' / \ $
Version cannot be t because the segment /t/ is reserved for Informatica internal use.
Different versions of a managed API point to different Cloud Application Integration processes.
Protocol The protocol of the service or the managed API:
  • REST
  • SOAP
Informatica Cloud Application Integration services are published with both REST and SOAP endpoints.
Status Status of a managed API:
  • Active : The managed API is active.
  • Inactive : The managed API is currently not available.
  • Service not available : This status indicates a managed API for a service that is unavailable or deleted.
If the service for which a managed API has been created is unavailable or deleted, the managed API is greyed out.
Authentication Method API authentication method:
  • Anonymous: The API does not require the API consumer to authenticate.
  • Basic: The API consumer must provide an Informatica Intelligent Cloud Services user name and password for authentication.
  • JWT - JSON Web Token: The API consumer must pass the JWT token as a bearer token in the HTTP Authorization header for authentication. For example:
    Authorization: Bearer aF…mk
  • JWT and Basic: The API consumer can either pass the JWT token as a bearer token in the HTTP Authorization header or provide the login credentials of the allowed user groups or users for authentication.
Group The group that the API belongs to.
Description Description of the service.


Updated December 31, 2019


Explore Informatica Network