406 error while connecting to API from Rest source of Copy data activity but works from Web activity and Postman.

Question

406 error while connecting to API from Rest source of Copy data activity but works from Web activity and Postman.

Mishra, Swastik 0

I am facing an issue where the API works from Web activity of Adf pipeline but doesn't work from Rest source of Copy data activity. It was working initially and stopped.

Same API works from web activity and postman.

My API works from Web activity but doesn't work from the Rest Data source of Copy Activity.

It was working initially and after a week when I tried it suddenly it fails with error 406. If I add Http Json data source adding additional headers Content type, Ocp-Apim-Subscription-Key and Authorization with Bearer token is so difficult to format it doesn't work too.

Json data from web activity added separately is also difficult to format and pass to azure sql table.

Failure happened on 'Source' side. ErrorCode=RestCallFailedWithClientError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Rest call failed with client error, status code 406 NotAcceptable, please check your activity settings.

Request URL: 8***/.

Response: ,Source=Microsoft.DataTransfer.ClientLibrary,'

Chandra Boorla 14,510 Reputation points Microsoft External Staff Moderator

2025-04-16T17:02:35.1866667+00:00

@Mishra, Swastik

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mishra, Swastik 0 Reputation points

2025-04-29T15:03:55.7+00:00

I tried by inserting a web activity to call the api and another web activity to PUT data into a blob storage. Once the data is stored in blob storage, I used the copy data to fetch from blob and store data in SQL.

Web 1 for to Call the API ,
Web 2 to PUT data in Blob

Copy data source is blob and sink is Azure SQL

The rest used as source was failing in Copy data but Web in copy data source also failed as the additional headers was not getting formatted correctly. Else it would have been more cost effective. Just for stagging I have to use Blob.

Http Header format in Source.

Web connection as source if would have separate header columns to add like Rest then it would have been easier and could have worked, I guess.

Rest Header Format in source :

So, calling web activity as a different action was the work around for the successful pipeline run.
Dileep Raj Narayan Thumula 255 Reputation points Microsoft External Staff Moderator

2025-04-30T11:30:24.7933333+00:00

@Mishra, Swastik, So the workaround you have tried did it resolve the issue?
could you confirm if it helped to resolve with regards the question you have asked?
Mishra, Swastik 0 Reputation points

2025-04-30T12:43:14.8+00:00

Yes it did

1 answer

Your answer

Chandra Boorla 14,510 Reputation points Microsoft External Staff Moderator

2025-04-16T17:02:35.1866667+00:00

@Mishra, Swastik

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mishra, Swastik 0 Reputation points

2025-04-29T15:03:55.7+00:00

I tried by inserting a web activity to call the api and another web activity to PUT data into a blob storage. Once the data is stored in blob storage, I used the copy data to fetch from blob and store data in SQL.

Web 1 for to Call the API ,
Web 2 to PUT data in Blob

Copy data source is blob and sink is Azure SQL

The rest used as source was failing in Copy data but Web in copy data source also failed as the additional headers was not getting formatted correctly. Else it would have been more cost effective. Just for stagging I have to use Blob.

Http Header format in Source.

Web connection as source if would have separate header columns to add like Rest then it would have been easier and could have worked, I guess.

Rest Header Format in source :

So, calling web activity as a different action was the work around for the successful pipeline run.
Dileep Raj Narayan Thumula 255 Reputation points Microsoft External Staff Moderator

2025-04-30T11:30:24.7933333+00:00

@Mishra, Swastik, So the workaround you have tried did it resolve the issue?
could you confirm if it helped to resolve with regards the question you have asked?
Mishra, Swastik 0 Reputation points

2025-04-30T12:43:14.8+00:00

Yes it did

Answer 1

Chandra Boorla 14,510 Microsoft External Staff Moderator

@Mishra, Swastik

The issue you're facing is due to the response data being in JSON-LD format (JSON for Linked Data). When using the Copy Data activity with REST source, ADF sets default headers that may not align with what the API expects in terms of content negotiation.

Root Cause.

ADF’s Copy Data activity sets default headers like Accept: application/json, which may not align with your API’s requirements. Since your API works in Web Activity and Postman, it's likely expecting a different Accept header—possibly for JSON-LD (application/ld+json) or another specialized format.

User's image

For additional information, please refer: Copy and transform data from and to a REST endpoint by using Azure Data Factory

Resolution.

To resolve the issue, explicitly configure the required headers in your REST dataset used in the Copy Activity. Here’s what you can try adding in the Request Headers:

Accept: application/ld+json
Content-Type: application/ld+json
Authorization: Bearer <your_token>
Ocp-Apim-Subscription-Key: <your_key>

This will ensure that ADF requests are compatible with the API’s expected format and prevent the 406 error.

Make sure:

The Authorization value is formatted exactly as: Bearer <token> (with a space).
Header names are correctly cased (Content-Type, not contenttype).
These headers match what works in Postman or Web Activity.

Additional considerations:

If the API returns complex JSON (e.g., JSON-LD), ADF might have trouble flattening it into a tabular format. In that case, consider:

Using Web Activity to call the API and save the response to Blob Storage.
Then use Mapping Data Flow or Data Flow activity to parse and load into SQL.

For more details, please refer to the below similar threads for useful insights.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Thank you.

Mishra, Swastik 0 Reputation points

2025-04-17T15:00:25.83+00:00

Hi, thank you so much for the response. I tried the suggestion of application/ld+

"additionalHeaders": { "Content-Type": "application/ld+json", "Ocp-Apim-Subscription-Key": "*", "Authorization": "Bearer *", "Accept": "application/ld+json" }

Error :

Failure happened on 'Source' side. ErrorCode=RestCallFailedWithClientError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Rest call failed with client error, status code 403 Forbidden, please check your activity settings.

I checked the additional header spelling and space with bearer and it all seems perfect.

Its little frustrating that web activity output can't be passed to copy data source directly. I tried Using Http Activity to call the API and save the response to Blob Storage, but if we have web activity individually we can add headers easily but when we do it with copy data we have to add headers in a single textbox and some how the format never comes correctly and its failing.

I will try the suggestion of using Web Activity to call the API and save the response to Blob Storage.
Chandra Boorla 14,510 Reputation points Microsoft External Staff Moderator

2025-04-17T17:02:17.18+00:00

@Mishra, Swastik

Thank you for your feedback. We are sorry to hear that the response did not meet your expectations and apologize for any inconvenience caused. To help us better understand the issue and assist you more effectively, could you please share the complete pipeline JSON or a screenshot of the relevant configuration?

In the meantime, you can refer to the thread below, which discusses a similar issue and may provide some useful insights.

Thread link: https://learn.microsoft.com/en-us/answers/questions/1189756/adf-rest-call-failed-with-client-error-status-code

Thank you.
Chandra Boorla 14,510 Reputation points Microsoft External Staff Moderator

2025-04-18T16:26:37.53+00:00

@Mishra, Swastik

Just following up on our previous response. If you found the information helpful, we encourage you to consider re-rating the thread, as your feedback is valuable and can assist others in the community facing similar issues.

If you have found a resolution to your issue, we would appreciate it if you could share it in the thread to benefit others. Otherwise, will respond with more details and we will try to help. Thank you.
Dileep Raj Narayan Thumula 255 Reputation points Microsoft External Staff Moderator

2025-04-21T16:24:34.5366667+00:00

Hello @Mishra, Swastik,

ERROR:

ErrorCode=RestCallFailedWithClientError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Rest

call failed with client error, status code 406 NotAcceptable, please check your activity settings.

A 406 error occurs when the server can't provide a response in the format specified by the Accept header in the request.

In your case, it seems that application/json might not be an acceptable response format for the server.

You can refer List of HTTP header fields

Find out the response (content type) returned by Service.

Try updating the header to Accept: */*. Also, ensure that no other Accept headers are included in the request.

Also consider refering Bearer tokens.

Note:You should also verify the lifetime of your access token to ensure it doesn’t expire too quickly—such as within an hour.

Disclaimer: This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
Dileep Raj Narayan Thumula 255 Reputation points Microsoft External Staff Moderator

2025-04-23T12:23:52.17+00:00

Hello @Mishra, Swastik,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Dileep Raj Narayan Thumula 255 Reputation points Microsoft External Staff Moderator

2025-04-24T11:49:43.4633333+00:00

Hello @Mishra, Swastik, We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

406 error while connecting to API from Rest source of Copy data activity but works from Web activity and Postman.

1 answer

Your answer