Standard-Order-API

Standard Order Experience API

Version: v1.0.0

Status: Production Ready

API Type: Experience Layer

Protocol: REST/HTTPS

Last Updated: June 15, 2026

Table of Contents

• Overview
• API Architecture
• API Endpoints
  • POST /order - Create an order using Basic Authentication
  • POST /orderUpdate - Receive order status updates from backend systems
  • POST /v2/order - Create an order using OAuth 2.0 Authentication
• Data Models
• Field Specifications
• Schema Validation Rules
• Error Handling
• Authentication

Overview

General Information

Environment URLs

📝 Note: This documentation uses the QC environment (https://muleqc.diam.compucom.com) in all examples. Replace with the appropriate environment URL for your specific needs.

Purpose

The Standard Order Experience API serves as a centralized integration layer for managing device and inventory orders across multiple enterprise clients. It provides a unified interface for order processing, status updates, and workflow orchestration between client systems and backend order management platforms.

Key Features

📝 Order Creation

Accept and process orders from various client portals with comprehensive validation, transformation, and intelligent routing to backend systems such as DIMS or LCAM.

🔄 Status Updates

Receive real-time order status updates from backend systems and propagate them to the appropriate client applications, ensuring seamless communication throughout the order lifecycle.

🔀 Client Routing

Intelligent routing based on client identifiers with support for client-specific data transformations, business rules, and processing workflows.

🛡️ Error Handling

Comprehensive error handling with automatic retry mechanisms in the Mule runtime. Errors are returned to customers for the order creation flow, and to backend systems for order updates, enabling graceful recovery and retry capabilities.

Use Cases

• Multi-Client Integration: Single API endpoint serving multiple client organizations with customized requirements and workflows
• Order Lifecycle Management: End-to-end order tracking from creation through fulfillment
• System Orchestration: Seamless integration between client portals and backend order management systems
• Real-Time Status Updates: Bi-directional communication for order status changes

API Architecture

High-Level Architecture

┌──────────────────────────────────────────┐
│         Client Systems & Portals         │
│      (Web, Mobile, ERP Systems)          │
└────────────────┬─────────────────────────┘
                 │ HTTPS/REST
                 │
┌────────────────▼──────────────────────────────────┐
│      Standard Order Experience API                │
│   ┌──────────────────────────────────────────┐    │
│   │   APIKit Router (RAML Validation)        │    │
│   └─────────────┬────────────────────────────┘    │
│                 │                                  │
│   ┌─────────────▼────────────────────────────┐    │
│   │   Client Identification & Routing        │    │
│   │   • Parent Customer Number Resolution    │    │
│   │   • Dynamic Client Configuration         │    │
│   └─────────────┬────────────────────────────┘    │
│                 │                                  │
│   ┌─────────────▼────────────────────────────┐    │
│   │   Data Transformation Layer              │    │
│   │   • Schema Validation                    │    │
│   │   • Field Mapping & Truncation           │    │
│   │   • Client-Specific Transformations      │    │
│   │   • Sales Reference Number Generation    │    │
│   └─────────────┬────────────────────────────┘    │
└─────────────────┼────────────────────────────────┘
                  │
         ┌────────┴────────┐
         │                 │
    ┌────▼─────────┐  ┌────▼─────────┐
    │ DIMS System  │  │ LCAM System  │
    │ (Backend)    │  │ (Backend)    │
    └──────────────┘  └──────────────┘

Integration Points

ℹ️ Architecture Pattern
This API follows the MuleSoft API-Led Connectivity approach as an Experience Layer API. It abstracts client-specific complexities and provides a consistent, easy-to-use interface while delegating core business processing to backend system APIs.

API Endpoints

The API exposes three main endpoints for order creation and status management. All endpoints are prefixed with /api/standard-order/

POST /order

Flow Type: Synchronous

Response Code: 201 Created

Response Time: ~2-5 seconds (typical)

Authentication: Basic Auth

Description

Creates a new order with synchronous processing. This endpoint provides immediate validation, processes the order, and returns confirmation upon successful submission to the backend system (DIMS or LCAM).

Features

• Comprehensive Field Validation: Enforces backend system field length and format requirements
• Intelligent Client Routing: Automatic routing based on parent customer number
• Sales Reference Number Generation: Auto-generates unique order reference numbers if not provided
• Real-Time Processing: Synchronous order creation with immediate confirmation

Request Example

Endpoint: POST https://muleqc.diam.compucom.com/api/standard-order/order

Headers:

Content-Type: application/json

Authorization: Basic <base64-encoded-credentials>

Body:

json

{

"order": [{

"salesRefNumber": "M0001234",

"customerNumber": "530101390",

"parentCustomerNumber": "799249461",

"entryDate": "08/26/20",

"requestedDate": "08/26/20",

"shipCustomerName": "Dane, Jane",

"shipCity": "FORT MILL",

"shipZipCode": "29707",

"shipAddress1": "8106 Calvin Hall Road",

"shipAddress2": "",

"shipAddress3": "",

"shipState": "SC",

"shipCountry": "US",

"shipPhone": "803-555-0123",

"requestedByEmail": "jane.dane@example.com",

"requestedForEmail": "recipient@example.com",

"requestedForName": "John Smith",

"requestedForPhone": "803-555-0456",

"customerPOReleaseNumber": "1098723456",

"customerPONumber": "PO-2020-08-001",

"viaCode": "bw",

"geoCode": 41,

"token": "",

"creditCardType": "",

"orderDetails": [

{

"orderLine": 1,

"customerPOLine": 1300,

"quantityOrdered": 2.0,

"price": 65.44,

"itemNumber": "R65736",

"description": "APC RACK SCREWS AND NUTS",

"manPartNo": "AR8100"

},

{

"orderLine": 2,

"customerPOLine": 1301,

"quantityOrdered": 1.0,

"price": 24.40,

"itemNumber": "R61591",

"description": "NETGEAR FS108 SWITCH 8 PORTS",

"manPartNo": "FS108NA"

}

],

"udf": [

{

"fieldNumber": 1,

"orderLine": 0,

"fieldName": "user_id",

"fieldDescription": "jdane",

"fieldLevel": "H"

},

{

"fieldNumber": 2,

"orderLine": 0,

"fieldName": "employee_number",

"fieldDescription": "EMP123456",

"fieldLevel": "H"

},

{

"fieldNumber": 3,

"orderLine": 0,

"fieldName": "email-addr",

"fieldDescription": "jane.dane@example.com",

"fieldLevel": "H"

}

],

"memo": [

{

"orderLine": 0,

"type": "o",

"comments": "Please deliver to front door reception desk"

}

]

}]

}

Response Example

201 Created - Success Response

{
  "status": "Success",
  "salesRefNumber": "M0047665"
}

400 Bad Request - Validation Error

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Missing required field: parentCustomerNumber"
  }
}

500 Internal Server Error - System Error

{
  "error": {
    "code": "BACKEND_ERROR",
    "message": "Unable to connect to backend system. Please try again later."
  }
}

POST /orderUpdate

Flow Type: Synchronous

Response Code: 200 OK

Retry Attempts: 3 attempts with exponential backoff

Authentication: Client-Specific (Basic Auth or OAuth 2.0)

Description

Receives order status updates from backend systems (DIMS or LCAM) and routes them to the appropriate client systems. This endpoint handles various order lifecycle events including shipment notifications, invoice generation, and order completion.

Features

• Automatic Retry Logic: Built-in retry mechanism with exponential backoff for transient failures
• OAuth Token Refresh: Automatic token refresh for expired OAuth credentials
• Multi-Client Routing: Intelligent routing based on parent customer number
• Comprehensive Status Updates: Supports order status, shipment tracking, invoice details, and serial numbers

Request Example

Endpoint: POST https://muleqc.diam.compucom.com/api/standard-order/orderUpdate

Headers:

Content-Type: application/json

Authorization: Depeds on client system

Body:

json

{

"orderHeader": [{

"transactionId": 82,

"salesRefNumber": "M0000286",

"orderNumber": 109593246,

"customerPONumber": "PO-2022-01-027",

"orderDate": "01/27/22",

"scheduledDate": "01/28/22",

"carrierId": "BW",

"orderStatus": "80",

"orderStatusDescription": "Partial Shipment",

"taxAmount": 72.50,

"totalAmount": 1010.00,

"currencyId": "USD",

"invoiceDate": "01/28/22",

"paymentTermId": "09",

"invoiceNumber": 65426326,

"customerNumber": "000054602",

"parentCustomerNumber": "ASSOCPURC",

"shipDate": "01/28/22",

"shipViaDesc": "Ground Shipping",

"dueDate": "02/27/22",

"ppsNumber": 21942216,

"callBackURL": "https://workflow.example.com/callback/243833/OAUpdateCallback/4863287883744102164",

"orderHeaderUdf": [

{

"orderNumber": 109593246,

"fieldName": "employee_number",

"fieldDescription": "EMP123456"

},

{

"orderNumber": 109593246,

"fieldName": "user_id",

"fieldDescription": "jsmith"

}

],

"orderDetails": [

{

"orderNumber": 109593246,

"lineNumber": 1,

"itemNumber": "EN4356",

"quantityOrdered": 2,

"quantityShipped": 2,

"customerPOLine": 1300,

"manPartNo": "32MU59-B",

"itemDescription": "32IN 4K 3840X2160 LED LCD MONITOR"

},

{

"orderNumber": 109593246,

"lineNumber": 2,

"itemNumber": "EG1181",

"quantityOrdered": 1,

"quantityShipped": 0,

"customerPOLine": 1301,

"manPartNo": "KB-800",

"itemDescription": "WIRELESS KEYBOARD"

}

],

"waybill": [

{

"ppsNumber": 21942216,

"packageId": "001",

"waybillNumber": "1Z999AA10123456784"

}

],

"invoiceLine": [

{

"invoiceNumber": 65426326,

"invoiceLinesId": 1,

"customerPOLine": 1300,

"qtyInvoiced": 2,

"itemNo": "EN4356",

"itemPrice": 500.00,

"grossAmount": 1000.00,

"taxAmount": 72.50,

"manPartNo": "32MU59-B",

"itemDescription": "32IN 4K 3840X2160 LED LCD MONITOR",

"invoiceLineUdf": [

{

"documentLineNo": 1,

"fieldName": "warranty_code",

"fieldDescription": "3YR-ONS"

}

],

"serialNumber": [

{

"invoiceLinesId": 1,

"serialNumber": "SN123456789ABC"

},

{

"invoiceLinesId": 1,

"serialNumber": "SN987654321XYZ"

}

]

}

]

}]

}

Response Example

200 OK - Success Response

{
  "status": 200,
  "message": "Order update processed successfully"
}

400 Bad Request - Invalid Payload

{
  "error": {
    "code": "INVALID_REQUEST",
    "message": "Invalid order update payload format"
  }
}

Error Handling & Retry Logic

• Connectivity Issues: Automatic retry with exponential backoff (1s, 2s, 4s intervals)
• Authentication Failures: OAuth token refresh with automatic retry
• Timeout Handling: 30-second timeout per attempt with retry on timeout
• Final Failure: After 3 failed attempts, error details are logged and returned to the backend system

POST /v2/order

Flow Type: Synchronous

Response Code: 201 Created

Version: 2.0

Authentication: OAuth 2.0

Description

This endpoint provides the same order creation functionality as /order but uses OAuth 2.0 authentication instead of Basic Auth. This version is maintained as part of the API versioning strategy to support clients requiring OAuth-based authentication.

Features

• OAuth 2.0 Authentication: Token-based authentication with automatic refresh
• Identical Functionality: Same validation, routing, and processing as /order
• Version Isolation: Future breaking changes will be isolated to this versioned endpoint

ℹ️ Version Strategy
This endpoint is maintained for API versioning and authentication flexibility. Future breaking changes to the order creation logic will be implemented in this versioned endpoint for OAuth clients, while /order continues to serve clients using Basic Authentication.

Request & Response

The request and response formats are identical to the POST /order endpoint, with the only difference being the authentication method.

Authentication Header:

Authorization: Bearer <oauth-access-token>

Data Models

Create Order Request Schema

{
  "order": [{
    "customerNumber": "string (optional, max 9)",
    "parentCustomerNumber": "string (required, max 14)",
    "entryDate": "string (required, format: MM/DD/YY)",
    "requestedDate": "string (required, format: MM/DD/YY)",
    "customerPONumber": "string (required, max 25)",
    "shipCustomerName": "string (required, max 35)",
    "shipAddress1": "string (required)",
    "shipAddress2": "string (optional, max 35)",
    "shipAddress3": "string (optional, max 35)",
    "shipCity": "string (required)",
    "shipState": "string (required, max 2)",
    "shipZipCode": "string (required, max 9)",
    "shipCountry": "string (required, max 3)",
    "shipPhone": "string (optional, max 25)",
    "requestedForEmail": "string (optional, max 250)",
    "requestedByEmail": "string (optional, max 250)",
    "requestedForName": "string (optional, max 50)",
    "requestedForPhone": "string (optional, max 50)",
    "customerPOReleaseNumber": "string (optional, max 35)",
    "shipPartially": "boolean (optional)",
    "viaCode": "string (optional, max 2)",
    "geoCode": "integer (optional, 0-999999999)",
    "token": "string (optional, max 20)",
    "creditCardType": "string (optional, max 30)",
    "tokenName": "string (optional)",
    "threeDeltaExpire": "string (optional, max 5, format: MM/YY)",
    "partnerBillingStreet": "string (optional, max 50)",
    "partnerBillingZip": "string (optional, max 10)",
    "callBackURL": "string (optional, max 250)",
    "salesRefNumber": "string (optional, max 8)",
    "orderDetails": [{
      "customerPOLine": "integer (optional, 0-999999999)",
      "orderLine": "integer (required, 0-999999999)",
      "quantityOrdered": "integer (required, 0-999999999)",
      "price": "number (required, multipleOf: 0.01)",
      "itemNumber": "string (required)",
      "description": "string (required)",
      "manPartNo": "string (optional)"
    }],
    "udf": [{
      "fieldNumber": "integer (optional, 0-99)",
      "fieldLevel": "string (optional, max 1)",
      "fieldName": "string (optional)",
      "fieldDescription": "string (optional, max 250)",
      "orderLine": "integer (optional, 0-999)"
    }],
    "memo": [{
      "orderLine": "integer (optional, 0-999)",
      "type": "string (optional, max 3)",
      "comments": "string (optional, max 32000)"
    }]
  }]
}

Update Order Request Schema

{
  "orderHeader": [{
    "transactionId": "integer (optional, max 999999999)",
    "salesRefNumber": "string (optional)",
    "customerNumber": "string (optional)",
    "parentCustomerNumber": "string (optional)",
    "orderNumber": "integer (optional, max 999999999)",
    "orderDate": "string (optional, format: MM/DD/YY)",
    "scheduledDate": "string (optional, format: MM/DD/YY)",
    "carrierId": "string (optional)",
    "orderStatus": "string (optional)",
    "orderStatusDescription": "string (optional)",
    "taxAmount": "number (optional, multipleOf: 0.01)",
    "totalAmount": "number (optional, multipleOf: 0.01)",
    "currencyId": "string (optional)",
    "invoiceDate": "string (optional, format: MM/DD/YY)",
    "paymentTermId": "string (optional)",
    "invoiceNumber": "integer (optional, max 999999999)",
    "anticipatedArrivalDate": "string (optional, format: MM/DD/YY)",
    "shipDate": "string (optional, format: MM/DD/YY)",
    "shipViaDesc": "string (optional)",
    "dueDate": "string (optional, format: MM/DD/YY)",
    "ppsNumber": "integer (optional, max 999999999)",
    "callBackURL": "string (optional)",
    "orderDetails": [{
      "orderNumber": "integer (optional, max 999999999)",
      "lineNumber": "integer (optional, max 999)",
      "itemNumber": "string (optional)",
      "quantityOrdered": "integer (optional, 0-999999999)",
      "quantityShipped": "integer (optional, 0-999999999)",
      "customerPOLine": "integer (optional, 0-999999999)",
      "manPartNo": "string (optional)",
      "itemDescription": "string (optional)",
      "orderLineUdf": [{
        "documentLineNo": "integer (optional, max 999999999)",
        "fieldName": "string (optional)",
        "fieldDescription": "string (optional)"
      }]
    }],
    "orderHeaderUdf": [{
      "orderNumber": "integer (optional, max 999999999)",
      "fieldName": "string (optional)",
      "fieldDescription": "string (optional)"
    }],
    "waybill": [{
      "ppsNumber": "integer (optional, max 999999999)",
      "packageId": "string (optional)",
      "waybillNumber": "string (optional)"
    }],
    "invoiceLine": [{
      "invoiceNumber": "integer (optional, max 999999999)",
      "invoiceLinesId": "integer (optional, max 999999999)",
      "customerPOLine": "integer (optional, 0-999999999)",
      "qtyInvoiced": "integer (optional, 0-999999999)",
      "itemNo": "string (optional)",
      "itemPrice": "number (optional, multipleOf: 0.01)",
      "grossAmount": "number (optional, multipleOf: 0.01)",
      "taxAmount": "number (optional, multipleOf: 0.01)",
      "manPartNo": "string (optional)",
      "itemDescription": "string (optional)",
      "invoiceLineUdf": [{
        "documentLineNo": "integer (optional, max 999999999)",
        "fieldName": "string (optional)",
        "fieldDescription": "string (optional)"
      }],
      "serialNumber": [{
        "invoiceLinesId": "integer (optional, max 999999999)",
        "serialNumber": "string (optional)"
      }]
    }]
  }]
}

Field Specifications

Create Order - Header Fields

Create Order - Order Detail Fields

Create Order - UDF (User Defined Fields)

Create Order - Memo Fields

Update Order - Header Fields

Update Order - Order Detail Fields

Update Order - Waybill Fields

Update Order - Invoice Line Fields

Schema Validation Rules

Create Order - Required Fields Validation

Create Order - Order Details Required Fields

Data Type Validations

Field Length Validations

Numeric Range Validations

ℹ️ RAML Validation
All requests are validated against RAML 1.0 schema definitions using the MuleSoft APIKit Router. Invalid requests are rejected with HTTP 400 Bad Request before reaching the application logic, ensuring data integrity and security.

⚠️ Validation Best Practices
- Always send numeric values as JSON numbers, not strings (e.g., 100 not "100")
- Ensure dates follow the exact format: MM/DD/YY (e.g., 08/26/20)
- Use lowercase for boolean values: true/false
- Empty strings ("") are different from null/missing fields in validation
- Arrays must have at least one item if required (e.g., orderDetails)
- Validate field lengths client-side to avoid unnecessary API calls

Error Handling

Error Response Format

All error responses follow a consistent format for easy parsing and error handling:

{
  "error": {
    "code": "ERROR_CODE",
    "message": "Detailed error message describing what went wrong"
  }
}

HTTP Status Codes

Common Error Codes

Retry Strategy

The API implements intelligent retry logic for transient failures:

• Automatic Retry: Failed requests are automatically retried up to 3 times
• Exponential Backoff: Retry intervals: 1 second, 2 seconds, 4 seconds
• Retry Conditions: Retries are attempted for:
  • Network connectivity issues (502, 503, 504)
  • Timeout errors (408)
  • Transient backend errors (500 with retry-able flag)
• Non-Retry Conditions: No retry for:
  • Validation errors (400)
  • Authentication failures (401)
  • Authorization failures (403)
  • Resource not found (404)

Client Retry Recommendations:

• Implement exponential backoff in client applications

• Maximum retry attempts: 3-5

• Initial retry delay: 1-2 seconds

• Log all retry attempts for troubleshooting

🚨 Error Monitoring
Critical errors trigger automated alerts for immediate investigation:
- Backend system connectivity failures
- Database connection issues
- Authentication/authorization failures
- High error rates exceeding thresholds
Alerts are sent to the operations team via email, Slack, and monitoring dashboards.

Authentication

The API supports two authentication methods to accommodate different client requirements and security policies.

Supported Authentication Methods

🔐 Basic Authentication

Traditional username and password authentication where credentials are base64-encoded in the Authorization header.

Use Case: Suitable for server-to-server integrations with secure credential storage.

Header Format:

Authorization: Basic <base64-encoded-credentials>

Example:

```

Username: api_user

Password: api_password

Base64 Encoded: YXBpX3VzZXI6YXBpX3Bhc3N3b3Jk

Header:

Authorization: Basic YXBpX3VzZXI6YXBpX3Bhc3N3b3Jk

```

Supported Endpoints:

• POST /order

• POST /orderUpdate

🎫 OAuth 2.0

Token-based authentication with automatic token refresh. Provides enhanced security with time-limited access tokens and refresh capabilities.

Use Case: Recommended for client applications, web portals, and integrations requiring enhanced security.

Supported Grant Types:

• Client Credentials

• Resource Owner Password Credentials (ROPC)

Header Format:

Authorization: Bearer <oauth-access-token>

Supported Endpoints:

• POST /v2/order

• POST /orderUpdate

OAuth 2.0 Token Endpoints

Development Environment

Production Environment

OAuth 2.0 Token Request

Client Credentials Grant:

POST /oauth/token HTTP/1.1
Host: sandboxapi.compucom.com
Content-Type: application/x-www-form-urlencoded

grant_type=client_credentials
&client_id=<your-client-id>
&client_secret=<your-client-secret>

Response:

json

{

"access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",

"token_type": "Bearer",

"expires_in": 300,

}

OAuth 2.0 Token Flow

The API implements intelligent OAuth token management with caching and automatic refresh:

1. Client requests API access
   ↓
2. Check Object Store for cached token
   ↓
3. If token exists and valid:
   → Use cached token

4. If token missing or expired:
   a. Request new token from OAuth provider
   b. Cache token in Object Store with expiration
   c. Use new token for API request
   ↓
5. Make API request with Bearer token
   ↓
6. If token expires during request:
   → Automatic refresh and retry

Token Caching Benefits:

• Performance: Reduces authentication overhead by caching tokens

• Efficiency: Minimizes calls to OAuth token endpoint

• Reliability: Automatic token refresh ensures uninterrupted service

• Scalability: Shared token cache across API instances

✅ Token Management Best Practices
- Cache tokens on the client side to reduce token requests
- Implement automatic token refresh before expiration
- Store tokens securely (never log or expose in URLs)
- Use HTTPS for all token requests and API calls
- Monitor token expiration and implement proactive refresh

Authentication Examples

Example 1: Order Creation with Basic Auth

curl -X POST https://muleqc.diam.compucom.com/api/standard-order/order \
  -H "Content-Type: application/json" \
  -H "Authorization: Basic YXBpX3VzZXI6YXBpX3Bhc3N3b3Jk" \
  -d '{
    "order": [{
      "parentCustomerNumber": "799249461",
      "entryDate": "08/26/20",
      "requestedDate": "08/26/20",
      "customerPONumber": "PO-2020-08-001",
      "shipCustomerName": "John Doe",
      "shipAddress1": "123 Main St",
      "shipCity": "New York",
      "shipState": "NY",
      "shipZipCode": "10001",
      "shipCountry": "US",
      "orderDetails": [{
        "orderLine": 1,
        "quantityOrdered": 1,
        "price": 100.00,
        "itemNumber": "ITEM001",
        "description": "Test Product"
      }]
    }]
  }'

Example 2: Order Creation with OAuth 2.0

# Step 1: Get OAuth Token
curl -X POST https://sandboxapi.compucom.com/oauth/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials" \
  -d "client_id=your-client-id" \
  -d "client_secret=your-client-secret"

# Response:
# {
#   "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
#   "token_type": "Bearer",
#   "expires_in": 300
# }

# Step 2: Create Order with Token
curl -X POST https://muleqc.diam.compucom.com/api/standard-order/v2/order \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  -d '{
    "order": [{
      "parentCustomerNumber": "799249461",
      "entryDate": "08/26/20",
      "requestedDate": "08/26/20",
      "customerPONumber": "PO-2020-08-001",
      "shipCustomerName": "John Doe",
      "shipAddress1": "123 Main St",
      "shipCity": "New York",
      "shipState": "NY",
      "shipZipCode": "10001",
      "shipCountry": "US",
      "orderDetails": [{
        "orderLine": 1,
        "quantityOrdered": 1,
        "price": 100.00,
        "itemNumber": "ITEM001",
        "description": "Test Product"
      }]
    }]
  }

Standard Order Experience API | Version 1.0.0

© 2026 CompuCom Systems, Inc. All rights reserved.

Last Updated: June 15, 2026

MuleSoft Anypoint Platform | CompuCom API Portal