> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runalloy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LineTen

> Integration details and setup guide for the LineTen connector in Alloy Automation.

## Pre-Built Tooling

| Category                            | Details                                        |
| ----------------------------------- | ---------------------------------------------- |
| **Authentication**                  | OAuth 2.0 (Client Credentials) or Bearer Token |
| **Two-Way Sync**                    | No                                             |
| **Events Supported**                | No                                             |
| **Realtime**                        | Polling                                        |
| **Supports Rate Limiting**          | Yes                                            |
| **Authentication Scopes Supported** | N/A (Client Credentials flow)                  |

***

## Objects Supported

Alloy Automation supports syncing the following objects from **LineTen**:

* Custom actions and resources (refer to LineTen API documentation for available endpoints)

***

## Set Up Guide

### Trial Access

| Question                                           | Answer                                                                                        |
| -------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| **Offers free trial?**                             | Contact LineTen for trial access information at [https://lineten.com/](https://lineten.com/). |
| **Requires paid sandbox**                          | Yes. LineTen typically requires a staging or sandbox environment. Contact LineTen support.    |
| **Requires partnership to obtain authentication?** | No, but you must be a LineTen customer or partner.                                            |

***

### Authentication (OAuth 2.0 Client Credentials)

LineTen uses OAuth 2.0 Client Credentials flow for machine-to-machine authentication.

#### How to obtain credentials

1. **Contact LineTen support** at [support@lineten.com](mailto:support@lineten.com) or through your account representative
2. **Request API access** for your organization
3. LineTen will provide you with:
   * **Client ID**: Your application identifier
   * **Client Secret**: Your application secret key
   * **Token URL**: The endpoint to obtain access tokens (typically `https://api-l10-idp-staging-neu.azurewebsites.net/connect/token` for staging)
   * **API Base URL**: Your instance's API endpoint (e.g., `https://api-nxd-staging-neu.azurewebsites.net/`)
4. **Configure credentials in Alloy Automation**:
   * Authentication type: OAuth 2.0 Client Credentials
   * Client ID: Provided by LineTen
   * Client Secret: Provided by LineTen
   * Token URL: Provided by LineTen
   * Note: Client credentials are sent using HTTP Basic Authentication (`client_secret_basic`)

#### API Documentation

* Contact LineTen support for comprehensive API documentation
* Base URLs may differ between staging and production environments
* Ensure you're using the correct environment URLs for your integration

***

## Use Cases

### 1) Last-mile delivery optimization

Integrate LineTen's delivery management data with your order fulfillment system to optimize routing, track delivery performance, and provide real-time updates to customers.

### 2) Shipping cost calculation

Use LineTen's rate calculation capabilities to dynamically compute shipping costs during checkout based on delivery address, package dimensions, and service levels.

### 3) Multi-carrier shipment tracking

Consolidate tracking information from multiple carriers managed by LineTen into your customer portal, providing a unified tracking experience regardless of the shipping provider.

### 4) Returns and reverse logistics

Automate returns processing by integrating LineTen's reverse logistics capabilities with your order management system, triggering return shipments and tracking return deliveries.

### 5) Delivery analytics and reporting

Pull LineTen shipment data into your business intelligence platform to analyze delivery performance, identify bottlenecks, and optimize your logistics operations.

***

## API Gotchas

* **Client Credentials flow**: LineTen uses OAuth 2.0 Client Credentials flow instead of the typical Authorization Code flow. This is a machine-to-machine authentication pattern that doesn't involve user interaction. Your application exchanges client credentials directly for an access token.
* **Environment URLs**: LineTen uses different URLs for staging and production environments. The OpenAPI spec shows staging URLs (e.g., `api-nxd-staging-neu.azurewebsites.net`). Ensure you update to production URLs when deploying to production.
* **Token management**: Access tokens from Client Credentials flow typically have shorter lifespans. Implement token caching and automatic refresh logic to minimize token requests and ensure uninterrupted API access.
* **Client authentication method**: LineTen uses `client_secret_basic` authentication, meaning client credentials are sent in the Authorization header (Basic Auth) when requesting tokens, not in the request body.
* **Limited public documentation**: LineTen's API documentation may not be publicly available. Work closely with LineTen support to understand available endpoints, request/response formats, and any instance-specific configurations.
* **Azure-hosted infrastructure**: LineTen's API is hosted on Azure (azurewebsites.net). Be aware of Azure service limits and regional considerations when planning your integration architecture.

> For questions or troubleshooting, contact **[support@runalloy.com](mailto:support@runalloy.com)**.