/api6/leads` endpoint caps at 200 records full lead history not accessible

I have another Dev Question

What we're seeingWe're integrating GoHighLevel with the Inflatable Office REST API (/api6/leads) using our

account API key to sync our full lead/opportunity history into an external

dashboard. The endpoint appears to cap the total number of leads returned at

200, regardless of the limit or offset parameters we send.

ReproductionCalling the endpoint with pagination:

GET https://rental.software/api6/leads?apiKey={KEY}&_body=true&limit=100&offset=0 → 100 leads (page 1) GET https://rental.software/api6/leads?apiKey={KEY}&_body=true&limit=100&offset=100 → 100 leads (page 2) GET https://rental.software/api6/leads?apiKey={KEY}&_body=true&limit=100&offset=200 → fetch fails / no results GET https://rental.software/api6/leads?apiKey={KEY}&_body=true&limit=5000 → still only 200 leads

• Total leads returned: 200 (2 pages of 100), then pagination stops.
• We have significantly more historical leads than 200 in the account (visible
  in the IO calendar and lead list UI), so the API is truncating our history.

Status breakdown of the 200 returned leads

Questions:

1. Is there a hard cap of 200 leads on the /api6/leads endpoint? If so, can
   it be raised or removed for our account so we can pull our full lead history?
2. Is there a recommended way to retrieve all-time historical leads — e.g. a
   date-range filter parameter (from/to, startdate/enddate), a
   created_after cursor, or a separate export/bulk endpoint?
3. Are "Temporary" leads (140 of 200) intended to be returned by the API?
   These appear to be unfinished/incomplete form submissions with no real
   customer name, email, or phone. Is there a parameter to exclude them, or a
   status filter so we can request only specific statuses (e.g. Quote,
   Signed, Complete)?
4. Is there an endpoint to retrieve the full rides/inventory catalog
   (/api6/rides)? It currently returns a 404 for our account, so we can only
   name rented items via the inline rentals object on each lead.

What we need

• The ability to retrieve all historical leads (not just the most recent
  200), ideally via date-range filtering or an increased pagination cap.
• Confirmation of any filter parameters supported by /api6/leads
  (status, date range, etc.).
• (Optional) Access to a working rides catalog endpoint.

Account info

• Subdomain: bouncehousewilmington
• Endpoint: https://rental.software/api6/leads
• Auth: API key (provided separately / on file)

Thank you!