Fedex web services sample code java

• Review the documentation to learn more about request and response elements, examples in your programming language of choice, error codes, and more.

• Check the Announcements page for planned service updates and learn what’s new.

Sign up or log in

Log in with your fedex.com user ID and password to begin integrating with FedEx APIs and webhooks.

If you do not have a user ID yet, you can sign up for free.

Create or join an organization.

Either create an organization, if one does not yet exist for your company, or join your company’s existing organization.

To create an organization:

If you create an organization, you will automatically be listed as the Admin of that organization.

• An Admin can invite users to join their organization, assign them to roles(e.g. contributor or viewer) and projects, and can manage shipping accounts.
• To learn more about these roles, explore our Organization Administration Guidelines.

To create your own organization, Click on Create Organization in the left-hand navigation.

Provide organization information

• Provide your company name, website URL and create an organization name. Give your organization a name that other users will recognize. This name can be used to organize your company into more specific groups (e.g. department, division, region, location) or can be the same as your company name.

To join an organization:

You can join an already existing organization by completing the following steps:

• If your company has already created an organization, ask the admin of the organization to invite you to join. You will have 24 hours to accept their invite. If you miss this window of time, you can always ask them to resend it.

• To accept the invite, you will need to either log in with your existing user ID and password or, if your existing user ID is already associated with an organization, you will need to create a new one.

Add a shipping account.

• Enter your account number, an account nickname, and a billing address associated with the account. We will then validate the billing address to be sure it matches the account details in order to prevent fraudulent activities.
• To view shipping accounts associated with your user ID, go to the Manage Organization page and the Shipping accounts tab. To create new shipping accounts, please contact your FedEx sales representative.
  

• You must then accept the End User License Agreement (EULA)or send it to another individual within the end user company who can accept the agreement. You can view the status of the EULA on the Manage organization page, under the shipping account tab.

Step 5: Add a billing account

An admin can add a billing account to their organization and assign it to projects. To begin, navigate to the Billing tab on the Manage Organization page. From there, you can open a new billing account on fedex.com and add the billing account to your organization on the FedEx developer Portal by completing the following steps:

1. Open a new billing account

• First, open a new billing account at fedex.com. This step will redirect you from the FedEx Developer Portal to fedex.com.

2. Add billing account to your organization

• Next, return to the Manage Organization page to add the account to your organization. You’ll need the account number and the address used to open the account for this step.

3. Assign billing account to a project

• Confirm the default billing account or add a new billing account to a project.

Step 6: Add users to your organization

An admin can invite users to their organization and assign them to roles and projects. To begin, click the Add Users button from the Users tab of the Manage Organization page. From there, you can add users by completing the following steps (those marked with an * are optional):

1. Enter users email addresses

• Enter the email addresses of any users that you want to invite to join your organization. You can enter multiple email addresses by hitting a space, comma, semicolon, or enter key on your keyboard between addresses

2. Select user roles

• Choose a different user role if the default option of viewer doesn’t match that user’s needs.*
  

3. Assign users to a project

• If you have already created projects, you can assign users to a project.*

An admin will always have access to all projects, but a contributor or viewer must be assigned to a project (unless a contributor creates a project, in which case they will be automatically assigned to that project).

Whether a user has accepted an invite yet or not, you can quickly update their projects or roles straight from the the Manage organization page, under the Users tab.

• Click on the caret beside the role or project, and a dropdown will appear with options.
• Select an option, then select the Apply button to save your selection.

1. Create a project to get credentials
2. Integrate APIs & test your implementation
3. Move your project to production
4. Complete your certification

Create a project to get credentials.

An admin or contributor for your organization can create an API project by clicking on the Create a API Project button.

Before getting started, you will first need to let us know why you need to access FedEx APIs. A modal will appear and present you with dropdown options. You should select the option that best identifies your business needs for integrating with FedEx APIs.

If you identify as a shipper, you can begin to create your project. This is a three step process:

Select the API(s) you want to include in your project. Based on the API(s) you select, you may need to make some additional selections.

If you select Track API, you will also need to:

• Select an account number to associate with your production key.
• Review the track API quotas, rate limits, and API certification details.
• Choose whether or not you want to opt-in to emails that will notify you if you exceed your transaction quota.

Enter some project specifics, including name and shipping location.

• Give your project an identifiable name that is unique to your organization
• Select any countries you plan to ship within so that we can assign you a test shipping account. To test shipping packages domestically within a European country, you must have a separate test account for each country. You can always add/remove countries later.
• To get notified about the latest API updates and any outage related information, you can set your notification preferences.

Review your project details, then accept the terms and conditions.

• Read and accept the FedEx Developer Portal License Agreement and acknowledge that you do not intend to sell or distribute your application.
• Once you click the "Create" button, you will see a confirmation screen. You can then view your test credentials within your new project.

Integrate APIs & test your implementation

On the Project overview page, retrieve your test credentials — API key, secret key, and shipping
account(s) — from the Test key tab. Next, you can.

• Request an OAuth access token, which must be used with each API transaction. The token is valid only for an hour, so you will need to programmatically code your application to refresh the token before the session expires. Refer to the API Authorization docs for more details
• Click on any Docs for your APIs to read the business context for each API so you can best understand how to use it. You can also review example requests for the endpoint that matches your desired integration.
• Implement your calls to these endpoints as described in the example requests, configuring them with your test credentials.
• Verify that the API call responses you receive match those shown in the documentation.
• Test your implementation within the FedEx test environment using your test credentials and the FedEx test URLs.

Move your project to production

Click the Production key tab. You can now start to move your project to production by
completing the following steps.

Within the Configure project step:

• You can rename your key as needed.
• Review the account number that you selected in step 1 of the project creation flow. This is used to move your project to production. Once your project is live in production, you can add more accounts as needed.

Within the Get project keys step:

• Your production API key and production secret key will be displayed. Make sure to copy them to a secure place.
• To keep your production secret key secure, we only display it once. If you lose it, you can generate a new one.
• Click Next.

You will now be brought back to the Project overview page. Here you can add more accounts associated with your project.

On the Project overview page:

• Click on the 3 vertical dots (or kebab menu) to add more accounts associated with your project.
• Next, click Edit.

This will bring you to the API key page where you can add any additional accounts you want to associate with your production key for this project.

Complete your certification

1. Some APIs require shipping label certification for use in our production environment. Complete the certification process for any APIs in your project with this requirement.

1. After all APIs have been certified and enabled, update your API requests by replacing the test URIs, keys and shipping accounts with the production URIs, keys and shipping account.
2. Retest your implementation in the production environment using sample data.
3. Enjoy the benefits of your new integration!

Prerequisites to create a webhook project

1. Learn about pricing
2. Complete billing and shipping account set up
3. Create a valid (call back) URL in your destination application/platform
4. Generate security token
5. Test webhook URL
6. Validate destination (call back) URL

Create a webhook project

Prerequisites to create a
webhook project

Learn about pricing

Subscribers are charged a monthly fee based on the count of track numbers. please refer to Shipment Visibility Webhook overview page to learn more about pricing.

Complete billing and shipping account set up

See the Create Organization Getting Started Guide for your organization admin to complete the billing and shipping account set up. See the Create Organization getting started guide for step-by-step instructions.

Create a valid (call back) URL in your destination application/platform

Create a valid (call back) URL in your destination application/platform to receive authentication codes/messages and Shipping Visibility Webhook payload notifications from FedEx.

URL requirements:

Generate security token

This security token can be used as a secret key to authenticate and validate information transmitted between your organization and FedEx.

Security token requirements:

Test webhook URL

Testing your URL is an optional step that you may find helpful.

Testing can help you get a better idea about whether the URL you created in step 1 is valid. It allows FedEx to identify your URL and build a connection with your URL to send data. Testing can also provide you with sample test data that can help you check and confirm whether you are able to process tracking data provided in your application. Testing does not, however, authenticate your URL.

Visit our webhook documentation to learn how to test your webhook URL.

Create a webhook project

Create a webhook project to receive configured payload notifications

On the My Projects page, go to the Webhooks tab.

An admin for your organization, you can create a webhook project by clicking on the Create a Webhook project button.

You can begin to create your project by completing the following steps:

1. Identify your business needs

• Select the option that best identifies why your business wants to integrate with FedEx webhooks.

1. Confirm billing account and select features

• Confirm your billing account, or add a different billing account from your organization.
• Select the features that you want to be configured with your project.

1. Configure project details

• Give your project an identifiable name.
• Provide pre-generated destination (call back) URL and security token details, which are created during pre-setup authentication.

Webhook project name

This is a non-empty, unique webhook project name
and should not be repeated in any other webhook
project.
• The webhook project name is auto-populated
with a suggested name, which can be edited as
needed.

Destination (call back) URL

This is the URL where you will receive the tracking
event data/payload.
• You should provide a working and valid
destination (call back) URL.
• The destination (call back) URL provided must be
in the standardized syntactical format (secure
https URL, don’t include fedex.com or its sub
domains in the URL).
• You can repeat the destination (call back) URL in
multiple webhooks.

This is used as shared secret to authenticate and
validate the Shipment Visibility Webhook response.
• Token value must be a minimum length of
25 characters and maximum of 100 characters.
• At least 1 uppercase, 1 lowercase, and 1 numeric
character are required.
• You can repeat this security token in
multiple webhooks.
• The security token will be used to create a hash-
based
message authentication Code (HMAC) signature
for response validation.

Payload language (country)

Select the preferred language for your tracking data
translations from the drop-down list.

Select the type of response in which the tracking
data needs to be received.
• Detailed tracking response: response type
consists of secured tracking data with entire
history of events
• Event-specific tracking response: response
type consists of secured tracking data with only
the most recent event information

Provide an email address to receive email
notifications when there are changes made to your
webhook project (e.g., created, edited, canceled).

Email language (country)

Select the preferred language in which you would
like to receive webhook email notifications from
FedEx.

These are the supported languages for email
notifications:
• English (United States)
• Spanish (United States)

• Choose from a list of eligible (U.S.-based) account numbers that you want to be associated with your project.

• Review your configured project details.
• Read and accept the Developer Portal License Agreement, and acknowledge that you do not
intend to distribute your application.
• Once you click the Create button:

1. If your create request was successfully validated and processed, you will be brought to a confirmation screen.
• If validation is unsuccessful or fails, there will be an error message.
2. Your Shipment Visibility Webhook project will then have a system generated webhook ID and be shown to have an “Active” status.

Still have questions? We’ve got answers

A webhook is an HTTPS-based callback function that allows lightweight, event-driven communication between 2 applications. In this case, your application and FedEx. Using webhooks allows you to receive near real-time updates about the events you want to know about. Learn more about the benefits of FedEx webhooks.

Read more

FedEx Ground, FedEx Ground Economy, FedEx Express and FedEx Freight (9-digit account number only) shipment tracking updates are supported through FedEx Shipment Visibility Webhook.

Read more

What events are available for subscription via FedEx Shipment Visibility Webhook? Created with Sketch.

The Shipment Visibility Webhook enables real-time push of in-transit shipment tracking events, ranging from ‘Label Creation’ to ‘Delivered’, including Picture Proof of Delivery.

Read more

1. FedEx creates Compatible provider organization.
2. Accept invite.
3. Invite users to your organization.
4. Select APIs you need for your solution.
5. FedEx creates project(s).
6. Integrate APIs into your application and certify to the Compatible Program.
7. FedEx moves project(s) into production.
8. Generate Production Secret Key.

FedEx creates Compatible provider organization

• FedEx will create an organization and then invite one team-member to join the organization. This user will be designated as the admin for your organization.
• Upon completion of certification and integration, you will be able to distribute the solution to your customers with ease .

• In order to get access to the API integration artifacts and documentation, please accept the invite. To accept the invite, you will need to either log in with your FedEx User ID and password or create a new one if you don’t already have credentials.

Invite users to your organization.

• As Admin, you are able to invite any team members that need access to the project or organization. For details on the different roles, view the Organization Administration Guide.

• If your organization has already been created, ask the Admin of the organization or FedEx to invite you to join. You will have 24 hours to accept their invite, but if you miss this window of time, you can ask them to resend it.

Select APIs you need for your solution.

• Visit the API Catalog to determine the right APIs for your solution. Your FedEx Customer Technology Consultant (CTC) and Compatible Channel manager can help you select the right APIs for your solution as per your business needs.

• Select an API to discover the overview, changelogs and key features.

• View the API's documentation to uncover request and response elements, examples in your language of choice, error objects and more.

• Go back to Salesforce to fill out the Product Information Worksheet (PIW) and list out the APIs you would like to have added to your solution.

FedEx creates project(s).

Once the PIW has been approved, FedEx will create your project(s). Each version of each of your solutions will have a separate project within the FedEx Developer Portal. If a user is not an Admin of the organization, they would need to be invited to view each project.

This is also when the FedEx Compatible team along with the FedEx CTC and certification teams will organize a technical demonstration for the APIs with your team. The FedEx team will discuss the new features and functionality available with the version of APIs you are adopting. The team will be able to address technical questions regarding APIs, API testing and all processes that need to be completed to start the process of ‘certification*’ for APIs.

* Certification – The process defined by the FedEx Compatible Program to satisfy Program Compliance requirements. Compatible Program Certification is required to ensure that all Compatible Providers implement, market and distribute FedEx technology to shippers (customers) as defined by FedEx technology & service standards.

Integrate APIs into your application and certify to the Compatible Program.

1. You will now have access to your Test API Key and Test Secret Key to start running transactions. Retrieve them from the Test Key tab of the Project Overview page.

1. In order to create customer keys, you will need to use the Credential Registration API, which is a private API only found in the API section of each of your projects.
2. Once you’ve created a few customer keys, go ahead and request an OAuth access token to be used with every API transaction. The session for the token is valid only for an hour, so you will need to programmatically code your application to refresh the token before the session expires. Refer to the API Authorization docs for more details. When viewing sample code, make sure “Reseller” is chosen from samples dropdown.

1. Select docs for the APIs on your Test Keys page and read the business context to best understand how to use the selected API. Review example requests for the endpoint that match your desired integration.
2. Implement your calls to these endpoints as described in the example requests, configuring them to use your test credentials.
3. Verify that the received API call responses are matching those shown in the documentation.
4. Completely test your implementation within the FedEx test environment using test credentials and the FedEx test URIs.
5. After fully testing your solutions, certify each solution in Salesforce. FedEx will fully review everything submitted and update you once your certification is approved.