Release Notes (Feb 2023)

Rapid API Hub for Enterprise Release Notes

We've made some updates to our platform to improve the customer experience. For our API Hub for Enterprise, we’ve released several new analytics features and improvements, including a new page describing log forwarding options and new Admin Panel Dashboard widgets. We’ve also fixed numerous bugs across our platform.

We encourage you to review these release notes to learn more about the changes that have been made and how they may impact your experience with our product.

As always, our team is committed to providing you with the best possible experience with our product, and we appreciate your continued support and feedback. If you have any issues or bugs, you can report them to us at our support page here.

2023.2:
New:

New Log Forwarding Options Page: (Please work with your RapidAPI representative to enable this feature) A new page that explains the three different methods for displaying API logs will appear whenever the Analytics page for an API that has no logs is opened. RapidAPI now offers three different methods for populating APIs logs:
1. RapidAPI Proxy - If your API is configured to use the RapidAPI Proxy, whenever a call is made through the Proxy, API call logs for the consumers and provider will be created
2. Platform Analytics API - The most flexible method is to call the Platform Analytics API directly. This is a high throughput API that allows you to import API logs from any source into your API Project and use the entire analytics suite
3. Gateway Integration - For enterprise customers who are using popular cloud API gateways, RapidAPI is now supporting best-practice gateway integrations. The first supported platform is Amazon API Gateway, with plans to also support Apigee and Kong soon.
Analytics Call To Action: A new page that explains the three different methods for getting API logs will show up whenever the analytics page for an API that has no logs is opened. Rapid now offers three different methods for populating an APIs logs.
- If your API is configured to use the Rapid Proxy, whenever a call is made through the Proxy, API call logs for the consumers and provider will be created.
- The most flexible method is to call the Platform Analytics API directly. This is a high throughput API that allows you to import API logs from any source into your RapidAPI project and use the entire analytics suite.
- For enterprise customers who are using popular cloud API gateways, Rapid now supports best practice gateway integrations. The first supported platform is Amazon API Gateway, with plans to also support Apigee and Kong soon.
New Admin Dashboard Widgets: Seven new widgets on the Admin Panel Dashboard for API traffic:
1. Total API Traffic: measures the total count of all API calls made, helping monitor the size and trend of API traffic and identify potential threats
2. Highest Traffic APIs: measures the 5 APIs with the highest amount of API calls made during a selected period, which can help organizations identify potential traffic spikes and proactively address them to ensure their APIs remain available and responsive
3. Active API Consumers: shows the unique numbers of teams or users who made at least 1 API call within a given period, which can provide insights into the level of engagement and usage of an API and help inform decisions related to capacity planning, resource allocation, and product development. Both widgets can be combined to gain more insights into API traffic by analyzing it by time or consumer, and to understand the actual API activity of consumers
4. Most Active Consumers: identifies the top 5 users/teams with the highest amount of API calls, which can reveal partnership opportunities and provide customer insights
5. API Errors: measures the count of API requests that returned an error code within a given period, helping detect potential issues or risks
6. API Error Rates identifies published APIs with the highest error rates to pinpoint areas for improvement.
7. Spike Arrests: shows all API calls that responded with the error code 429, which is important in monitoring spikes in API traffic and detecting potential security threats
Admin Dashboard - API Traffic Widgets: Seven new widgets on the admin dashboard for API traffic:
- "Total API Traffic": measures the total count of all API calls made, helping monitor the size and trend of API traffic and identify potential threats.
- "Highest Traffic APIs": measures the 5 APIs with the highest amount of API calls made during a selected period, which can help organizations identify potential traffic spikes and proactively address them to ensure their APIs remain available and responsive.
- "Active API Consumers": shows the unique numbers of teams or users who made at least 1 API call within a given period, which can provide insights into the level of engagement and usage of an API and help inform decisions related to capacity planning, resource allocation, and product development. Both widgets can be combined to gain more insights into API traffic by analyzing it by time or consumer, and to understand the actual API activity of consumers.
- "Most Active Consumers": identifies the top 5 users/teams with the highest amount of API calls, which can reveal partnership opportunities and provide customer insights.
- "API Errors": measures the count of API requests that returned an error code within a given period, helping detect potential issues or risks.
- "API Error Rates" identifies published APIs with the highest error rates to pinpoint areas for improvement.
- "Spike Arrests": shows all API calls that responded with the error code 429, which is important in monitoring spikes in API traffic and detecting potential security threats.

Improved:

Admin Dashboard Widget Popover: All widgets on the Admin Panel Dashboard now have an info popover that describes what the widget measures, and how to use the information
Analytics: Reduced time it takes to load API logs for high volume APIs
Analytics: Admin Panel metric charts “from date” will now start at the beginning of the day, avoiding a situation that the first point moves as the day progresses
GraphQL API: we now support uploading a GraphQL API with an extension of .graphqls.

Fixed:

Fixed a bug that caused Quota data to show inaccurate consumption numbers on the "apps > Billing > Subscriptions and Usage" page
Fixed a bug where the API analytics on Admin Panel would not properly load
Fixed stability issues with the "API Alerts" feature
Fixed a bug that occurs when an Admin approves a new user and a "Network Error" occurs after pressing the "Approve" button
Fixed a bug that occurs when a non-member of an org encounters a "Could not find organizations for user" error when clicking on "Join Organizations"
Fixed stability issues with the Admin Panel & API Hub Playground
Fixed a bug where a "REQUEST_OR_RESPONSE_BODY_FAILED_PROCESSING" error appears when using the REST PAPI create and update API version ASYNC endpoints
Fixed a bug where the API Image/Display picture goes missing after updating tags (in the process of trying to make an API public)
Fixed a bug where In Provider > Users the option to see the # of requests a subscriber did in the past 30 days was missing in the new Studio
Fixed a bug where users aren' auto redirected to the context the user is allowed to create APIs from in Studio
Fixed a bug causing a Deprecated API Plan to not show up for an Organization Account (Admin Account) on the API Pricing Page.
Fixed a bug where API Rate Limit Headers did not appear and APIs could be called beyond the allowed rate limit.
Fixed a bug where enabling the analytics tab exposed incorrect information in the enterprise settings configuration for a tenant.
Fixed a bug where uploading a YAML file causes "something went wrong error" in some Enterprise tenants.
Fixed a bug where adding a new API new OpenAPI JSON files cannot be imported if they a field of x-version-lifecycle with a value of 'current'.
Fixed a bug where a "your organization does not have available seats" error would occur when approving users to an organization despite having available seats for some Enterprise tenants
Fixed a bug where adding users to a team through importing through a CSV only imports the first user and errors out on remaining users.
Fixed a bug where audit trails from the Org dashboard are showing blank actions erroneously
Fixed a bug where when creating a Spotlight from a PDF, the Title field was marked as optional even though it is a required field.
Fixed a bug where Files are not deleted via GQL PAPI from the UI when a Spotlight is deleted in some Enterprise tenants.
Fixed a bug where some Enterprise tenants don't have the "Manage Organizations" button in the new masthead.
Fixed a bug where when accessing the inbox in Studio when all projects are selected, the inbox will be empty.
Fixed a bug where a "Too many requests" error would appear when updating an APIs definition.
Fixed a bug where remapping the base URL of an API using API Transformations would cause an error.
Fixed a bug where a "You are not authorize to make this action" error would appear when using the createGQLApiVersions mutation in the GQL API.
Fixed a bug where not all APIs of a certain category are visible when navigating to the Category's page in the Hub.
Fixed a bug where a "Free" tag would appear next to APIs in some Enterprise tenants.
Fixed inconsistent color coding of endpoints from the Hub playground.