​

1 What it does

• Sync data to internal systems — push to ERP / CRM, no manual handoff.
• Scraping — build a crawler, fetch web content, extract data.
• Integrate third-party services — payments, SMS, geolocation.

​

2 Notes

​

2.1 HTTP method

​

2.2 Parameters

​

2.2.1 GET

​

2.2.2 POST / PUT / PATCH / DELETE

• x-ddpaas-signature-timestamp: <signing timestamp>
• x-ddpaas-signature: <signature>

public static String calcSignature(String apiSecret, long ts) {
    try {
        Mac mac = Mac.getInstance("HmacSHA256");
        SecretKeySpec key = new SecretKeySpec(apiSecret.getBytes(), "HmacSHA256");
        mac.init(key);
        return Base64.getEncoder()
            .encodeToString(mac.doFinal(Long.toString(ts).getBytes()));
    } catch (NoSuchAlgorithmException | InvalidKeyException e) {
        log.error("sign api secret failed", e);
    }
}

​

2.2.3 Define the response (output)

• The HTTP response is passed downstream. The response format determines how downstream steps parse and reference these params.
• JSON — downstream steps parse the response as structured JSON. Fill in a sample response so downstream can reference fields.
• Text — downstream references the whole response as text.
• None — downstream cannot reference the response.

​

3 FAQ

​

3.1 FAQ

• Q: HTTP failure rules
  • status code ≠ 200
  • System exceptions, e.g. timeout.
• Q: What causes HTTP request timeouts? A: Causes — network latency, slow server response, firewall / proxy restrictions, DNS issues, or server overload.
• Q: Can the AI Table automation HTTP request use a fixed IP for IP-allow-listing? A: Yes. Most platforms allow outbound IP allow-lists or fixed IP binding via the platform admin or API gateway. IP ranges: 203.119.128.0/17, 59.82.0.0/16, 140.205.0.0/16, 106.11.0.0/16
• Q: Can I append query params directly in the URL? A: Yes — ?key1=value1&key2=value2 works for GET, and for some POST too (server-dependent).
• Q: Why does an HTTP request fail to parse correctly? How do I verify it? A: Causes:
  • Bad request format (e.g. JSON syntax errors).
  • Encoding issues (e.g. wrong Content-Type).
  • Server endpoint changed or version mismatched.
  • Missing required headers (e.g. auth token). Verification:
  • Replay the same request manually with Postman / curl.
  • Check the status code (4xx = client, 5xx = server).
  • Enable debug logging or capture with Wireshark.
• Q: What does a JSON-compliant HTTP response look like? A:
  • Structural rules:
    • Must be a valid JSON object ({}) or array ([]).
    • Field names quoted with double quotes ("key").
    • Supported types: string, number, boolean, object, array, null.
  • Common conventions: status code ("code"), message ("message"), data ("data").
• Q: Max number of key-value params in an HTTP request? A:
  • No hard limit, but bounded by:
    • URL length (recommended < 2048 chars).
    • Server parser limits (some servers cap param count).
    • Performance (avoid redundant params).
• Q: Can I reference array data from the HTTP response in downstream steps? A: Yes — loop over it, or compose fields when sending messages.
• Q: When using a group’s custom bot to send messages, the open-platform sample code doesn’t work as-is — what could be wrong? A:
  • Common issues:
    1. Wrong webhook URL — placeholder not replaced with the actual generated URL or token.
    2. Permission missing — bot not in the target group, or not authorized.
    3. Format mismatch — body doesn’t match API spec (e.g. wrong Content-Type).
    4. Signature failed — missing or wrong signature (timestamp / secret not computed).
    5. Network blocked — firewall or proxy blocking.
  • Fixes:
    • Double-check placeholders in the sample code (e.g. {token}).
    • Use a debug tool to inspect headers, body, and response.
    • Check the open-platform docs or contact support.