This adds a new stream which uses the dispatch capacities endpoint to iteratively search technician availabilities by date range. It's a different pattern than any other endpoint and the data is modeled differently. I've chosen to do some of the cleaning and formatting here in the tap rather than leaving it to be done downstream because capacity data is only really useful for an analytics use case at the technician level like this. Basically, the API itself rolls things up a little bit and this is closer to what a reasonable "raw" data should look like in the context of raw data returned by the more typical GET endpoints in this tap.
This adds a new stream which uses the dispatch capacities endpoint to iteratively search technician availabilities by date range. It's a different pattern than any other endpoint and the data is modeled differently. I've chosen to do some of the cleaning and formatting here in the tap rather than leaving it to be done downstream because capacity data is only really useful for an analytics use case at the technician level like this. Basically, the API itself rolls things up a little bit and this is closer to what a reasonable "raw" data should look like in the context of raw data returned by the more typical GET endpoints in this tap.