Based on the OData specification, Connect’s APIs are fully documented and discoverable. The APIs can be accessed from standard JavaScript, applications compliant with OpenAPI, or any application that supports the OData standard. The following sections show how to use these standards to discover the APIs.

Service Document

The service document is a simple listing of all the APIs in the JSON format by default. The service document is returned from the service root, where all requests are made, including metadata discovery requests. The following is an example of the service root:

https://myconnectserver/odata.rsc/

To retrieve more detailed information, make a request to the metadata URL.

Metadata URL

Connect exposes the capabilities of its APIs to OData consumers through the OData metadata document URL. The metadata document is returned as XML and contains column data types, the key of the resource, and other information. You can access the complete metadata resource by appending $metadata to the service root, as shown in the following example:

https://myconnectserver/odata.rsc/$metadata

To access the metadata for a resource, append $metadata to the resource URL of the resource, as shown in the following example:

https://myconnectserver/odata.rsc/Cars/$metadata

OpenAPI Definition

OpenAPI (previously known as Swagger) definitions are generated for the endpoints you surface through Connect.

To obtain the OpenAPI definition, append $oas or $swagger to the service root, as shown in the following example:

https://myconnectserver/odata.rsc/$oas