How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Microsoft Azure Turn API

The Turn API from Microsoft Azure — 2 operation(s) for turn.

Microsoft Azure Turn API is one of 1667 APIs that Microsoft Azure publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include TURN. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, pricing, a JSON-LD context, and a getting-started guide.

This API exposes 2 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 2020-08-01-preview.

2 operations 2 paths 7 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2020-08-01-preview
Resource Areas
1

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Turn 2
POST
/networktraversal/:issueRelayConfiguration
Microsoft Azure Issue A Configuration For An Stun Turn Server For An Existing Identity
microsoftAzureCommunicationnetworktraversalIssuerelayconfiguration 1 param body → 200default
POST
/networkTraversal/:issueRelayConfiguration
Microsoft Azure Issue A Configuration For An Stun Turn Server
microsoftAzureCommunicationnetworktraversalIssuerelayconfiguration 1 param body → 200default

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are CommunicationIceServer_2 (4 properties), CommunicationIceServer (3 properties), CommunicationRelayConfigurationRequest_2 (3 properties), CommunicationRelayConfiguration (2 properties). Each schema is shown below with its type and property counts.

CommunicationRelayConfiguration_2
object
A relay configuration containing the STUN/TURN URLs and credentials.
2 properties 2 required
CommunicationRelayConfigurationRequest
object
Request for a CommunicationRelayConfiguration.
1 property
CommunicationRelayConfigurationRequest_2
object
Request for a CommunicationRelayConfiguration.
3 properties
CommunicationIceServer
object
An instance of a STUN/TURN server with credentials to be used for ICE negotiation.
3 properties 3 required
CommunicationIceServer_2
object
An instance of a STUN/TURN server with credentials to be used for ICE negotiation.
4 properties 4 required
CommunicationRelayConfiguration
object
A relay configuration containing the STUN/TURN URLs and credentials.
2 properties 2 required
RouteType
string
The routing methodology to where the ICE server will be located from the client. "any" will have higher reliability while "nearest" will have lower latency. It…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-azure-turn-api-openapi.yml Raw ↑

Other APIs Microsoft Azure publishes across the network.

Microsoft Azure AI Search API
Microsoft Azure Communication Services API
Microsoft Azure Event Grid API
Microsoft Azure Functions API
Microsoft Azure DevOps REST API
Microsoft Azure AI Foundry API
Microsoft Azure Resource JSON Schema
Microsoft Azure JSON-LD Context
Microsoft Azure AccessConnector API
Microsoft Azure AccessControlRecords API
Microsoft Azure AccessPolicies API
Microsoft Azure AccessReviewInstanceAcceptRecommmendations API
Where this information came from

This is an independent, third-party profile of Microsoft Azure Turn API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.