Swagger doesn’t seem to work for invoking methods with parameters from request body, but its there just for the API schema. Use Postman, or plain CURL for invoking.
Agree, normally I would do it that way, but there is relatively complex type I need as parameter, so I decided to implement it this way.
There is no database of dealers. It’s scraping tool that hits live dealer websites for information. Dealer info is stored in config file. Any dealer which website compatible with one of 3 implementations, could be added to the config
Yeah, that is true for GET requests. It sounds like it can do it for POST requests.
There is no database of dealers. It’s scraping tool that hits live dealer websites for information. Dealer info is stored in config file. Any dealer which website compatible with one of 3 implementations, could be added to the config
Yeah, I meant which dealer sites are in the config file for the API?
You call service to start search, get back result key and endpoint information, where results will be available when ready, and then you start polling result endpoint periodically, until results are ready.
Details:
We now have 2 operations:
First you invoke “StartSearch” operation. It will synchronously return “202 Accepted” status with ticket information, while starting actual search asynchronously in background.
You will get back searchKey for results retrieval, RetryAfter to tell you how often you should poll result endpoint, and result endpoint Uri.
You start periodically polling (but not quicker than retryAfter suggests) results endpoint, supplying searchKey as parameter. If results aren’t ready yet, you will get “202 Accepted” code with payload indicating that search is still in progress
Keep polling that endpoint until you get search results. You either get payload with success status and array of results, or with failure status and error message. In both cases it’ll be 200 OK code.
still totally real-time searches, no stale car data here lol
searches will never time out, no matter how long it takes to scrape all dealers for info
client-side paging, sorting and insanely useful FILTERING on all results that you get - lighting fast search on all columns in the grid, e.g. putting “xdr blue FWD” will filter down all results to only xDrive FWD cars in blue. Try it on all columns, VIN, stock, engine etc.
real-time search statistics showing how search is initiated, how it polls for results, and when it finishes
fancy spinning indicator, always my proudest accomplishment in any UI work, yeah baby!
On plus side, sterling new URL can set page size via query parameters, which removes the need to programmatically determine paging (which is not that reliable) and crawl each page to collect all stock.
I noticed one of my local MB sites did something similar. Seemed to be with the last update in their inventory and they moved couple other links around.
Yup, this is unfortunate if dealers do it often enough. With this change, which was broken filter at dealer’s, it was easy enough to spot, by seeing not relevant to search results. But if URL changes drastically, some sites might start erroring out and stop providing results completely. Those would be hard to spot. Gotta periodically check logs to catch offenders like that.
Added bunch of tri-state Hyundai dealers, 90% of those are plug and play DealerCom sites, excellent uniformity. Search for Sonata for example is sitting around 600 units.
Since I’m scraping this info from dealer’s search page, not all packages might be there. You can click individual listing link to see all packages, if they are also listed on dealer details page.
I’m going on vacation tomorrow, so most likely there will be no updates for next week. Have fun with search everyone and let me know what else can we add to it.
added 30 tri-state and PA Audi dealers for all your east coast audi searching needs
Line 3: Audi Allentown
Line 4: Audi Bridgewater
Line 5: Audi Brooklyn
Line 6: Audi Devon
Line 7: Audi Eatontown
Line 8: Audi Fort Washington
Line 9: Audi Freehold
Line 10: Audi Greenwich
Line 11: Audi Hawthorne
Line 12: Audi Hunt Valley
Line 13: Audi Mechanicsburg
Line 14: Audi Mendham
Line 15: Audi Newton
Line 16: Audi of Huntington
Line 17: Audi Princeton
Line 18: Audi Reading
Line 19: Audi State College
Line 20: Audi Warrington
Line 21: Audi West Chester
Line 22: Audi Wynnewood
Line 23: Audi Wyoming Valley
Line 26: Bell Audi
Line 31: Biener Audi
Line 68: DCH Millburn Audi
Line 70: Fiore Audi
Line 71: Flemington Audi
Line 87: Jack Daniels Audi of Paramus
Line 88: Jack Daniels Audi of Upper Saddle River
Line 96: Mohegan Lake Audi
Line 116: Town Audi