If you have an existing REST service that you want to expose through an IBM® API
Connect API definition, you can
create a proxy API and specify the target endpoint by using the API
Manager.
About this task
You can complete this task either by using either the API Designer UI application, or by using the browser based API Manager UI.
To complete this task,
you must be assigned a role that has the Api-Drafts:Edit,
Settings:View, and App:View permissions. The pre-supplied Developer role has these permissions by default;
if you are assigned a custom role it must have these permissions.
For more information, see Creating custom
roles.
Create proxy REST APIs in minutes by using the API
Manager tool to create an
API from target service. This procedure creates a REST proxy that routes all
traffic to a target REST API or service endpoint.
Procedure
To compose a proxy API from a target service, complete the following
steps.
-
In the navigation pane, click
Develop, and then click . The Add API: Create screen is
displayed.
-
Select From target service, and click Next.
-
Click Next. Specify the API summary in the Info
screen. You can fine-tune the API after it is created.
- The Title can include special characters but should be kept short so that
it can be easily displayed in the user interface.
- The Name is entered automatically. The value in the
Name field is a single string that is used to identify the Product in developer toolkit CLI commands. To view
the CLI commands to manage draft APIs, see apic draft-apis.
- The Version corresponds to the value of the
info.version
property of the API's OpenAPI definition. The
version.release.modification version numbering scheme is recommended; for example
1.0.0.
- The Base path is the URL segment of the API and does not include the host
name or any additional segments for paths or operations. The base path cannot include special
characters and must begin with a
/
character even if it is otherwise empty.
- The optional Description helps to identify the API.
-
Specify the existing REST API endpoint that you want to call in the Target Service
URL field.
-
Click Next. In the Secure section, configure the
API security that you require.
- Secure using Client ID - Select this option to require an Application to
provide a Client ID (API Key). This causes the
X-IBM-Client-Id parameter to be
included in the request header for the API. If selected, you can then select whether to limit the
API calls on a per key (per Client ID) basis:
- Limit API calls on a per key basis - If selected, you must configure the
rate limit that you require. Rate limits control the maximum number of calls allowed within a time
period (hour, minute, month or day). For example, 100 calls per hour.
For information about security options in IBM API
Connect, see Configuring API
security.
- CORS - Select this option to enable cross-origin resource sharing (CORS)
support for your API. This allows your API to be accessed from another domain.
-
Click Next to create your API definition.
The Summary panel displays messages as the definition is created, and the selected security
options and rate limits are enforced.
-
Select one of the following options:
- To further configure your API, click Edit API. For details, see Editing an API
definition.
- If you do not want to configure your API further at this time, click the left arrow icon
to return to the
APIs and Products page; you can then move on immediately to another task. For
details on how to configure your API later, see Editing an API
definition.
Results
You created a proxy API from an existing target service.
What to do next
APIs are made available to application developers by including them in a
Product, and then publishing that Product to a Catalog. For more information, see Working with Products and Working with
Catalogs.