Skip to content

Commit 7ceb413

Browse files
authored
Merge pull request #187626 from ProbablePrime/rifox/skd-options-reorder
reorder SDK page so it makes a lot more sense.
2 parents 8268c75 + 7b50b8d commit 7ceb413

File tree

1 file changed

+16
-22
lines changed

1 file changed

+16
-22
lines changed

articles/communication-services/concepts/sdk-options.md

Lines changed: 16 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,12 @@ ms.service: azure-communication-services
1313
---
1414
# SDKs and REST APIs
1515

16-
Azure Communication Services APIs are organized into eight areas. Most areas have fully open-sourced SDKs programmed against published REST APIs that you can use directly over the Internet. The Calling SDK uses proprietary network interfaces and is closed-source.
16+
Azure Communication Services capabilities are conceptually organized into discrete areas based on their functional area. Most areas have fully open-sourced SDKs programmed against published REST APIs that you can use directly over the Internet. The Calling SDK uses proprietary network interfaces and is closed-source.
1717

1818
In the tables below we summarize these areas and availability of REST APIs and SDK libraries. We note if APIs and SDKs are intended for end-user clients or trusted service environments. APIs such as SMS should not be directly accessed by end-user devices in low trust environments.
1919

2020
Development of Calling and Chat applications can be accelerated by the [Azure Communication Services UI library](./ui-library/ui-library-overview.md). The customizable UI library provides open-source UI components for Web and mobile apps, and a Microsoft Teams theme.
2121

22-
## REST APIs
23-
Communication Services APIs are documented alongside other [Azure REST APIs in docs.microsoft.com](/rest/api/azure/). This documentation will tell you how to structure your HTTP messages and offers guidance for using [Postman](../tutorials/postman-tutorial.md). REST interface documentation is also published in Swagger format on [GitHub](https://github.com/Azure/azure-rest-api-specs).
24-
2522
## SDKs
2623
| Assembly | Protocols| Environment | Capabilities|
2724
|--------|----------|---------|----------------------------------|
@@ -54,29 +51,14 @@ Publishing locations for individual SDK packages are detailed below.
5451
| UI Library| [npm](https://www.npmjs.com/package/@azure/communication-react) | - | - | - | - | - | [GitHub](https://github.com/Azure/communication-ui-library), [Storybook](https://azure.github.io/communication-ui-library/?path=/story/overview--page) |
5552
| Reference Documentation | [docs](https://azure.github.io/azure-sdk-for-js/communication.html) | [docs](https://azure.github.io/azure-sdk-for-net/communication.html)| -| [docs](http://azure.github.io/azure-sdk-for-java/communication.html) | [docs](/objectivec/communication-services/calling/)| [docs](/java/api/com.azure.android.communication.calling)| -|
5653

57-
The mapping between friendly assembly names and namespaces is:
58-
59-
| Assembly | Namespaces |
60-
|------------------------|--------------------------------------|
61-
| Azure Resource Manager | Azure.ResourceManager.Communication|
62-
| Common | Azure.Communication.Common |
63-
| Identity | Azure.Communication.Identity |
64-
| Phone numbers| Azure.Communication.PhoneNumbers |
65-
| SMS| Azure.Communication.SMS|
66-
| Chat | Azure.Communication.Chat |
67-
| Calling| Azure.Communication.Calling|
68-
| Calling Server | Azure.Communication.CallingServer|
69-
| Network Traversal| Azure.Communication.NetworkTraversal |
70-
| UI Library | Azure.Communication.Calling|
71-
72-
## SDK platform support details
54+
### SDK platform support details
7355

74-
### iOS and Android
56+
#### iOS and Android
7557

7658
- Communication Services iOS SDKs target iOS version 13+, and Xcode 11+.
7759
- Android Java SDKs target Android API level 21+ and Android Studio 4.0+
7860

79-
### .NET
61+
#### .NET
8062

8163
Except for Calling, Communication Services packages target .NET Standard 2.0, which supports the platforms listed below.
8264

@@ -99,6 +81,18 @@ The Calling package supports UWP apps build with .NET Native or C++/WinRT on:
9981
- Windows 10 10.0.17763
10082
- Windows Server 2019 10.0.17763
10183

84+
## REST APIs
85+
Communication Services APIs are documented alongside other [Azure REST APIs in docs.microsoft.com](/rest/api/azure/). This documentation will tell you how to structure your HTTP messages and offers guidance for using [Postman](../tutorials/postman-tutorial.md). REST interface documentation is also published in Swagger format on [GitHub](https://github.com/Azure/azure-rest-api-specs).
86+
87+
### REST API Throttles
88+
Certain REST APIs and corresponding SDK methods have throttle limits you should be mindful of. Exceeding these throttle limits will trigger a`429 - Too Many Requests` error response. These limits can be increased through [a request to Azure Support](../../azure-portal/supportability/how-to-create-azure-support-request.md).
89+
90+
| API| Throttle|
91+
|------------------------------------------------------------------------------------------------------------------------------|---------------------|
92+
| [All Search Telephone Number Plan APIs](/rest/api/communication/phonenumbers) | 4 requests/day|
93+
| [Purchase Telephone Number Plan](/rest/api/communication/phonenumbers/purchasephonenumbers) | 1 purchase a month|
94+
| [Send SMS](/rest/api/communication/sms/send) | 200 requests/minute |
95+
10296
## API stability expectations
10397

10498
> [!IMPORTANT]

0 commit comments

Comments
 (0)