API Response Codes

Every Fivetran REST API response includes an HTTP status code. Most responses also include a JSON body with a code field and a message field.

Use the HTTP status code to determine whether the request succeeded. If it failed, use the code field for programmatic error handling and the message field for a human-readable explanation.

{
    "code": "NotFound_Connector",
    "message": "Connector with id 'abc123' does not exist."
}

Supported HTTP status codes

Fivetran code values

The code field in responses is a stable string identifier. Use code, not message, to branch your error handling logic.

The following table covers common code values. Some endpoints return additional codes specific to their resource type. Each connector also returns its own connector-specific code values. Refer to the individual endpoint reference pages for the code values specific to that endpoint.

Error handling example based on code

RESPONSE=$(curl -s -w "\n%{http_code}" \
  -H "Accept: application/json" \
  -u "$FIVETRAN_API_KEY:$FIVETRAN_API_SECRET" \
  "https://api.fivetran.com/v1/connections/abc123")

HTTP_STATUS=$(echo "$RESPONSE" | tail -1)
BODY=$(echo "$RESPONSE" | sed '$d')
CODE=$(echo "$BODY" | python3 -c "import json,sys; print(json.load(sys.stdin).get('code',''))")

if [ "$HTTP_STATUS" -ge 400 ]; then
  case "$CODE" in
    "NotFound_Connector")
      echo "Connection not found. Check the connectionId."
      ;;
    "Unauthorized")
      echo "Invalid API key or secret. Check your credentials."
      ;;
    "TooManyRequests")
      echo "Rate limited. Wait for the Retry-After value before retrying."
      ;;
    *)
      echo "Unexpected error: $CODE"
      ;;
  esac
fi

Fivetran-specific success behavior

A 2xx response confirms we accepted your request, but it doesn't always mean the operation has completed or succeeded. Some endpoints return 2xx for asynchronous operations, deferred actions, or requests that require additional validation in the response body.