logo
Welcome to our new AbleCommerce forums. As a guest, you may view the information here. To post to this forum, you must have a registered account with us, either as a new user evaluating AbleCommerce or an existing user of the application. For all questions related to the older version of Gold and earlier, please go to AbleCommerce Gold forum. Please use your AbleCommerce username and password to Login. New Registrations are disabled.

Notification

Icon
Error

Options
Go to last post Go to first unread
Jay  
#1 Posted : Thursday, March 21, 2024 10:59:18 AM(UTC)
Jay

Rank: Member

Groups: Authorized User, Developers
Joined: 11/12/2018(UTC)
Posts: 25

Thanks: 1 times
Was thanked: 4 time(s) in 3 post(s)
I'm trying to get FedEx with OAuth working on a our 9.0.9 development site. I got the test keys and account # and configured the plugin to use test mode and debug mode. I've run into the following issues.

1. While setting up a project on FedEx's developer site, the Track API can not be selected with any of the other APIs. It looks like an either/or choice (either only Tracking or any combination of other). I selected Address Validation API and Rates and Transit Times API.

2. On the AC configuration page, if I set Pickup Type to "Regular stop", the debug log shows the following response:
Code:
Receive: {"transactionId":"c286c7c1-f01c-4775-9a7d-0aec92255531","errors":[{"code":"INVALID.INPUT.EXCEPTION","message":"Invalid field value in the enum pickupType"}]}

Relevant line in sent data is: "pickupType": "REGULAR_STOP",)

3. If I choose a different Pickup Type, I get the following response:
Code:
Receive: {
  "transactionId" : "APIF_SV_RATC_TxID607eddad-0918-4e6c-93c0-eef236e4568b",
  "errors" : [ {
    "code" : "REQUEST.MISMATCH",
    "message" : "The response is unavailable for the request payload sent to this virtualized sandbox instance. Please use the exact request payload from API JSON Collection available for download through FedEx Developer Portal and try again."
  } ]
}

An example of the sent date is (account number masked by me):
Code:
Send: {
  "accountNumber": {
    "value": "XXXXXXXXX"
  },
  "requestedShipment": {
    "shipper": {
      "contact": null,
      "address": {
        "city": "Chesterton",
        "stateOrProvinceCode": "IN",
        "postalCode": "46304",
        "countryCode": "US",
        "residential": false,
        "streetLines": [
          "1200 Cuting Edge Dr.",
          ""
        ]
      }
    },
    "recipients": null,
    "recipient": {
      "contact": null,
      "address": {
        "city": "SACRAMENTO",
        "stateOrProvinceCode": "CA",
        "postalCode": "95828",
        "countryCode": "US",
        "residential": false,
        "streetLines": [
          "8425 CARBIDE COURT",
          ""
        ]
      }
    },
    "shipDatestamp": null,
    "pickupType": "USE_SCHEDULED_PICKUP",
    "serviceType": null,
    "packagingType": null,
    "blockInsightVisibility": false,
    "shippingChargesPayment": null,
    "labelSpecification": null,
    "requestedPackageLineItems": [
      {
        "weight": {
          "units": "LB",
          "value": 10.0
        },
        "dimensions": null,
        "declaredValue": {
          "amount": 30.0,
          "currency": "USD"
        },
        "groupPackageCount": 0
      }
    ],
    "rateRequestType": [
      "LIST"
    ],
    "ShipmentSpecialServices": null
  },
  "carrierCodes": [
    "FDXE",
    "FDXG"
  ]
}

I tried several different combinations of the Rate Request Type, Enable Package Breakup, and Include Declared Value For Insurance settings, all get same response.

Does anyone have FedEx with OAuth working? Any ideas for resolving the issue?

Wanna join the discussion?! Login to your AbleCommerce Forums forum account. New Registrations are disabled.

Katie S  
#2 Posted : Thursday, March 21, 2024 1:36:13 PM(UTC)
Katie S

Rank: Advanced Member

Groups: System, Administrators, Developers, Registered, HelpDesk
Joined: 10/29/2018(UTC)
Posts: 423

Thanks: 4 times
Was thanked: 34 time(s) in 33 post(s)
Hi Ray,

The Track API should have been available. I'm wondering if something changed after I wrote these instructions.

Quote:
============= MIGRATING TO FEDEX OATH ============================

FedEx requires clients to obtain API keys through the FedEx Developer Portal.

1. Go to https://developer.fedex.com/api/en-us/home.html
2. Create a developer account with FedEx.
3. Access the My Projects page using the sidebar menu.
4. Create a Project.
5. Select the option "I work for a company that ships with FedEx and needs to integrate
FedEx technology into their system."
6. Give your project a name.
7. Select the following 3 supported API's:

- Address Validation API
- Rates and Transit Times API
- Track API

8. Continue and agree to the certification summary.
9. Accept terms (step 2) by reading and agreeing (I Accept) as shown on-screen.
10. Step 3 - configure the project by assigning a country and creating the project.


For the second issue, I'm going to retest and see what's going on with the Pickup Type.

Did you try the default value for Pickup Type?

I'll try to get back to you tomorrow.

Thanks
Thanks for your support!

Katie
Secure eCommerce Software and Hosting
Jay  
#3 Posted : Thursday, March 21, 2024 2:58:59 PM(UTC)
Jay

Rank: Member

Groups: Authorized User, Developers
Joined: 11/12/2018(UTC)
Posts: 25

Thanks: 1 times
Was thanked: 4 time(s) in 3 post(s)
I did a little digging on #2, according to this page of the API reference guide the REGULAR_STOP type (and a couple others) is only associated with the Pickup API, not the Rate API. Using USE_SCHEDULED_PICKUP is fine for my use case.

As you mentioned, I'm guessing #1 is a result of a change on their end since you created and tested your plugin.

Regarding #3, when I open my project, there is a "How to use the FedEx testing environment" bar with a drop arrow, and clicking it mentions (among other things) virtualization with a link to this page with some more info. Didn't have time to investigate further; I can't tell if they are saying you have to use their "canned" test requests, or only that if you do, it will go to the virtual server instead of the test server.
Jay  
#4 Posted : Friday, March 22, 2024 8:57:16 AM(UTC)
Jay

Rank: Member

Groups: Authorized User, Developers
Joined: 11/12/2018(UTC)
Posts: 25

Thanks: 1 times
Was thanked: 4 time(s) in 3 post(s)
Interesting - it seems to be working this morning now (with "Use scheduled pickup" as the PickUp type). The rates don't match what the "old" FedEx plugin is returning though. It seems like the settings match, but I'll do some testing to see if I can get a configuration that returns matching rates.
Katie S  
#5 Posted : Friday, March 22, 2024 10:39:49 AM(UTC)
Katie S

Rank: Advanced Member

Groups: System, Administrators, Developers, Registered, HelpDesk
Joined: 10/29/2018(UTC)
Posts: 423

Thanks: 4 times
Was thanked: 34 time(s) in 33 post(s)
Good Morning Jay,

Thanks for the update. I'm glad to see that things are partially working. If you don't mind, please keep us updated. I'll try to get the plugin installed over the weekend and figure out what happened to the tracking API.

Thanks for your support!

Katie
Secure eCommerce Software and Hosting
Jay  
#6 Posted : Tuesday, March 26, 2024 3:36:15 PM(UTC)
Jay

Rank: Member

Groups: Authorized User, Developers
Joined: 11/12/2018(UTC)
Posts: 25

Thanks: 1 times
Was thanked: 4 time(s) in 3 post(s)
A couple of updates...

I'm pretty sure the price difference is because the "old" plugin is getting rates from FedEx's live server. I forgot I had it configured that way on our dev site because I get errors if I try to have it use FedEx's test server. However, I can't test that theory by setting up the OAuth plugin to use FedEx's live server, because I am unable to get a Production Key from FedEx. There is a known issue on their developer site when you try to get your production key that just shows an error message. The API support guy told me he's got several customers with the same issue and is waiting for the development team to fix the issue, so he'll add me to the list and notify me when it is fixed. He has no ETA from them.
Katie S  
#7 Posted : Wednesday, March 27, 2024 1:58:17 PM(UTC)
Katie S

Rank: Advanced Member

Groups: System, Administrators, Developers, Registered, HelpDesk
Joined: 10/29/2018(UTC)
Posts: 423

Thanks: 4 times
Was thanked: 34 time(s) in 33 post(s)
Thanks for letting us know about the production key issue.

I've been confused about FedEx and their announcements as to what is exactly going to stop working, and when.

When we originally posted the announcement back in October, and developed the OAuth plugin, I could have sworn they were retiring FedEx Web Services on May 15th, 2024.

When I started looking for confirmation on the date last weekend, it seemed that something changed and now they are only retiring the FedEx Web Services Tracking API, Address Validation, and Postal code validation on May 15th.

Now, today, when I go to the FedEx Web Services page at https://www.fedex.com/en...eloper/web-services.html the announcement is different again:

Caution: FedEx Web Services Tracking, Address Validation, and Validate Postal Codes WSDLS will be disabled on August 31, 2024

Thanks for your support!

Katie
Secure eCommerce Software and Hosting
Jay  
#8 Posted : Wednesday, March 27, 2024 5:11:53 PM(UTC)
Jay

Rank: Member

Groups: Authorized User, Developers
Joined: 11/12/2018(UTC)
Posts: 25

Thanks: 1 times
Was thanked: 4 time(s) in 3 post(s)
They've probably pushed back / postponed the cutoff dates due to too many customers still using the old services.
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.