NVM Problem solved thanks

4 comments

· Sorted by Oldest

Max J.
·
·
Hi Azrael B.! Welcome to the community. My apologies for not getting to your request sooner we are around typically Monday - Friday Pacific Time. What turned out to be the issue? Was it an API key or that trailing slash? I am not personally familiar with the platform you are using.
Azrael B.
·
·
not sure, someone on the automation platform side, got it working but the body format Raw is {"inputText":"power","numCards":10,"cardSplit":"auto","additionalInstructions":" Make the titles catchy.","textOptions":{"amount":"brief","tone":"professional","audience":" tech investors"},"imageOptions":{"source":"aiGenerated"},"cardOptions":{"dimensions":"16x9"}}
Azrael B.
·
·
however this body which is assume is also raw, ( i dont know code) doesnt work {"inputText":""# The Final Frontier: Deep Sea Exploration\n* Less than 20% of our oceans have been explored\n* Deeper than 1,000 meters remains largely mysterious\n* More people have been to space than to the deepest parts of our ocean\n---\n# Technological Breakthroughs\n* Advanced submersibles capable of withstanding extreme pressure\n* ROVs (Remotely Operated Vehicles) with HD cameras and sampling tools\n* Autonomous underwater vehicles for extended mapping missions\n* Deep-sea communication networks enabling real-time data transmission\n---\n# Ecological Discoveries\n* Unique ecosystems thriving without sunlight\n* Hydrothermal vent communities using chemosynthesis\n* Creatures with remarkable adaptations: bioluminescence, pressure resistance\n* Thousands of new species discovered annually\n---\n# Scientific & Economic Value\n* Understanding climate regulation and carbon sequestration\n* Pharmaceutical potential from deep-sea organisms\n* Mineral resources and rare earth elements\n* Insights into extreme life that could exist on other planets\n---\n# Future Horizons\n* Expansion of deep-sea protected areas\\n* Sustainable exploration balancing discovery and conservation\n* Technological miniaturization enabling broader coverage\n* Citizen science initiatives through shared deep-sea data","numCards":10,"cardSplit":"auto","additionalInstructions":" Make the titles catchy.","textOptions":{"amount":"brief","tone":"professional","audience":" tech investors"},"imageOptions":{"source":"aiGenerated"},"cardOptions":{"dimensions":"16x9"}}
Max J.
·
·
Hey! I can see what happened with that first issue - your platform support fixed the header formatting (the `Content-Type:` key had a colon in it, and there was a trailing backslash in the URL). Glad they got that sorted! Now for your second body - I see a couple of JSON formatting issues that are tripping things up: Right at the start: `"inputText":""# The Final Frontier...` That double quote after the colon is the problem. Should be: `"inputText":"# The Final Frontier...` And there's one spot with `\\n` (double backslash) that should be `\n`. Quick note: The `\n` characters you're using are actually correct! That's how we handle card separators in markdown, so that part is working as designed. Here's a super helpful tool: paste your JSON into https://jsonlint.com/ - it'll catch these formatting issues and show you exactly where they are. Makes troubleshooting JSON way easier! Once the JSON syntax is clean, the Gamma API should handle your markdown content without issues. The newlines and formatting you're using look good from our end. Let me know if you hit any Gamma-specific errors after getting the JSON sorted!

Max J.
·
·
Hi Azrael B.! Welcome to the community. My apologies for not getting to your request sooner we are around typically Monday - Friday Pacific Time. What turned out to be the issue? Was it an API key or that trailing slash? I am not personally familiar with the platform you are using.
Azrael B.
·
·
not sure, someone on the automation platform side, got it working but the body format Raw is {"inputText":"power","numCards":10,"cardSplit":"auto","additionalInstructions":" Make the titles catchy.","textOptions":{"amount":"brief","tone":"professional","audience":" tech investors"},"imageOptions":{"source":"aiGenerated"},"cardOptions":{"dimensions":"16x9"}}
Azrael B.
·
·
however this body which is assume is also raw, ( i dont know code) doesnt work {"inputText":""# The Final Frontier: Deep Sea Exploration\n* Less than 20% of our oceans have been explored\n* Deeper than 1,000 meters remains largely mysterious\n* More people have been to space than to the deepest parts of our ocean\n---\n# Technological Breakthroughs\n* Advanced submersibles capable of withstanding extreme pressure\n* ROVs (Remotely Operated Vehicles) with HD cameras and sampling tools\n* Autonomous underwater vehicles for extended mapping missions\n* Deep-sea communication networks enabling real-time data transmission\n---\n# Ecological Discoveries\n* Unique ecosystems thriving without sunlight\n* Hydrothermal vent communities using chemosynthesis\n* Creatures with remarkable adaptations: bioluminescence, pressure resistance\n* Thousands of new species discovered annually\n---\n# Scientific & Economic Value\n* Understanding climate regulation and carbon sequestration\n* Pharmaceutical potential from deep-sea organisms\n* Mineral resources and rare earth elements\n* Insights into extreme life that could exist on other planets\n---\n# Future Horizons\n* Expansion of deep-sea protected areas\\n* Sustainable exploration balancing discovery and conservation\n* Technological miniaturization enabling broader coverage\n* Citizen science initiatives through shared deep-sea data","numCards":10,"cardSplit":"auto","additionalInstructions":" Make the titles catchy.","textOptions":{"amount":"brief","tone":"professional","audience":" tech investors"},"imageOptions":{"source":"aiGenerated"},"cardOptions":{"dimensions":"16x9"}}
Max J.
·
·
Hey! I can see what happened with that first issue - your platform support fixed the header formatting (the `Content-Type:` key had a colon in it, and there was a trailing backslash in the URL). Glad they got that sorted! Now for your second body - I see a couple of JSON formatting issues that are tripping things up: Right at the start: `"inputText":""# The Final Frontier...` That double quote after the colon is the problem. Should be: `"inputText":"# The Final Frontier...` And there's one spot with `\\n` (double backslash) that should be `\n`. Quick note: The `\n` characters you're using are actually correct! That's how we handle card separators in markdown, so that part is working as designed. Here's a super helpful tool: paste your JSON into https://jsonlint.com/ - it'll catch these formatting issues and show you exactly where they are. Makes troubleshooting JSON way easier! Once the JSON syntax is clean, the Gamma API should handle your markdown content without issues. The newlines and formatting you're using look good from our end. Let me know if you hit any Gamma-specific errors after getting the JSON sorted!