Introduction

The API endpoints exposed by the 10-4 Systems Freight Portal require authentication under the context of a user within an organization. The Authentication Services API provides a means of authenticating against the Freight Portal to receive a token that can be used for subsequent calls.

A customer uses the Authorization header to send the 10-4 server authentication credentials,
The authorization method is put before the encoded string, and returns an encrypted authentication token to be used in subsequent calls.

📘

Important Information

Please ensure to change the temporary password assigned to your API User Account before testing endpoints.

You will receive a 302 redirect error in the event your password has not yet been changed from the temporary password.

For dedicated environments an APIKey will need to be provisioned in the settings portion of the freight portal. That will be used in the header as an Authorization Bearer Token. Other forms of authentication will not be applicable.

Numerous components on a network, such as DNS servers, switches, load balancers, 3rd party dependencies, and others can generate errors anywhere in the life of a given request. The usual technique for dealing with these error responses in a networked environment is to implement retries in the client application. This technique increases the reliability of the application and reduces operational costs for the developer. Based on the volume of calls to our API an implementation of a retry policy as part of your integration may be needed. The 10-4 support team can help review your volume to see if retry logic should be added to your workflow.