Skip to main content

Environments & Base URLs

Connect Enterprise operates in two isolated environments. Each environment has its own base URL and requires dedicated credentials.

Environments​

EnvironmentBase URLPurpose
Developmenthttps://lfs-connect-enterprise-api-dev-h7ekhqc6g0g2greg.centralus-01.azurewebsites.netIntegration testing and development
Productionhttps://lfs-connect-enterprise-api-prod-d6hrg8hrg9bphpc7.centralus-01.azurewebsites.netLive enterprise operations

Credential Isolation Credentials issued for Development are not valid in Production, and vice versa. Contact the PRIMO team to obtain credentials for each environment.

API Version​

All endpoints are versioned under the /v1/ path prefix.

Example:

POST https://lfs-connect-enterprise-api-prod-d6hrg8hrg9bphpc7.centralus-01.azurewebsites.net/v1/otr/quote
POST https://lfs-connect-enterprise-api-dev-h7ekhqc6g0g2greg.centralus-01.azurewebsites.net/v1/drayage/quote
GET  https://lfs-connect-enterprise-api-prod-d6hrg8hrg9bphpc7.centralus-01.azurewebsites.net/v1/tools/otr/accessorials

Required Headers​

HeaderValueRequired
Content-Typeapplication/jsonYes (for POST requests)
AuthorizationBearer <token>Yes (for protected endpoints)

Anonymous Endpoints. Some utility endpoints under /v1/tools/ do not require authentication. These are marked with No authentication required in the Tools documentation.

API Conventions​

Request Format​

All request bodies must be sent as JSON (Content-Type: application/json).

Response Envelope​

Most API responses follow a standard envelope structure:

{
  "data": { ... },
  "errors": null
}
  • data — Contains the response payload on success
  • errors — Contains error details on failure; null on success

HTTP Status Codes​

CodeMeaning
200 OKRequest succeeded
400 Bad RequestInvalid request data or validation failure
401 UnauthorizedMissing or invalid bearer token
403 ForbiddenThe server understands the request but refuses to authorize it
500 Internal Server ErrorUnexpected server error

Next Steps​