关于新增Smart Quotes(v2)特定客户quoteIds查询API的问询

Totally get where you're coming from—needing to pull all quote IDs tied to a specific customer is such a common, practical use case, and it’s frustrating that the Quotes(Smart)(v2) API only offers GET /v2/quotes/{quoteId} for individual quote details. Here’s how to approach this:

1. Double-Check for Hidden Workarounds First #

• Before requesting a new endpoint, quickly scan the full Home Portal API docs again to see if there’s an existing way to get this data:
  • Is there a v1 version of the Quotes API that includes a list endpoint with customer ID filtering? Sometimes older versions retain features that newer ones haven’t caught up to.
  • Do customer-related endpoints (like GET /v2/customers/{customerId}) include a nested list of associated quote IDs? Some APIs tuck these cross-references into parent resource responses.
  • If there’s a general GET /v2/quotes endpoint (even without filtering), could you paginate through all quotes and filter by customer ID on your end? Note: This is only feasible if the total number of quotes isn’t massive—otherwise it’s inefficient.

2. Formal Request for the New Endpoint #

If no workarounds exist, here’s how to make a strong case for adding this feature:

• Reach out to the API maintainers: Contact the Home Portal support team or product owner directly (via their official channels—support tickets, feedback forms, etc.).
• Be specific about your use case: Explain exactly why you need this endpoint (e.g., "We need to bulk update quote statuses for a customer, or generate monthly reporting on all quotes tied to their account"). Concrete examples help teams prioritize feature requests.
• Propose a clear endpoint structure: Suggest something intuitive like:

  GET /v2/quotes?customerId={customerId}
  

  Mention adding optional query parameters like limit or offset for pagination, or status to filter quotes by their state—this shows you’ve thought through the practicality of the feature.
• Highlight the impact of the gap: If you’re currently using manual workarounds (like tracking quote IDs in a spreadsheet) or can’t complete critical workflows, share that detail. It helps the team understand the urgency.

3. Temporary Stopgap (If You Can’t Wait) #

If you need a solution immediately, consider storing quote IDs in your own system as they’re created:

• Whenever you generate a quote for a customer via the API, save the quoteId and associated customer ID to your internal database. This way, you can retrieve the full list of quotes for a customer from your own records instead of relying on the API. Just note this only covers quotes created after you set up this tracking.

内容的提问来源于stack exchange，提问作者tania_dm