(858) 586 7777 | About | Testimonials | Contact
vteams vteams vteams vteams
  • How does it work?
    • Startup Process
    • Your First Day
  • Technologies
    • Hire PHP Developer
    • Hire App Developer
    • Hire JavaScript Developer
    • Hire ROR Developer
    • Hire IOS Developer
    • Hire .NET Developer
    • Hire AI Developer
    • Hire Robotics Engineer
  • Sample Budgets
  • Meet The Team
  • Experiments
  • Captain’s Log
  • Blog
vteams vteams
  • How does it work?
    • Startup Process
    • Your First Day
  • Technologies
    • Hire PHP Developer
    • Hire App Developer
    • Hire JavaScript Developer
    • Hire ROR Developer
    • Hire IOS Developer
    • Hire .NET Developer
    • Hire AI Developer
    • Hire Robotics Engineer
  • Sample Budgets
  • Meet The Team
  • Experiments
  • Captain’s Log
  • Blog
Blog
  1. vteams
  2. Blog
  3. Failed To Get Freight Rates For Shipping Through FedEx Freight Rates API – Solution
Jul 31

Failed To Get Freight Rates For Shipping Through FedEx Freight Rates API – Solution

  • July 31, 2015

FedEx Freight Rates API for Shipping is one of the most complex freight rates APIs but a reliable and affordable solution as compared to others available on the market. In comparison to “Simple Rates”, Freight Rates API has less support available on Google and other support forums which makes it a bit hard to get proper help/support when one is stuck with any problem.

Our resource of vteam #401 was facing problem in getting freight rates. He created several support tickets on FedEx forum, but failed to get any proper response. He observed errors on each request he was creating. Initially, he thought it happened because Freight service is not validated from FedEx and that is why he was facing issues repeatedly. He used all the information received in every possible way in his code for calling the API but the transaction was returning the following error:

Severity: ERROR
Source: cust
Code: 959
Message: The account number entered for FEDEX_FREIGHT could not be validated. LocalizedMessage: The account number entered for FEDEX_FREIGHT could not be validated.
Id: ACCOUNT_NUMBER_TYPE
Value: FEDEX_FREIGHT

In order to fix the problem, developer did some R&D. He read FedEx documentation and performed a step by step analysis on the code as well. When he signed up for “FedEx API”, they sent him the key and meter number for using these credentials with the API. Live account details were also provided to him by the client. He tried everything but no didn’t succeed.

Solution:

Two common mistakes were identified in the following code after R&D:

1
2
3
if($var == 'key') Return 'Ktz78Vwm8O7xrqoL'; // My FedEx key
if($var == 'password') Return 'yjlxWFFXzLmTKCdEd3rG4clzQ'; // FedEx password received in EMAIL
if($var == 'shipaccount') Return '510087607'; // Account Number [Either Test or Live]

Normally ‘shipaccount’ is confused with FedEx Freight LTL Shipper Account Number due to the name similarity between them, but in actual ‘shipaccount’ is the test or live account number.

1
if($var == 'freightaccount') Return '510087020'; // FedEx Freight LTL Shipper Account Number

Generally it is confused with the test or live account number instead of Shipper Account Number.

1
2
3
4
5
if($var == 'locationid') Return 'PLBA';
if($var == 'printlabels') Return false;
if($var == 'printdocuments') Return true;
if($var == 'packagecount') Return '4';
if($var == 'meter') Return '118616750'; // Meter number

Conclusion:

Following two points should be noted:

1.‘shipaccount’ is not the Shipper Account Number but it is either Test or Live FedEx freight account Number
2.‘freightaccount’ is not the Test or Live FedEx freight account Number but it is the FedEx Freight LTL Shipper Account Number

The developer was doing the mistake due to this confusion in the names and keywords. This is quite a common issue that every developer may encounter but no specific help is available online for this particular scenario. Our resource learned the solution from hit and trial. This solution will be beneficial for every developer out there committing the same common mistake repeatedly.

  • Facebook
  • Twitter
  • Tumblr
  • Pinterest
  • Google+
  • LinkedIn
  • E-Mail

Comments are closed.

SEARCH BLOG

Categories

  • Blog (490)
  • Captain's Log (1)
  • Closure Reports (45)
  • Experiments (7)
  • How-To (56)
  • Implementation Notes (148)
  • Learn More (156)
  • LMS (8)
  • Look Inside (10)
  • Operations Log (12)
  • Programmer Notes (20)
  • R&D (14)
  • Rescue Log (4)
  • Testimonials (25)
  • Uncategorized (4)

RECENT STORIES

  • GitHub Actions- Automate your software workflows with excellence
  • Yii Framework – Accomplish Repetitive & Iterative Projects with Ease
  • A Recipe for CRM Software Development
  • Are Agile and DevOps the same?
  • The Data Scientist’s Toolset

ARCHIVES

In Short

With the vteams model, you bypass the middleman and hire your own offshore engineers - they work exclusively for you. You pay a reasonable monthly wage and get the job done without hassles, re-negotiations, feature counts or budget overruns.

Goals for 2020

  • Open development center in Australia
  • Complete and Launch the Robot
  • Structural changes to better address Clients' needs

Contact Us

Address: NEXTWERK INC.
6790 Embarcadero Ln, Ste 100,
Carlsbad, CA 92011, USA

Tel: (858) 586 7777
Email: fahad@nextwerk.com
Web: www.vteams.com

© 2020 vteams. All Rights Reserved.

Content Protection by DMCA.com