Freight LTL API

[scottsawyer]

FEATURE REQUEST

I am working on a Drupal Commerce FedEx patch to provide freight quotes.

According to https://developer.fedex.com/api/en-us/catalog/rate/v1/docs.html

Note: The Rate API does not provide the rate quotes for FedEx freight services. To know about the rate quotes of FedEx freight service, visit the Freight LTL API docs page.

Freight LTL API is a separate endpoint /rate/v1/freight/rates/quotes with different parameters.

I think in order to support freight requests, FedExRest\Services\Rates maybe should become a wrapper with two sub services, Rates and FreightRates, and be expanded to accept params for both.

[ash-g-1337]

Hi @scottsawyer
If you are able, I encourage you to fork and enhance this.
I was working on Freight LTL support (see my fork), however the project I was doing this for changed direction and I haven't had capacity to finish this. Additionally, there is a chance that FedEx may change things up since FedEx Freight and Ground are splitting -- dont let that discourage you tho.

[scottsawyer]

Ha, thanks @ash-g-1337 it seems Freight and Ground may have already split at the API level. i am looking at your fork, looks like you made some progress with FreightLTL, how far along would you say you've gotten? Did this stuff pretty much work when you last committed? Have you looked at freight rates at all yet?

[ash-g-1337]

I had to check my notes and re-open the repo to where I left off - I have pushed some left over changes from my local repo.

3 of the 5 APIs were done -- Was working on Rate -- one of the bigger entity "freightShipmentDetail" needs to be built out -- After that entity, the Rate component should work barring some edge cases and creating shipment should should be fairly easy since it would re-use most of entities from rate.

I did some unit testing, but not end to end testing. FedEx API behaves little different in their Testing Env vs their production -- it gets annoying to pass unit tests due to that since some same request would work fine in Production, but not in testing.

I just dont have the capacity for next few months as my current project does not intend to use direct FedEx Freight integration anytime soon (ill see if anyone on my team has any capacity to finish this, but no promises).

If you want to take an attempt at completing it, go right ahead -- I did most of this pre-AI, it should be much quicker now if I fed it FedEx documentation -- It could likely build out the entity in mins -- it would just take time to validate all of this.