Azure Communication Services: Sender Usernames
REST API for Email Services/Domains/SenderUsernames
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
REST API for Email Services/Domains/SenderUsernames
Endpoints 4
SenderUsernames
- GETListBy_Domains
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Communication/emailServices/:emailServiceName/domains/:domainName/senderUsernamesList all valid sender usernames for a domains resource. - GETGet
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Communication/emailServices/:emailServiceName/domains/:domainName/senderUsernames/:senderUsernameGet a valid sender username for a domains resource. - PUTCreate Or Update
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Communication/emailServices/:emailServiceName/domains/:domainName/senderUsernames/:senderUsernameAdd a new SenderUsername resource under the parent Domains resource or update an existing SenderUsername resource. - DELETEDelete
/subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Communication/emailServices/:emailServiceName/domains/:domainName/senderUsernames/:senderUsernameOperation to delete a SenderUsernames resource.
API details
- Base URL
https://management.azure.com- Authentication
- OAuth 2.0 (implicit flow) with 1 scope
- Operations
- 4 operations on 2 pathsGET 2PUT 1DELETE 1
- Main resources
- SenderUsernames 4
- Response formats
application/json- Description format
- Swagger 2.0, API version
2025-05-01 - Links
- OpenAPI document
How to test the Azure Communication Services: Sender Usernames in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Azure Communication Services: Sender Usernames collection, without the publisher's secrets.
- Add your credentialsThis API uses OAuth 2.0 (implicit flow) with 1 scope. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “ListBy_Domains” (GET /subscriptions/:subscriptionId/resourceGroups/:resourceGroupName/providers/Microsoft.Communication/emailServices/:emailServiceName/domains/:domainName/senderUsernames), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Azure Communication Services: Sender Usernames?
REST API for Email Services/Domains/SenderUsernames It is listed under Communication and has 4 endpoints.
Who publishes the Azure Communication Services: Sender Usernames?
It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Azure Communication Services: Sender Usernames?
Requests go to https://management.azure.com. Endpoint paths are added to this base URL.
How do I authenticate with the Azure Communication Services: Sender Usernames?
With OAuth 2.0 (implicit flow) with 1 scope.
How many endpoints does the Azure Communication Services: Sender Usernames have?
4 operations on 2 paths (2 GET, 1 PUT, 1 DELETE). The largest groups are SenderUsernames.
Is forking the Azure Communication Services: Sender Usernames free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.