to open the navigation menu.
In this article
The API Catalog offers Developer Portal users access to the SnapLogic APIs developed in your Org without needing SnapLogic credentials. Developer Portal users can explore APIs and, depending on policies and publication settings, try them. A subscription service allows users to create accounts. Developer Portal users can subscribe to APIs by creating Applications.
The article is intended for users of a SnapLogic Org Developer Portal and the API developers who publish their APIs and manage them through the Org. Org admins are a secondary audience.
The API Catalog is divided into sections. Click to open the navigation menu.
The navigation menu displays shortcuts to these sections, as shown in the following image.
Home Page: Displays a preview of Applications and APIs.
Applications: Displays all Applications.
Catalog: Displays all APIs.
Click in the top left-side corner to return to the Home page.
The Home page displays a selection of your Applications along with APIs that are marked Featured. Click See All to show all of your Applications or all APIs in the Catalog.
To search for APIs, click to view the entire API catalog in the Developer Portal.
Enter your search string in the Search field.
Optionally, select the default filters (Featured and Deprecated) for your search, and click Apply. You can further filter the search results by clicking the available categories.
Your search string will be compared with the following API attributes:
API Name
Version
Created By
Description
Tags
You can logically group, filter the selection, and classify APIs by category to more easily navigate the APIs. This increases the productivity targeting a specific service.
Select a filter and category to classify a service in Developer Portal > Catalog Tab.
To easily navigate specific APIs, this feature now only allows selection of a single category with multiple filters.
You can now do Category selection with the option buttons.
To easily navigate specific APIs, this feature now only allows selection of a single category with multiple filters.
You can now do Category selection with the option buttons.
After you select the filter and category, you can view the selection with the number of APIs in the selection as a header:
Now after browsing the API Documentation, the previously selected filter and category does not clear out. You can still search for the APIs in the same selection.
The category selection is cleared out automatically if you either log out of the portal or the session times out.
You can bookmark the selection of filter and category in your browser and it remains intact after you are logged off. However, as per the roles and permission you can still view the APIs.
Now after browsing the API Documentation, the previously selected filter and category does not clear out. You can still search for the APIs in the same selection.
The category selection is cleared out automatically if you either log out of the portal or the session times out.
You can bookmark the selection of filter and category in your browser and it remains intact after you are logged off. However, as per the roles and permission you can still view the APIs.
When you access a previously saved ‘filter and category selection’ bookmark in your browser after the enhancement, the system now intelligently presents the first category in the list as the default selection. |
Search results that match with the filter and category in the side pane of the API documentation. When you do this, you enable easy selection of any API and you can view its documentation.
Either select the filter and category of the required APIs or enter the API name in the Search Bar of the Developer Portal:
From the selected filter and category, you can view and select the APIs while you browse through the API document:
|
You can view the details of any API by clicking the API card. Clicking the API displays the documentation of that API.
Click Subscribe.
Proceed through the API subscription wizard.
Click to open the API definitions and documentation for each REST call.
Click Authorization or the padlock by each REST call to open Authorizations Available dialog. When you subscribe to an API, you receive the bearer token or key to call the API.
Scroll through each REST call to view Parameters and Responses.
Click to close the API documentation.
Click to generate a specification for the API.
Choose one of the following formats for your specification download:
JSON
YAML
Navigate to your local downloads folder to open the specification.
The following details are provided for the API:
Version: The version of the API.
Updated: The last time the API version was updated.
Created by: The creator of the API.
Description: A description of the API functionality.
Tags: Metadata labels of the API used to categorize the API contents.
Other Versions: Other versions of the API, which can be accessed through the version link.
Contact: The contact information (email and Slack) of the administrator of the API.
Categories: The API Catalog categories under which the API falls.
Base URL: The endpoint through which you can invoke the API.
The Base URL for OAS 3.0 is displayed as a Server properties settings.
The Base URL for OAS 2.0 is displayed as a text link at bottom of the API meta-data section.
OAS Version: The Open API Specification version that the API was created with.
Additional details:
Documentation: (Specification) The API owner can include a documentation reference in the Swagger editor, which appears as a web link.
Terms of Service: (Specification) The API owner can include a link to the terms of service in the Swagger editor, which appears as a web link.
License: (Specification) The API owner can include a link to the API license in the Swagger editor, which appears as a web link.
If the API owner who published the API includes a documentation reference in the Swagger editor, the description appears here as a web link.
You can also view the various HTTP methods and endpoints of the API.
To subscribe to the API, click the Subscribe button, then select or create the application to which you want to add the subscription.
The Subscribe button appears only if the API was published with Allow Subscriptions enabled.
The Subscribe button appears only if the API was published with Allow Subscriptions enabled.
To return to the API catalog, click Cancel.
To authenticate to use an API,
Click the security lock icon to open the Available authorizations dialog.
Depending on the configuration of the API, you can authenticate by filling in one of the following sections in the Available authorizations dialog:
applicationSecret (apiKey). If you created an application, edit your application and copy the Client Secret from the Edit Application dialog and paste it into the Value field.
Basic authorization. Enter your SnapLogic account credentials.
Click the Authorize button of the section you filled in.
Check the API Key expiration date when you encounter a 401 error. Renew the API key to resolve the error encountered.
Check the API Key expiration date when you encounter a 401 error. Renew the API key to resolve the error encountered.
Adding Basic Authentication support to the outbound flow when connecting to a backend service through the API proxy is important to enhance the security and flexibility of outbound connection in the SnapLogic APIM solution. This authentication is executed on the JCC level, and the other policies applied are executed after the execution of Basic Authentication.
Add the Basic Authentication security schema to the API specification.
Authorize the Basic Authentication you added with login credentials to your API specification..
Click the Authorize button:
Enter the login credentials to authenticate:
Click the Authorize button.
If the Proxy fails to execute with the Basic Authentication, then you can override the execution with the policies applied such as the Basic Auth Policy, Authorize by Role Policy, etc.
Basic Authentication is the first security level authorization and not a policy. It is an extended support of the Bearer Authentication Schema for the Proxy.
If the Proxy fails to execute with the Basic Authentication, then you can override the execution with the policies applied such as the Basic Auth Policy, Authorize by Role Policy, etc.
Basic Authentication is the first security level authorization and not a policy. It is an extended support of the Bearer Authentication Schema for the Proxy.
You can try out APIs in the Developer Portal while viewing the API’s documentation in the Developer Portal.
Prerequisites
The API must include a CORS Restriction policy. If the Developer Portal is set up to allow the Try It Out feature for all APIs using the default CORS Restriction policy, the policy is not required at the API level.
The API must be published.
You must be authenticated to use the API.
To try out the API:
Expand one of the panels that show an HTTP method and an API endpoint.
Click the Try it out button at the top right of the expanded panel.
Fill in the values in the Parameters section.
Verify the results in the Responses section.