The health endpoint provides a single-call overview of every supplier’s sync state. It runs two optimized queries (window functions, no N+1) and returns the results in one response — useful for dashboards, alerting, and spotting suppliers that need attention.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/VisualGraphxLLC/API-HUB/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
auth_token cookie (admin login).
Example:
Response
ISO 8601 timestamp when the health snapshot was computed
Array of
SupplierSyncHealth objects — one per supplierInterpreting the results
consecutive_failures > 0
consecutive_failures > 0
The supplier’s last N jobs all failed. Check the supplier’s auth credentials and whether their API endpoint is reachable. For PromoStandards suppliers, SOAP fault codes
100, 104, or 110 indicate an auth problem — re-enter credentials in the supplier form.recent_error_count is high but consecutive_failures is low
recent_error_count is high but consecutive_failures is low
Intermittent failures — the supplier API is unstable or rate-limiting. Review the
errors JSONB in the individual job records (GET /api/sync-jobs?supplier_id={id}) to identify which products are failing.last_full_sync is null
last_full_sync is null
No full sync has ever completed for this supplier. Trigger one with
POST /api/suppliers/{id}/import and mode=full_sellable.last_sync_status is partial_success
last_sync_status is partial_success
The job completed but some products failed hydration. Check
failed_count and errors on the specific job record. Partial success is normal for large catalogs with occasional bad data.