Enhance Jotform Nutrition API Integration
Budget: $50 – $0 USD
My Jotform Enterprise app uses an AI agent to answer customers’ nutrition questions by querying the USDA FoodData Central API. Straight-forward items like “chicken” work, but anything more complex—“chicken taco,” “veggie lasagna,” mixed dishes, branded items—returns partial or scrambled results. Data comes back incomplete and, when it does arrive, macronutrients are sometimes mapped to the wrong fields, so protein appears as carbs, fats drop to zero, etc.
I need someone who can dive into the existing integration, trace the request/response cycle, and correct both problems:
• Guarantee full, reliable data retrieval for multi-ingredient or prepared foods.
• Fix the misclassification logic so calories, protein, carbs, and fats land in their proper properties every time.
You can have access to my Jotform workspace but have to sign a BCA because of HIPPA privacy laws, current webhook scripts, and the Open API connection I already built for FoodData Central. Ideally you’re comfortable with REST APIs, JSON parsing, Jotform’s server-side features, and you know your way around nutrition databases; bonus points if you’ve handled FDC’s Foundation, SR Legacy, and Branded endpoints before.
Acceptance is simple: when I can ask, “What are the calories, carbs, and protein in a chicken taco (2 medium tortillas)?” and receive a complete, correctly mapped response inside the chat interface, the job is done.
I need someone who can dive into the existing integration, trace the request/response cycle, and correct both problems:
• Guarantee full, reliable data retrieval for multi-ingredient or prepared foods.
• Fix the misclassification logic so calories, protein, carbs, and fats land in their proper properties every time.
You can have access to my Jotform workspace but have to sign a BCA because of HIPPA privacy laws, current webhook scripts, and the Open API connection I already built for FoodData Central. Ideally you’re comfortable with REST APIs, JSON parsing, Jotform’s server-side features, and you know your way around nutrition databases; bonus points if you’ve handled FDC’s Foundation, SR Legacy, and Branded endpoints before.
Acceptance is simple: when I can ask, “What are the calories, carbs, and protein in a chicken taco (2 medium tortillas)?” and receive a complete, correctly mapped response inside the chat interface, the job is done.
Related categories:
PHP
JavaScript
Software Architecture
MySQL
Nutrition
Software Development
JSON
Data Integration
API Development
REST API