Performing simple File Storage REST API operations using Postman
The blog provides guidance to perform simple File storage REST API operations such as Create, Copy, Rename and Delete operations using Postman.
Let’s look at some of the command syntax to perform REST API operations and will be making use of SAS as the auth scheme. We need to take care of the pointers below while performing the operations via Postman:
- Ensure the URL is formed correctly as per the operation you are trying to perform.
- The mandatory header needs to be passed.
- Ensure you are appending/removing extra ‘?’ to the SAS token in the URLs accordingly.
- Http verb can be GET, PUT or DELETE as provided by the REST API specifications.
Create Share:
The create share operation creates a new Azure Files share under the specified account.
Create Share (FileREST API) - Azure Files | Microsoft Learn
Syntax URL:
In the below snippet example, a PUT operation was performed on the storage account named somatest to create a File share name as createshare1. File Share was created successfully.
Create Directory:
The Create Directory operation creates a new directory under the specified share or parent directory.
Create Directory (FileREST API) - Azure Files | Microsoft Learn
Syntax URL:
In the below example, we tried performing the Create directory operation named as createmydirectory1 on existing File share.
Delete Directory:
The Delete Directory operation removes the specified empty directory. Note that the directory must be empty before it can be deleted.
Delete Directory (FileREST API) - Azure Files | Microsoft Learn
Syntax URL:
In the below example snippet, we have deleted the directory named createmydirectory inside a file share using HTTP verb as DELETE
Create file:
The Create File operation creates a new file or replaces a file. When you call Create File, you only initialize the file. To add content to a file, you call the Put Range operation.
Create File (FileREST API) - Azure Files | Microsoft Learn
Syntax URL:
Mandatory headers:
In the below example snippet, we have created a file named filecreate1 inside a directory and File share.
Put Range:
The Put Range operation writes a range of bytes to a file.
Put Range (FileREST API) - Azure Files | Microsoft Learn
Syntax URL:
Mandatory headers:
In the below example snippet, we have tried to update a file which is created as part of Create File REST API. We are writing 5bytes to the file.
Copy file:
The Copy File operation copies a blob or file to a destination file within the storage account.
Copy File (FileREST API) - Azure Files | Microsoft Learn
Syntax URL:
Mandatory headers:
In the below example snippet, we have copied the file named copyfile2 from Source fileshare testshare to destination fileshare createshare. You need to authorize the source file to successfully copy to destination.
Rename file:
The Rename File operation renames a file in a storage account.
Rename File (REST API) - Azure Storage | Microsoft Learn
Syntax URL:
Mandatory headers:
In the below example snippet, we have renamed the file from filecreate2 to filecreate3.
Conclusion:
Should you need to test a different API not discussed here, you can easily follow a similar pattern. Adjust the necessary header parameters as required by the specific API you're exploring.
This flexibility allows you to extend these testing techniques to a broad spectrum of APIs, ensuring you're equipped to handle various endpoints by customizing headers and configurations as needed.
I hope this information proves valuable in navigating different APIs and adapting your approach to their unique requirements. Happy testing, discovering, and harnessing the potential of APIs to drive your development endeavors!
Hope this helps!!
Reference Links:
Operations on the FileService resource - Azure Files | Microsoft Learn
Operations on the FileShare resource - Azure Files | Microsoft Learn
Operations on directories (FileREST API) - Azure Files | Microsoft Learn
Operations on files (FileREST API) - Azure Files | Microsoft Learn
Published on:
Learn moreRelated posts
Azure Storage - TLS 1.0 and 1.1 retirement
Overview TLS 1.0 and 1.1 retirement on Azure Storage was previously announced for Nov 1st, 2024, and it was postponed recently to 1 year later...
Efficient Management of Append and Page Blobs Using Azure Storage Actions
Overview In Azure Storage, Blob Lifecycle Management (BLM) allows you to automate the management of your data based on rules defined by...
[Azure AI Search] Internal Server Error when creating CMK encrypted objects
Scenario Customers follow the Microsoft doc to create CMK encrypted objects (data source, index etc.), but get the 500 Internal Serv...
Optimizing Azure Table Storage: Automated Data Cleanup using a PowerShell script with Azure Automate
Scenario This blog’s aim is to manage Table Storage data efficiently. Imagine you have a large Azure Table Storage that accumulates logs from ...
Optimizing Azure Table Storage: Automated Data Clean-up using a PowerShell script with Azure Automat
Scenario This blog’s aim is to manage Table Storage data efficiently. Imagine you have a large Azure Table Storage that accumulates logs from ...
Restoring Soft-Deleted Blobs with multithreading in Azure Storage Using C#
Blob soft delete is an essential feature that safeguards your data against accidental deletions or overwrites. By retaining deleted data for a...
Performing simple Azure Table Storage REST API operations using curl command.
The blog provides guidance to perform simple Table Storage REST API operations such as Create table, Delete Table, Insert entity, Delete entit...
Bulk delete all the old jobs from the batch account
Deleting a Job also deletes all Tasks that are part of that Job, and all Job statistics. This also overrides the retention period for Task dat...
Utilizing Azure Storage and Runbooks for scheduled automated backups of Azure SQL Databases
In this article, we are going to provide detailed steps to create a scheduled Azure SQL Database backup to storage account using automation. T...
[Azure Service Bus] JMS messages getting dead-lettered
The article discusses a problem where numerous messages end up in the dead letter queue (DLQ) when the JMS service bus consumer connects to th...