如何将可正常运行的CURL/XHR请求改写为适配Google Apps Script的代码

云原生阿岚

2026-10-4

修复后的可运行代码

function callPolygonRPC() {
  const rpcUrl = "https://rpc-mainnet.maticvigil.com/";
  const payload = {
    jsonrpc: "2.0",
    id: "dontcare",
    method: "eth_call",
    params: [
      {
        from: "0x0000000000000000000000000000000000000000",
        data: "0x7b84daec00000000000000000000000000000000000000000000000000000000000000280000000000000000000000009fd15feb6f86d2da6a3ac17372debd1db4e02e93",
        to: "0xbda1f897e851c7ef22cd490d2cf2dace4645a904"
      },
      "latest"
    ]
  };

  const options = {
    method: "POST",
    contentType: "application/json",
    payload: JSON.stringify(payload),
    muteHttpExceptions: true
  };

  const response = UrlFetchApp.fetch(rpcUrl, options);
  Logger.log("状态码：" + response.getResponseCode());
  Logger.log("返回结果：" + response.getContentText());
}

核心修改点

移除了所有无效冗余配置：mode、credentials、referrerPolicy以及sec-*开头的浏览器专属请求头、referrer字段等，这些参数是浏览器Fetch API的专属配置，Google Apps Script的UrlFetchApp并不支持，多余的请求头还会触发公共RPC节点的安全拦截机制。
不再手动拼接转义JSON字符串，改用JSON.stringify()自动生成请求体，避免转义错误导致JSON结构异常，触发节点返回Unrecognized JSONRPC command错误。
增加muteHttpExceptions: true配置，请求返回非200状态码时不会直接抛出异常，方便拿到完整返回内容排查问题。
直接用UrlFetchApp内置的contentType字段配置请求类型，不需要手动在headers里加Content-Type。