Clay Icon
  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    To fix the "Failed to parse body input" error when making a POST request, ensure your JSON body is properly formatted: 1. Use double quotes around all keys and string values: ```

    { "name": "John", "age": 30 } ```2. For dynamic column values: • Wrap string values in quotes • Leave numbers without quotes (except for numbers with trailing zeros) • Use proper JSON syntax with commas between key-value pairsCommon issues to check: ** Remove any trailing commas ** Check for extra spaces or hidden characters * Verify all brackets and colons are properly placedIf you're still having trouble, try pasting your JSON into a validator like JSONLint to spot formatting issues. Sources: HTTP API integration overview | Clay University HTTP API with JWT authentication | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?

  • Avatar of Pek
    Pek
    ·
    ·

    I think it already is:

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Here's how to properly format your JSON body for a POST request: 1. Use double quotes around all keys and string values: ```

    { "name": "John", "age": 30 } ```2. When using dynamic column variables (/column): • Wrap string values in quotes • Leave numbers without quotes (except for numbers with trailing zeros) • Remove any trailing commasKey formatting rules: ** All keys must be surrounded by double quotes ** If combining plain text with a dynamic column tag, create a Formula column first ** Ensure keys are separated by commas ** Be careful with extra spaces, colons, and bracketsFor validation, try pasting your JSON into a validator like JSONLint to spot any formatting issues. Sources: HTTP API integration overview | Clay University HTTP API with JWT authentication | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Hi Pek! This thread was recently closed by our Support team. If you have a moment, please share your feedback: