.png)
project44 Integration Guide
Connect project44 transportation visibility data with enterprise systems through REST APIs, OAuth 2.0, scheduled workflows, and selected event notifications.
project44 integration options at a glance
project44 integrations are centered on authenticated REST APIs for registering tracking requests, retrieving shipment and movement details, querying tracking events, and working with transportation data exposed by the subscribed API product. Selected project44 products and tenants also support webhook-style event notifications for shipment or movement updates, although event coverage and delivery behavior must be verified. Martini can consume these APIs, receive supported callbacks, transform payloads, and orchestrate downstream updates. Scheduled workflows support polling, pagination, checkpointing, reconciliation, and backfill where event coverage is incomplete. OAuth 2.0 credentials, regional endpoints, scopes, and tenant-specific settings should be stored in protected environment configuration.
| Integration point | Supported by project44? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | project44 REST APIs can register tracking requests, retrieve shipment and movement details, query tracking events, and work with exposed transportation resources such as carriers, facilities, stops, equipment, appointments, and tenders. | Martini can consume authenticated project44 REST endpoints from workflows, transform responses, apply business rules, and expose normalized APIs to downstream systems. |
| Webhooks and outbound callbacks | Limited | Selected project44 products and event types support shipment or movement notifications. Coverage, payload completeness, delivery behavior, and authentication vary by API product and tenant. | Martini can receive supported callbacks, validate authentication or signatures where applicable, deduplicate events, retrieve additional details, and route normalized events to other systems. |
| Authentication | Yes | project44 API access uses OAuth 2.0 bearer tokens with client credentials. Token hosts, scopes, audiences, and regional authorization settings depend on the tenant and subscribed API product. | Martini can store client credentials and token configuration as protected environment secrets and use OAuth 2.0 configuration for authenticated API workflows. |
| Scheduled synchronization | Yes | Scheduled polling can retrieve changed shipments, tracking events, and milestones for reconciliation, backfill, or APIs without the required event coverage. | Martini schedulers can run incremental workflows with pagination, overlap windows, checkpoints, idempotency controls, and bounded retry handling. |
| Bulk, asynchronous, and batch APIs | Not confirmed | Batch or asynchronous behavior may exist for selected APIs or operational processes, but broad platform-wide support was not confirmed. | Martini can orchestrate endpoint-specific asynchronous behavior when documented, but implementations should not assume bulk or job support across project44 APIs. |
| File and attachment APIs | Not confirmed | No general-purpose project44 file import, export, or attachment API was confirmed. Transportation documents may be available in selected products or workflows. | Martini can process files through supported endpoints when project44 documentation confirms them, but the integration should otherwise use REST APIs and event mechanisms. |
| Database and analytics access | No | No supported direct customer database access was confirmed for project44 integrations. | Martini should consume project44 APIs and supported event mechanisms rather than attempting direct database connectivity. |
| SDKs | Not confirmed | project44 provides API-oriented developer resources, but a universally required or supported official SDK set was not confirmed. | Martini can integrate directly through authenticated HTTPS REST requests without requiring an SDK. |
How project44 exposes data and business events
project44 REST APIs
project44’s developer platform is primarily REST-based. Depending on the subscribed product, the APIs can register tracking requests, retrieve shipment and movement details, query milestones, and work with transportation resources such as stops, carriers, facilities, equipment, tenders, and appointments.
Martini implementation pattern
Martini implementation pattern: a workflow obtains or reuses an OAuth 2.0 bearer token, calls the applicable project44 endpoint, handles pagination and transient failures, maps the response into a canonical transportation model, and writes the result to downstream applications or exposes it through a Martini API.
Implementation sequence
project44 event notifications
Selected project44 products and API configurations support webhook-style notifications for shipment or movement changes. Notifications are not necessarily available for every object or event, and the payload may contain a notification requiring a follow-up API request.
Martini implementation pattern
Martini implementation pattern: a webhook-triggered workflow accepts the supported callback, validates its authentication or signature model, checks replay and duplicate controls, retrieves the current shipment when necessary, and routes the normalized event to operational or customer-facing systems.
Implementation sequence
Scheduled project44 synchronization
Scheduled polling is appropriate for reconciliation, backfill, missed notifications, and API products without the required event coverage. The exact filtering, pagination, and update semantics depend on the project44 API product.
Martini implementation pattern
Martini implementation pattern: a scheduler reads a stored watermark or cursor, queries project44 with a small overlap window, processes pages incrementally, deduplicates shipments and events, updates target applications, and commits the checkpoint only after successful processing.
Implementation sequence
Common project44 integration patterns
Pattern 1: Sync project44 shipments to an ERP
When to use this pattern
Use this pattern when SAP S/4HANA, NetSuite, or Microsoft Dynamics 365 needs transportation status, milestone, carrier, or estimated-arrival information associated with deliveries and fulfillment records.
Integration direction
Example Mapping
| project44 Field | Canonical Field | Target Field |
|---|---|---|
| shipment.id | transportationShipmentId | Delivery transportation reference |
| trackingEvents[].status | shipmentMilestone | Delivery status |
| trackingEvents[].eventTime | milestoneTimestamp | Status timestamp |
| stops[].facility | stopLocation | Delivery location |
Martini implementation pattern
A scheduled Martini workflow reads a checkpoint, retrieves changed project44 shipments and events, matches them to ERP delivery references, normalizes timestamps and status precedence, and updates the ERP. The workflow uses overlap windows, idempotency keys, bounded retries, and a failed-record queue or reconciliation path.
Martini capabilities used
- workflows
- scheduled triggers
- API consumption
- data mapping
- business rules
- error handling
Pattern 2: Route project44 events to operational cases
When to use this pattern
Use this pattern when shipment delays, disruptions, or delivery exceptions should create or update operational work in ServiceNow or customer-facing workflows in Salesforce.
Integration direction
Example Mapping
| project44 Field | Canonical Field | Target Field |
|---|---|---|
| shipment.id | shipmentReference | Configuration or case reference |
| trackingEvents[].status | exceptionStatus | Incident status |
| trackingEvents[].eventTime | occurredAt | Event time |
| trackingEvents[].description | exceptionDescription | Incident description |
Martini implementation pattern
Martini receives a supported project44 callback, validates the request, checks the event key, retrieves additional shipment context when needed, and applies severity and duplicate rules before creating or updating the target case. Events that arrive out of order are evaluated against timestamps or status precedence.
Martini capabilities used
- webhook-triggered workflows
- API consumption
- data mapping
- business rules
- idempotency
- error handling
Pattern 3: Submit transportation context to project44
When to use this pattern
Use this pattern when a TMS or internal logistics application needs a controlled integration for sending shipment, carrier, stop, facility, or tracking context to project44.
Integration direction
Example Mapping
| project44 Field | Canonical Field | Target Field |
|---|---|---|
| shipmentReference | customerShipmentReference | project44 shipment reference |
| carrierCode | carrierIdentifier | project44 carrier reference |
| stops[].locationCode | facilityIdentifier | project44 facility reference |
| equipment.number | equipmentIdentifier | project44 equipment reference |
Martini implementation pattern
A Martini REST API accepts the source application request, validates required identifiers and business rules, transforms the payload into the applicable project44 request, and calls the project44 REST API with OAuth 2.0. The workflow records correlation identifiers and classifies validation, authorization, rate-limit, and transient failures separately.
Martini capabilities used
- API exposure
- API consumption
- request validation
- data transformation
- business rules
- error handling
Pattern 4: Reconcile project44 and transportation data
When to use this pattern
Use this pattern when an enterprise needs to detect missed notifications, stale movements, status mismatches, late-arriving events, or unprocessed deliveries across project44 and an internal transportation application.
Integration direction
Example Mapping
| project44 Field | Canonical Field | Target Field |
|---|---|---|
| shipment.id | shipmentKey | Transportation shipment ID |
| trackingEvents[].status | vendorStatus | Execution status |
| trackingEvents[].eventTime | vendorEventTime | Milestone timestamp |
| stops[].appointment | appointmentContext | Stop appointment |
Martini implementation pattern
A scheduled Martini workflow retrieves project44 changes and compares them with the target system’s current state. It applies status precedence, identifier crosswalks, and time-zone normalization, then updates mismatches or raises exceptions. The checkpoint advances only after the page and its downstream updates complete successfully.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- comparison rules
- checkpointing
- monitoring and error handling
Applications commonly integrated with project44
project44 can be integrated with transportation, enterprise resource, customer-service, and operational applications to distribute shipment visibility, milestones, exceptions, and transportation context. Exact API coverage depends on the project44 product and the connected application, so each implementation should verify supported resources and identifiers.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Synchronize deliveries, carrier milestones, shipment status, and estimated arrival information with enterprise logistics and order processes. | project44 → Martini → SAP S/4HANA | A scheduled or event-triggered Martini workflow retrieves project44 shipment and tracking data, maps references and milestones to SAP delivery models, applies status precedence rules, and updates SAP through its supported API. Failed records are retained for retry and reconciliation. |
| Oracle Transportation Management | Exchange transportation plans, shipment references, carrier information, and execution milestones between transportation operations and visibility services. | Oracle Transportation Management → Martini → project44 | Martini exposes a controlled API for transportation messages, validates identifiers and required fields, transforms the payload into the applicable project44 REST request, and records response identifiers for later status synchronization. |
| Salesforce | Make shipment status, delivery milestones, and transportation exceptions available to sales and customer-service users. | project44 → Martini → Salesforce | Martini receives supported project44 notifications or polls for changes, normalizes shipment and event data, matches it to Salesforce business references, and updates the relevant account, order, case, or custom object through Salesforce APIs. |
| ServiceNow | Create or update logistics incidents, exception cases, and operational tasks when shipments are delayed or disrupted. | project44 → Martini → ServiceNow | A Martini webhook workflow or scheduled reconciliation identifies delayed or disrupted shipments, applies severity and duplicate rules, and creates or updates ServiceNow records while retaining the project44 shipment and event identifiers. |
| NetSuite | Synchronize fulfillment and shipment status with transportation visibility data. | project44 → Martini → NetSuite | Martini retrieves project44 milestones, maps them to NetSuite fulfillment references, applies timestamp and status transformations, and updates NetSuite through its supported API. A checkpoint and idempotency key prevent duplicate updates. |
| Microsoft Dynamics 365 | Align orders, deliveries, transportation execution, and estimated arrival information across logistics and commercial processes. | Microsoft Dynamics 365 → Martini → project44 | Martini accepts shipment context from Dynamics 365 or retrieves it from project44, resolves cross-system identifiers, calls the appropriate project44 REST resource, and synchronizes resulting milestones back through a reusable workflow. |
| Manhattan Active Transportation Management | Exchange transportation execution and visibility data between transportation planning or execution and project44. | Manhattan Active Transportation Management → Martini → project44 | A Martini API receives transportation updates, maps carrier, stop, facility, and shipment references to project44 terminology, invokes the applicable REST endpoints, and routes status changes back to Manhattan through its supported interfaces. |
| Blue Yonder | Synchronize transportation planning, shipment execution, and visibility milestones. | Blue Yonder → Martini → project44 | Martini orchestrates bidirectional API calls, normalizes shipment and event identifiers, applies business rules for milestone precedence, and uses bounded retries and reconciliation for transient or downstream failures. |
How to build a project44 integration in Martini
Objective
Configure the project44 API product, regional endpoints, OAuth 2.0 settings, and tenant permissions without embedding secrets in workflow definitions.
Instructions in Martini
- Confirm the applicable project44 authorization host, scopes, audience, and API base URL
- Store client ID, client secret, token settings, and regional configuration in protected Martini environment configuration
- Configure OAuth 2.0 bearer-token authentication and avoid logging credentials
Objective
Select event-driven processing, scheduled polling, or a combined model based on the project44 product’s supported notification coverage.
Instructions in Martini
- Verify which project44 events and resources support callbacks
- Use a webhook-triggered workflow for supported near-real-time notifications
- Use a scheduler for reconciliation, backfill, and APIs without adequate event coverage
Objective
Obtain shipment, movement, stop, carrier, facility, equipment, appointment, tender, or tracking-event data through the applicable project44 interface.
Instructions in Martini
- Call the documented project44 REST resource or receive the supported callback
- Handle pagination, continuation tokens, and incomplete notification payloads
- Use overlap windows and stable identifiers for incremental retrieval
Objective
Coordinate project44 calls, enrichment, target updates, and state management as a maintainable Martini workflow.
Instructions in Martini
- Separate token acquisition, vendor retrieval, transformation, and target updates where practical
- Use correlation identifiers throughout the workflow
- Persist checkpoints only after successful downstream processing
Objective
Convert project44 transportation terminology into canonical shipment, order, delivery, case, or transportation models used by target systems.
Instructions in Martini
- Map project44 identifiers to explicit target-system references
- Normalize timestamps, time zones, status values, and milestone precedence
- Preserve vendor identifiers for traceability and reconciliation
Objective
Control duplicate processing, event ordering, exception severity, and target update behavior before writing data.
Instructions in Martini
- Deduplicate using event IDs or stable shipment and event keys
- Reject or quarantine incomplete payloads according to validation rules
- Treat late or out-of-order events according to timestamps or status precedence
Common project44 data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Shipments | Represent transportation movements being tracked and provide references for status, milestones, and delivery visibility. | SAP S/4HANA, Oracle Transportation Management, NetSuite, Microsoft Dynamics 365 | Martini retrieves or receives shipment information, resolves business identifiers, maps the object to orders or deliveries, and applies idempotent update rules. |
| Tracking events | Represent pickup, in-transit, arrival, delivery, delay, and other shipment milestones. | Salesforce, ServiceNow, SAP S/4HANA, customer notification services | Martini normalizes timestamps and status values, evaluates event ordering and precedence, deduplicates by event identifiers, and routes updates to downstream workflows. |
| Stops | Represent pickup, delivery, or intermediate locations associated with a transportation movement. | Oracle Transportation Management, Manhattan Active Transportation Management, Blue Yonder | Martini maps stop sequences, facility references, appointment context, and local time information into the target transportation model. |
| Carriers | Identify transportation providers responsible for executing a movement. | Oracle Transportation Management, SAP S/4HANA, Blue Yonder, Manhattan Active Transportation Management | Martini applies carrier identifier crosswalks, validates required references, and enriches shipment updates before sending them downstream. |
| Facilities | Represent warehouses, distribution centers, ports, customer sites, and other transportation locations. | SAP S/4HANA, Microsoft Dynamics 365, Oracle Transportation Management | Martini normalizes facility identifiers, addresses, time zones, and location roles before mapping them to enterprise logistics objects. |
| Equipment | Represent trailers, containers, trucks, or other transport equipment associated with a movement. | Transportation management applications, ERP logistics modules, operational data stores | Martini maps equipment identifiers and types, preserves vendor references, and applies validation rules before updating target systems. |
Authentication and security considerations
OAuth 2.0 and protected configuration
project44 API access uses OAuth 2.0 bearer tokens. The token endpoint, scopes, audience, regional authorization host, and permissions vary by API product and tenant.
- Store client IDs, client secrets, token settings, scopes, and regional endpoints as protected Martini environment secrets.
- Reuse valid access tokens until expiry where appropriate and never log tokens or client secrets.
- Confirm that the provisioned project44 permissions authorize the specific API resources used by the workflow.
- For callbacks, verify the applicable project44 authentication, signature, timestamp, and replay-protection model before processing events.
Operational considerations for project44 integrations
Rate limits and pagination
Confirm rate limits for each project44 API product and use bounded retries with backoff for HTTP 429 and transient 5xx responses. Process documented pages or cursors incrementally rather than repeatedly retrieving full shipment histories.
Synchronization and idempotency
Use watermarks, cursors, overlap windows, stable shipment identifiers, and event identifiers to support incremental processing. Do not assume tracking events arrive in order; compare timestamps, status precedence, or vendor-provided sequence information before updating downstream systems.
Schema and identifier management
Payloads vary by project44 product and may evolve. Validate required fields, tolerate additive fields, preserve vendor references, and maintain explicit mappings between shipment, order, booking, carrier, facility, and delivery identifiers.
Retries and testing
Classify authentication, authorization, validation, not-found, rate-limit, vendor, network, and downstream failures separately. Test callback security, pagination, duplicate delivery, late events, time zones, and reconciliation behavior before production deployment.
Why use Martini instead of scripts or point-to-point integrations?
Centralized integration logic
Martini provides a maintainable place to orchestrate project44 API calls, supported callbacks, scheduled reconciliation, transformations, target updates, and exception handling instead of duplicating logic across scripts or point-to-point interfaces.
Reusable APIs and workflows
Martini can expose a normalized REST API for internal consumers while workflows encapsulate project44 authentication, identifier mapping, business rules, retries, and downstream delivery behavior.
Operational control
- Use protected environment configuration for OAuth credentials and regional settings.
- Apply consistent validation, idempotency, checkpointing, and retry policies.
- Monitor workflow execution and retain safe correlation and failure information for reconciliation.
- Extend transformations with custom logic when vendor-specific rules require more flexibility.
Frequently asked questions
project44 can be integrated through its REST APIs using OAuth 2.0 bearer-token authentication. Enterprise workflows can register tracking requests, retrieve shipment and movement details, query tracking events, and work with transportation resources exposed by the subscribed API product. Selected products and tenants also support webhook-style notifications for certain shipment or movement events. Scheduled synchronization remains useful for reconciliation, backfill, and event coverage gaps.
Yes. Martini can integrate with project44 by consuming its documented REST APIs, using OAuth 2.0 credentials, receiving supported project44 event notifications, and orchestrating mappings and downstream updates through workflows. The exact resources, events, regional endpoints, and permissions depend on the project44 API product and tenant.
No. A dedicated project44 connector is not required. Martini can use project44’s native REST APIs, OAuth 2.0 authentication, supported webhook-style callbacks, and scheduled workflows to implement the integration. No native Martini project44 connector was identified in the supplied context.
Lonti does not charge an additional per-connector or per-vendor fee to integrate project44 with Martini. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from project44, cloud infrastructure, or other third-party systems depending on subscriptions, usage, and deployment model.
Use the project44 REST APIs as the primary integration method. Use supported webhook-style notifications for selected event-driven scenarios, and scheduled workflows for reconciliation, backfill, pagination, or resources without the required event coverage. GraphQL and SOAP APIs were not confirmed for project44.
Martini can receive webhook-style callbacks when the applicable project44 product and tenant support them. Event coverage is not universal across all project44 resources, so the supported event types, payload completeness, authentication or signature requirements, and retry behavior should be verified before implementation.
Use a watermark, cursor, event timestamp, or vendor-provided continuation value for incremental synchronization, with a small overlap window for late-arriving changes. Deduplicate using a project44 event ID where available, or a stable combination of shipment identifier, event type, timestamp, and status version. Reconciliation workflows can detect missed notifications and mismatches.
Yes. Martini can expose a REST API that provides internal applications with a stable shipment-status or tracking interface. A workflow behind the API can call project44, transform vendor-specific responses, apply authorization and business rules, and return a normalized model without requiring each consumer to understand project44-specific details.
Related Martini documentation
Operations
Connect project44 with Martini
Use Martini to build secure, maintainable project44 integrations for shipment visibility, transportation events, reconciliation, and downstream enterprise workflows.