What causes RestSinkCallFailed?

The REST API returned a non-success HTTP status code (4xx or 5xx). The API authentication token or API key is expired or invalid. The request payload format does not match what the REST API expects (wrong JSON structure, missing required fields). The REST endpoint is temporarily unavailable or rate-limiting requests

How do I fix RestSinkCallFailed?

Check the ADF activity run output for the HTTP status code and response body returned by the REST API.. Verify that the REST linked service authentication credentials (Bearer token, API key, OAuth) are valid and not expired.. Review the request body mapping in the copy activity sink to ensure it matches the REST API contract.. If the API is rate-limiting, add a retry policy to the copy activity with exponential backoff.. Test the REST endpoint directly (e.g., with Postman) using the same credentials and payload to isolate the issue.

High severitydata source

Power BI Refresh Error:
RestSinkCallFailed

What does this error mean?

An ADF copy activity writing data to a REST API endpoint (REST sink) received an error response from the target API. The HTTP call to the REST endpoint failed.

Common causes

1The REST API returned a non-success HTTP status code (4xx or 5xx)
2The API authentication token or API key is expired or invalid
3The request payload format does not match what the REST API expects (wrong JSON structure, missing required fields)
4The REST endpoint is temporarily unavailable or rate-limiting requests

How to fix it

1Check the ADF activity run output for the HTTP status code and response body returned by the REST API.
2Verify that the REST linked service authentication credentials (Bearer token, API key, OAuth) are valid and not expired.
3Review the request body mapping in the copy activity sink to ensure it matches the REST API contract.
4If the API is rate-limiting, add a retry policy to the copy activity with exponential backoff.
5Test the REST endpoint directly (e.g., with Postman) using the same credentials and payload to isolate the issue.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

In ADF Monitor, click the failed run, then the failed activity. The detail pane shows the error code, message, and sub-error codes.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-rest