Skip to main content

· 2 min read

Access to DX Analytics is no longer restricted to API Owners, the entire team can now track the performance of their API Portal.


APIMatic’s API Portal enables users to track important data points which can help measure the ROI(return on investment) of all API Documentation and Developer Experience efforts. These include metrics like Popular Pages, SDK Downloads and Time to Hello World (the amount of time taken from Documentation discovery to first API call). Read more about DX Analytics from the Introducing API Developer Experience Analytics Blog

Access to DX Analytics has so far been restricted to API owners - the users who initially created an API Portal. However, a large number of customers use APIMatic’s collaboration capabilities to build and maintain their API Portal as a team. We believe that every member of the team should have access to analytics data to quantify the impact of their efforts.

Therefore we are opening up access to DX Analytics for all team members.

How to Access DX Analytics for the API Portal?

You can view analytics for your API Portal by clicking on DX Analytics in your APIMatic Dashboard and selecting your Portal in the left sidebar.

In case you have not published an API Portal yet, but want to get a sense of what your Portal’s Analytics will look like, we have provided some sample data for you to play with.

DX Analytics Gif

· One min read

Previously, our Ruby SDKs were initiating a new connection for each API call. Now, we have made this HTTP connection persistent. Using persistent request allows all server requests to be made through one connection, consequently reducing network latency.

· 5 min read

In the improved Python SDK, fields of a custom type can now differentiate between a nullable value and a missing value and will operate according to the behavior of the type specified. This way you can either pass a value that corresponds to the type specified, use null as a value or skip the field altogether depending upon the defined behavior of the field.

· 2 min read

OAS allows you to set optional/required properties in models. While serializing a model, optional properties will be omitted if the value of property is not set (i.e. initialized with null) and, required properties will be serialized in any case. This is a case of factoring schema in oneOf/anyOf. Now with this support, you can define properties with the same names but with different optional/required constraints in request/response of an endpoint.