This endpoint returns all the available plugins that can be used to make requests to carrier specific schedule endpoints (such as POST /schedule)

This method allows for the synchronous or asynchronous (using the mode query parameter) retrieval of a carrier's schedule. Making this request, a process will be started on the server that collects the schedules. When running the process synchronously, your request will wait until the job has completed or until it times out (usually after 60 seconds.) When running the request asynchronously (recommended) you may retrieve the status and results using the /schedule/{request_id} endpoint (the request_id being the value provided in the 202 result body of this request.) When the status field in the returned body contains the value PENDING, the job has not yet completed and no results are available. When the value for the status field is COMPLETED or FAILED the final result is available and no further updates to the set are to be expected.

Note that the cached resultset will expire after 300 seconds so your call must be made within this timeframe.

Use this method to retrieve the results of an earlier made asynchronous request. When the status field in the returned body contains the value PENDING, the job has not yet completed and no results are available. When the value for the status field is COMPLETED or FAILED the final result is available and no further updates to the set are to be expected. You may call this method multiple times to retrieve its state, but note the requests get throttled. Observe the response headers to retrieve the throttle state.

This method allows for the asynchronous retrieval of a parsed schedule set. Making this request, a process will be started on the server that collects the schedules and parses them to the schema. At any time you may retrieve the intermediate results using the /schedules/{request_id} endpoint (the request_id being the value provided in the 202 result body of this request.) When the status field in the returned body contains the value PENDING, intermediate results will be provided. When the value for the status field is COMPLETED or FAILED the final result is available and no further updates to the set are to be expected.

Note that the cached resultset will expire after 300 seconds so your call must be made within this timeframe.

Use this method to retrieve the (intermediate) results of an earlier made request. When the status field in the returned body contains the value PENDING, intermediate results will be provided. When the value for the status field is COMPLETED or FAILED the final result is available and no further updates to the set are to be expected. When the job has not yet completed raw data will be parsed on request which may cause some additional latency, as the chained job becomes completed the parsed resuls will be served directly. You may call this method multiple times to provide partial result sets in your client, but note the requests get throttled. Observe the response headers to retrieve the throttle state.