Celigo’s API Management solution allows you to expose your company’s data, services, and assets. It enables business systems to connect, accelerate partner connectivity, increase business agility, and spur product innovation. API management enables developers and organizations to secure, scale, govern, analyze, and monetize these APIs. Celigo’s API Management solution empowers you to extend your digital platform, forge new communication channels, and attract new customers.
Celigo API Management provides the core features necessary for all phases of the API lifecycle, including:
-
Design - create, edit and version APIs to make your organization’s data and processes available for reuse
-
Secure - manage the policies (authorization, rate-limiting, throttling, masking, etc…) that will take effect for various plans you make available for your APIs
-
Socialize - publish your APIs to a centralized and customizable portal for internal and external consumers to discover and subscribe
-
Monitor - analyze usage patterns, performance and consumption to guide decision making for your API initiatives
Celigo API Management is an integrated component of the Celigo platform that helps you form the backbone of your API-led integration strategy. You can build new backend services using the platform's core integration features (imports, exports, My APIs, etc.…) and push them to the API Management console to customize and govern your endpoints before exposing them.
Celigo API Management provides three major components:
-
APIM Console - allows API publishers to create new APIs, add policies, define plans, approve subscriptions and monitor API usage metrics.
-
APIM Developer Portal - allows API consumers to discover APIs that may be of interest to them, subscribe to APIs, and manage their ongoing subscriptions.
-
APIM Gateway - enforces the policies and other security controls that have been applied to the API proxy interface
There are many benefits to publishing, managing, and consuming APIs through Celigo's integrator.io. For most, the benefits come from customization and ease-of-use.
-
API security and access control – Implements authentication, authorization, and encryption mechanisms to secure APIs and ensure only authorized users can access sensitive data and services.
-
API performance analytics – Developers can create custom dashboards, reports, and analytics tools to monitor API usage.
-
API governance – Controls the rate at which different users or applications can access your APIs to prevent overload and ensure fair usage.
-
API documentation and Developer portal – Creates user-friendly documentation, interactive examples, and a developer portal to facilitate understanding and adoption of your APIs.
-
External developer access and partner integration – Allows third-party developers to access and utilize your organization's APIs to build applications and services that enhance your offerings. It also enables partners to integrate their systems with your APIs for more streamlined collaboration and data sharing.
-
Internal API consumption and integration – Enables different teams within your organization to use and share APIs to promote the reusability of services, reduce duplication of efforts, and accelerate development cycles.
-
Legacy system modernization – Exposes APIs for legacy systems, allowing them to be integrated with modern applications and services, avoiding the need for a complete system overhaul.
-
Monetization and revenue generation – Generates revenue by exposing certain APIs to external developers for a fee or subscription, creating new business models and opportunities.
There are many ways to take advantage of API management.
-
Implement and build APIs
-
Define API security and traffic shaping and provide routing information to backend endpoints
-
Expose APIs to the gateway
-
Publish APIs to the portal
-
Design APIs
-
Define metrics and analyze API usage
-
Collaborate with API developers to define security, traffic shaping, and other policies
There are various features you can make use of in Celigo's API Management solution.
API publishers can configure, implement, and publish APIs for consumers and application developers to use. The APIM console allows publishers to configure every aspect of an API, from its policies to its plans and documentation. Publishers can use various authentication methods, including, but not limited to, JWT, OAuth 2.0, and keyless authentication.
API consumers and application developers can access and consume APIs an organization exposes in the Developer Portal to build new APIs and applications, thereby automating business processes.
Public and private APIs can be published in the developer portal for external and internal consumption. API consumers can use an identity provider to sign in to the developer portal and discover, subscribe, test, and consume the APIs. API requests from a client-based web application with a different URL will be allowed via the APIM gateway using CORS (Cross-origin resource sharing).
API publishers can view prebuilt dashboards in the APIM Console to monitor how well the APIs are performing and identify bottlenecks, latency issues, and other performance-related issues, which can help you optimize these APIs. You can also create custom dashboards around API performance, status, lifecycle stage, etc.
API publishers can configure and enforce policies at the API gateway level to manage and control API traffic (e.g. using rate limiting), apply transformations to requests or responses, define logs and metrics, manage caches, etc.
When a resource is managed through the API console, the required API gateway policies will be added by default. You can add more policies at API manager → API → Policy Studio. There are 40+ policies you can use to customize your API. Some commonly used policies are:
-
Rate Limiting
-
IP Filtering
-
XML to JSON
-
REST to SOAP
-
Mock
-
Cache
-
Transform header
-
Dynamic routing
-
HTTP Callout
API publishers can document APIs in OpenAPI specification (OAS) format so that API consumers can have a clear and detailed explanation of how an API works and how to use it effectively. It will also reduce the learning curve for consumers, making it easier for them to adopt and integrate the API into their applications.
integrator.io will generate the OpenAPI specification (OAS) for export and import backend services, not including MyAPI services. Specifications for multiple endpoints in an API will be grouped. Services pushed to the API manager will be automatically configured with the required OAS. You can update the OAS in the API manager at API → General → Documentation. API publishers can publish the documentation to the Developer Portal so consumers can discover, subscribe to, and adopt APIs.
API publishers can publish the documentation to the Developer Portal so consumers can discover, subscribe and adopt APIs.
Caution
There are prerequisite elements to generate OAS for any APIs. MyAPI is a script-based resource where prerequisite elements will be missing; thus, the OAS will not be generated. If the OAS is generated, users must manually verify and update OAS in the API manager.
API publishers can view audit logs of all changes done in the API manager to easily identify who has changed the API configuration when the API breaks and to revert back to the previous API version if required.
API publishers can create notifications based on set alerts (e.g., API key expiry, new subscription, etc.) using one or more of the following options:
-
Portal notification to send messages to users logged in to the developer portal
-
Email notification to send messages to a specific list of email addresses
-
Webhook notification to send an HTTP POST request to a specific URL
Comments
Please sign in to leave a comment.