> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/shippingandmailing/fedex.md).

# Fedex

The Provider for FedEx uses five pieces of information in order to authenticate its actions with the FedEx service.

* Server: This controls the URL where the requests should be sent. Common testing options for this are: "<https://gatewaybeta.fedex.com:443/xml>", "<https://wsbeta.fedex.com:443/xml>", "<https://gatewaybeta.fedex.com:443/web-service>", and "<https://wsbeta.fedex.com:443/web-service>"
* DeveloperKey: This is the identifier part of the authentication key for the sender's identity. This value will be provided to you by FedEx after registration.
* Password: This is the secret part of the authentication key for the sender's identity. This value will be provided to you by FedEx after registration.
* AccountNumber: This valid 9-digit FedEx account number is used for logging into the FedEx server.
* MeterNumber: This value is used for submitting requests to FedEx. This value will be provided to you by FedEx after registration.
* PrintLabelLocation: This property is required to use the GenerateLabels or GenerateReturnLabels stored procedures. This should be set to the folder location where generated labels should be stored.

&#x20;

###


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/system-settings/data-sources/connection-settings/shippingandmailing/fedex.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.