Clay Icon
  • Avatar of Joel B.
    Joel B.
    ·
    ·

    outputs shown are from a previous run.

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Here are some troubleshooting steps to resolve JSON parsing issues:1. Check your string formatting: • Ensure all text values are enclosed in double quotes • Make sure dynamic column values are properly quoted 2. Review syntax carefully: • Check for proper comma separation between keys • Look for any extra spaces, colons, or brackets • Remove any trailing commas at the end 3. Clean up potential hidden characters: • Copy and paste your JSON into a plain text editor to spot any hidden characters • Remove any unexpected characters that might have been includedFor additional validation, you can use a tool like JSONLint (jsonlint.com) to check your JSON formatting, or ask an LLM to help identify and fix formatting issues. Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    To resolve JSON parsing issues, here are the key troubleshooting steps:1. Check your string formatting: • Ensure all keys and string values are enclosed in double quotes • If using dynamic column values, make sure they're properly quoted • For numbers with trailing zeros (like 0004), use quotes 2. Review syntax carefully: • Verify proper comma separation between keys • Check for extra spaces, colons, or brackets • Remove any trailing commas 3. Clean up hidden characters: • Copy and paste your JSON into a plain text editor to spot any hidden characters • Remove any unexpected characters that might have been includedFor additional validation, you can use JSONLint (jsonlint.com) or ask an LLM to help identify and fix formatting issues. Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University

  • Avatar of Joel B.
    Joel B.
    ·
    ·

    JSON lint showing as valid JSON

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Even if your JSON is valid according to JSONLint, there might still be formatting issues specific to Clay's requirements. Here are the key things to check:1. For dynamic values: • If using dynamic column values (/column), ensure they're properly quoted for strings • Numbers with trailing zeros (like 0004) must be in quotes • Regular numbers should not be in quotes 2. Check for these common issues: • Verify all keys are surrounded by double quotes • If combining plain text with dynamic column tags, create a Formula column first and then include that column (with quotes) in your body • Look for any hidden characters by pasting into a plain text editorIf the issue persists after checking these items, you may want to request human support for further assistance. Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Great! I'm here if you need any further assistance.

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

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