Manhattan

Manhattan Active is a comprehensive supply chain and warehouse management solution that provides feature-rich SaaS applications for managing inventory, orders, shipments, and logistics operations. The Manhattan connector enables you to access Manhattan Active API endpoints to retrieve orders, shipments, and other supply chain data. This connector is particularly useful for applications that need to extract order data, track shipments, integrate supply chain data with other systems, or build logistics analytics and reporting solutions.

Power end-to-end data operations for your Manhattan API with Nexla. Our bi-directional Manhattan connector is purpose-built for Manhattan, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Manhattan or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Manhattan workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Manhattan credential, you'll need to obtain OAuth 2.0 credentials (Client ID and Client Secret) from your Manhattan Active account. Manhattan Active uses OAuth 2.0 client credentials flow (2-legged OAuth) for API authentication.

To obtain Manhattan Active API credentials:

1. Log in to your Manhattan Active account. The URL format depends on your deployment: https://<unique_id>.omni.manh.com, https://<unique_id>.sce.manh.com, or https://<unique_id>.scp.manh.com.

2. Navigate to the API or Developer settings section in your Manhattan Active account. This is typically found in the system administration or integration settings.

3. In the API settings, locate the OAuth client management section. Manhattan Active uses OAuth 2.0 clients for API access.

4. Create a new OAuth client or select an existing one. You'll need to provide a name and description for the client.

5. After creating the OAuth client, you'll receive a Client ID and Client Secret. Copy these credentials immediately, as the Client Secret may only be displayed once.

6. Note your Manhattan Active API URL and Authorization Server URL. These URLs follow the pattern:

   • API URL: https://<unique_id>.omni.manh.com, https://<unique_id>.sce.manh.com, or https://<unique_id>.scp.manh.com
   • Authorization Server URL: https://<unique_id>-auth.omni.manh.com, https://<unique_id>-auth.sce.manh.com, or https://<unique_id>-auth.scp.manh.com

Manhattan Active uses OAuth 2.0 client credentials flow (2-legged OAuth), which means you don't need user authorization. The Client ID and Client Secret are used to obtain an access token directly. The unique ID in your URLs is specific to your Manhattan Active deployment.

For detailed information about Manhattan Active API authentication and OAuth client management, refer to the Manhattan Active Developer Documentation.

Authenticate

Credentials required

OAuth2

Field	Required	Secret	Description
Client ID	Yes	No	Manhattan Client ID
Client Secret	Yes	Yes	Manhattan Client Secret
Authorization Server URL	Yes	No	Endpoint to obtain access token, such as https://<unique_id>-auth.omni.manh.com or https://<unique_id>-auth.sce.manh.com or https://<unique_id>-auth.scp.manh.com
Manhattan Active API URL	Yes	No	Application URL such as https://<unique_id>.omni.manh.com or https://<unique_id>.sce.manh.com or https://<unique_id>.scp.manh.com
Email used only for validation	No	No

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Manhattan

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. In the Client ID field, enter the Client ID that you obtained from your Manhattan Active OAuth client settings.

4. In the Client Secret field, enter the Client Secret that you obtained from your Manhattan Active OAuth client settings.

   The Client Secret is sensitive information and should be kept secure. If you've lost your Client Secret, you'll need to generate a new one in your Manhattan Active OAuth client settings.

5. In the Authorization Server URL field, enter the endpoint to obtain access token. This should be in the format https://<unique_id>-auth.omni.manh.com, https://<unique_id>-auth.sce.manh.com, or https://<unique_id>-auth.scp.manh.com, where <unique_id> is your Manhattan Active deployment identifier. The default value is https://<unique_id>-auth.scp.manh.com.

6. In the Manhattan Active API URL field, enter the application URL for your Manhattan Active deployment. This should be in the format https://<unique_id>.omni.manh.com, https://<unique_id>.sce.manh.com, or https://<unique_id>.scp.manh.com, where <unique_id> is your Manhattan Active deployment identifier. The default value is https://<unique_id>.scp.manh.com.

7. Optionally, in the Email used only for validation field, enter an email address that will be used for connection validation. The default value is anyuser@example.com. This email is only used to test the connection and does not need to be a real user email.

8. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

The Manhattan connector enables you to access Manhattan Active API endpoints to retrieve orders, shipments, and other supply chain data. This connector is particularly useful for applications that need to extract order data, track shipments, integrate supply chain data with other systems, or build logistics analytics and reporting solutions.

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Manhattan connector tile, then select the credential that will be used to connect to the Manhattan Active API, and click Next; or, create a new Manhattan credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Manhattan Active API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Fetch All Orders

This endpoint retrieves all orders from your Manhattan Active system. Use this endpoint when you need to extract order data, analyze order patterns, or integrate order information with other systems.

• This endpoint automatically retrieves all orders accessible to your Manhattan Active account. The endpoint uses pagination with nextToken to handle large datasets efficiently, automatically fetching additional pages as needed.

This endpoint uses GET requests with pagination through nextToken. The endpoint automatically fetches additional pages using the nextToken from the response pagination metadata. For more information about the Fetch All Orders endpoint, refer to the Manhattan Active API documentation.

Fetch All Shipments

This endpoint retrieves all shipments from your Manhattan Active system. Use this endpoint when you need to extract shipment data, track shipments, or integrate shipment information with other systems.

• This endpoint automatically retrieves all shipments accessible to your Manhattan Active account. The endpoint uses pagination with nextToken to handle large datasets efficiently, automatically fetching additional pages as needed.

This endpoint uses GET requests with pagination through nextToken. The endpoint automatically fetches additional pages using the nextToken from the response. For more information about the Fetch All Shipments endpoint, refer to the Manhattan Active API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Manhattan data sources can also be manually configured to ingest data from any valid Manhattan Active API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, path to data, and request headers.

Manhattan Active API endpoints typically follow the pattern {api_url}/api/v3/{resource}, where {api_url} is the Manhattan Active API URL configured in your credential. Most Manhattan Active endpoints use the GET method.

For nested API responses, common paths to data include $.orders[*] for arrays of orders or $.shipments[*] for arrays of shipments. You do not need to include an Authorization header, as the Bearer token is automatically included from your credential.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Manhattan data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.