Why does the Azure Get Blobs Zip API report 'blobIds is null' despite including them?

Based on the API’s requirements, the error you’re seeing is likely because the request isn’t formed as expected. Here are a couple of points to check:

1. Authorization Header:
   The Logs Ingestion API requires a bearer token obtained via the client credentials flow. In your header, you’re using Basic authentication. Replace it with:

   Authorization: Bearer <your_token>
   

   Using the correct token ensures the API processes your request properly.

2. Request Body and blobIds:
   The error mentioning that “blobIds is null” suggests that the API expected a property (or list) named blobIds within your JSON payload. If your payload is intended to include blobIds, verify that it is correctly set in the JSON body. For example:

   JSONCopied
   {
     "blobIds": ["id1", "id2"],
     "otherProperty": "value"
   }

   Even if you believe “blobIds” is there, if the API doesn’t parse your request due to a header or formatting issue, it might be seen as null.

3. Content-Type and Accept Headers:
   Confirm that the headers match what the API expects. For the Logs Ingestion API, you should use:

   Content-Type: application/json
   

   (The Accept header is generally used to specify the format of the response; if the API expects JSON for requests, it’s best not to mix formats.)

In summary, correct your Authorization header to use a valid Bearer token and double-check your JSON payload to ensure the blobIds property is included. Doing so should resolve the error regarding blobIds being null.