# Alternative for incorrect OAuth swagger specification

**URL:** <https://community.hubspot.com/t/alternative-for-incorrect-oauth-swagger-specification/89746>\
**Category:** APIs & Integrations\
**Tags:** oauth\
**Created:** [September 15, 2023, 5:42pm UTC](https://community.hubspot.com/t/alternative-for-incorrect-oauth-swagger-specification/89746 "2023-09-15T17:42:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Invantive](https://avatars.discourse-cdn.com/v4/letter/i/22d042/32.png) [@Invantive](https://community.hubspot.com/u/Invantive)\
**Post date:** [September 15, 2023, 5:42pm UTC](https://community.hubspot.com/t/alternative-for-incorrect-oauth-swagger-specification/89746/1 "2023-09-15T17:42:32Z")

</div>

The URL [https://api.hubspot.com/api-catalog-public/v1/apis/oauth/v1](https://api.hubspot.com/api-catalog-public/v1/apis/oauth/v1) is one of the default swagger specifications.

However, it’s contents are not a valid swagger / OpenAPI specification. For instance, the required “title” is missing.

All these specifications are automatically converted into a HubSpot data model on our UniversalSQL-engine, but the queries on OAuth entities are not available due to the incorrect format.

Is there an alternative available which contains valid OpenAPI specification for Oauth topic?