Skip to main content

​
Understanding the Response Status

The data.status field indicates the outcome of the request:
StatusMeaningWhen This Occurs
"filled"All requested offers were filledreturned == requested
"partial_fill"Some offers filled (multi-offer mode)0 < returned < requested
"no_offers_found"No offers availablereturned == 0 (no keywords detected, no links found, or filtered)
"internal_error"Service failureTimeout, service unavailable, or unexpected error
Example response with no offers: 
{
  "data": {
    "status": "no_offers_found",
    "offers": [],
    "requested": 1,
    "returned": 0
  },
  "error": null
}
The offers array only contains offers with URLs. If the array is empty, check the status field to understand why no offers were returned.

​
Common Causes

returned: 0 in response

Symptoms: API returns successfully but data.returned is 0.Possible causes:
  1. No product detected - The message doesn’t contain a clear product reference 
    // This won't match
{ "message": "Hello, how are you?" }

// This will match
{ "message": "What's a good yoga mat for beginners?" }
  2. Intent score too low - Query filtered by intent threshold 
    // status will be no_offers_found
{
  "data": {
    "status": "no_offers_found",
    "offers": [],
    "returned": 0
  }
}
  3. No affiliate available - Product identified but no affiliate link exists
  4. Message too short - After sanitization (removing PII, URLs, blocked keywords), no words remain 
    // Example: "user@email.com" becomes empty after sanitization
// Single-word product names are supported
Solutions:
  • Use more specific product queries
  • Check the status field for specifics