Scheduled feed URL
Let Legend pull an approved inventory export on a recurring schedule.
When to use it
A practical fit for your existing workflow.
Merchants that already publish a stable HTTPS export and want hands-off refreshes.
Input contract
Fields and structure
Use stable field names and meanings across every refresh. Legend normalizes the values, but the source contract should not drift silently.
Required or expected
Public or authenticated HTTPS URLStable file structureAt least one refresh every 24 hoursFull catalogue snapshots when missing offers should be deactivated
Recommended fields
feed_urlformatinterval_hoursdeactivate_missing
Supported variations
- HTTP authentication during onboarding
- Custom request headers
- IP allow-listing
- Non-daily refresh schedule
Copyable example
Scheduled source request
Replace the demonstration values with your own catalogue data. No customer, order, or payment data belongs in an inventory feed.
JSON
{
"feed_url": "https://merchant.example/legend-feed.csv",
"format": "lqrs",
"interval_hours": 24,
"deactivate_missing": true
}From source to live offer
Connection workflow
Every route uses the same quality gates before an offer becomes public.
Publish the export at a stable HTTPS URL.
Validate the source without changing live offers.
Save the URL and refresh schedule in Business Manager.
Review each import, match rate, and any rejected rows.
Before publication
Validation checklist
These checks keep bad prices, stale stock, and uncertain product matches out of the public marketplace.
- The URL must use HTTP or HTTPS.
- The selected parser must match the returned file.
- A full snapshot is required before deactivate_missing can be enabled safely.
- Redirects, timeouts, and parser errors remain visible in import diagnostics.
Other connection paths