RocketShipIt

RocketShipIt

  • Docs
  • API Examples

›Guides

Guides

  • Getting Started
  • API Explorer
  • Errors
  • Self-Hosting
  • Cloud API
  • Rating
  • Tracking
  • Shipping Labels
  • Address Validation
  • Batch Requests
  • ETD / Paperless Customs
  • Thermal Printing
  • Add a logo to the shipping label
  • Add Reference Values to Labels
  • Return Labels
  • Scale Integrations
  • Laravel
  • FedEx Ground Collect
  • UPS Mail Innovations
  • Saturday Delivery
  • Find Locations
  • FedEx Test Environment
  • Switching UPS / FedEx REST
  • Authenticating Multiple UPS Accounts with UPS REST API
  • Authenticating with REST oauth APIs
  • Customizing RocketShipIt Requests

References

  • Requirements
  • Supported Shipping Carriers
  • Carrier Authentication
  • API Examples
  • Request/Response Format
  • Parameters
  • Carrier Errors
  • Command Line Options
  • Label Transformations
  • Supported Address Validation Countries
  • DHL Addons (Special Service Codes)
  • Rate Details
  • GetSubscription
  • Accessorial / Surcharge Codes
  • Shipping Carrier APIs
  • FedEx SmartPost
  • Carrier Parameters
  • UPS API Parameters
  • FedEx API Parameters
  • API REST Migration Deadlines

Troubleshooting

  • What if I run into trouble?
  • FAQs
  • Inaccurate Rates?

Switching to New UPS and FedEx REST API

If you have been using RocketShipIt previous to 2024 you likely are using the RocketShipIt carriers: UPS and FedEx. To use the newer REST based APIs you just need to authenticate differently and switch the RocketShipIt carrier value to UPS-REST and FedEx-REST.

UPS and FedEx had a (now legacy) SOAP XML based API that RocketShipIt integrated with in 2008. In 2023 They added a JSON REST API. It appears that they used the same structure as their previous XML based APIs and their new JSON APIs are basically a fecade on top of their old API. The good news is most of the parameter names and structures haven't changed.

In order to use their new REST APIs, you will need to:

  1. In the carrier developer portals: Create an "App" (This makes a test client_id/client_secret). That app has no permissions by default.
  2. Request permissions for all the services you want to use (I suggest clicking all of them). This gives you permission to use rates, tracking, etc.
  3. Authenticate with test=true see: https://docs.rocketshipit.com/2-0/examples/#fedex-rest-authenticate
  4. Make a request with key and test=true: https://docs.rocketshipit.com/2-0/examples/#fedex-rest-rates
  5. Move to production
  6. Use new credentials and set test=false or omit the test param

NOTE For FedEx: Move to production right away. Their test env is not great. See: https://docs.rocketshipit.com/rs/docs/fedex-test-environment.html You will know when you get REQUEST.MISMATCH errors.

UPS

03-05-2024 - UPS does not have signature or proof of delivery implemented yet in their new REST API.

← FedEx Test EnvironmentAuthenticating Multiple UPS Accounts with UPS REST API →
  • UPS
RocketShipIt
Docs
Getting StartedAPI Reference
RocketShipIt
SupportMy Account
Copyright © 2025 RocketShipIt LLC