POST /content

This endpoint allows you to request a new content on any topic. The request is processed asynchronously, and you'll receive a request ID that you can use to check the status and retrieve the results.

Endpoint

Request Parameters

Parameter Details

topic

The topic parameter should be a specific question or topic you want to analyze. It can be a broad topic like "AI trends in healthcare" or a specific question like "What are the latest developments in quantum computing?". The more specific your topic, the more focused the content will be.

data_structure

The data_structure parameter defines the structure of the custom JSON response, allowing you to get results in exactly the format your application needs. It should be a JSON object that defines the structure you want, with field names as keys and field types and descriptions as values.

Supported types are:

• "string" - Text fields
• "number" - Numeric values
• "boolean" - True/false values
• [] - Arrays (e.g., ["string"] for an array of strings)
• {} - Nested objects

The TrendiFi API requires a data_structure parameter that defines exactly how you want your content data to be organized. This allows you to get data in a format that perfectly matches your application's needs:

// POST https://trendifi.app/api/v1/content
        {
          "topic": "Electric vehicles market trends",
          "data_structure": {
            "summary": "string - concise overview of current EV market trends in 2-3 sentences",
            "key_trends": [{
              "name": "string - short name of a specific market trend",
              "description": "string - detailed explanation with supporting data points",
              "impact_score": "number - rating from 1-10 of market impact"
            }],
            "market_leaders": ["string - names of top companies with brief description of their market position"],
            "regional_insights": {
              "north_america": "string - key developments and adoption rates in North American markets",
              "europe": "string - regulatory environment and market growth in European countries",
              "asia": "string - manufacturing trends and consumer adoption in Asian markets"
            },
            "forecast": {
              "growth_rate": "number - projected annual growth percentage for next 3 years",
              "challenges": ["string - specific obstacles facing the industry with potential solutions"],
              "opportunities": ["string - emerging areas for innovation and investment"] 
            }
          }
        }

This tells the AI how to structure the response, allowing you to programmatically render the data in your application without additional parsing.

Code Examples

# Request new content with data structure
curl -X POST https://trendifi.app/api/v1/content \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "topic": "Tesla stock performance",
  "data_structure": {
    "market_summary": {
      "price_change": "number - percentage change in stock price over last 30 days",
      "trading_volume": "number - average daily trading volume in millions",
      "key_metrics": ["string - important financial indicators with current values"]
    },
    "analysis": {
      "short_term_outlook": "string - 1-2 paragraph analysis of 3-month prospects",
      "long_term_outlook": "string - 1-2 paragraph analysis of 1-year prospects",
      "risk_factors": ["string - specific risks that could impact stock performance"]
    },
    "recommendations": ["string - actionable investment advice based on the analysis"]
  }
}'

# Response
{
  "request_id": "req_8f7d6e5c4b3a2910", 
  "status": "processing", 
  "created_at": "2025-05-30T14:32:10Z"
}

Response

The POST /content endpoint returns a response with a request ID that you can use to check the status of your content request and retrieve the results when processing is complete.

Response Fields

Example Response

{
  "request_id": "ins_8f7d6e5c4b3a2910",
  "status": "processing",
  "created_at": "2023-09-15T14:32:10Z"
}

Error Handling

{
  "error": {
    "message": "No topic provided",
    "error_code": "missing_topic"
  }
}

{
  "error": {
    "code": "not_found",
    "message": "Insight with ID 'ins_01H9XK7ABCDEFGHIJKLMNOPQRS' not found"
  }
}

Next Steps