.png)
Pricefx Integration Guide
Integrate Pricefx with enterprise applications through authenticated REST APIs, pricing workflows, asynchronous processing, and selected callback mechanisms.
Pricefx integration options at a glance
Pricefx is primarily integrated through authenticated REST APIs that exchange JSON for Products, Customers, Price Lists, Price Records, Rebates, Quotes, calculations, and related commercial data. Selected Pricefx deployments may provide callback or event-oriented notifications, but coverage must be confirmed for each process. Bulk, asynchronous, and batch operations can support larger imports, calculations, and exports where the tenant exposes the relevant job model. File-based exchange may also be configured for selected feeds. Martini can manage tenant-specific authentication, orchestrate scheduled or event-driven workflows, transform payloads, expose normalized APIs, and apply retry, checkpointing, and idempotency controls.
| Integration point | Supported by Pricefx? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Pricefx primarily uses authenticated REST APIs for Products, Customers, Price Lists, Price Records, Rebates, Quotes, pricing calculations, and commercial data exchange. | Martini can consume the Pricefx REST APIs, expose REST APIs to surrounding applications, transform JSON payloads, and orchestrate end-to-end workflows. |
| Webhooks / outbound callbacks | Limited | Selected Pricefx processes may provide callback or event-oriented notifications, but broad coverage across Pricefx objects and events is not confirmed. | Martini can expose an authenticated API endpoint or receive a supported webhook-style notification, validate it, retrieve the current object when needed, and initiate downstream processing. |
| Bulk, asynchronous, and batch APIs | Limited | Bulk or asynchronous processing may support large master-data loads, pricing calculations, exports, and rebate or agreement processing. Exact endpoints and job models vary by tenant and module. | Martini can submit jobs, persist job identifiers, poll with controlled intervals, retrieve results, and deliver outputs idempotently. |
| File and attachment exchange | Limited | File-based imports, exports, or scheduled feeds may be configured for selected Pricefx processes. Supported formats and transfer mechanisms require tenant confirmation. | Martini can coordinate file-based workflows, transform flat-file content where applicable, invoke Pricefx endpoints, and route rejected files or records for review. |
| Authentication | Yes | Pricefx API access commonly uses bearer-token-style authentication, service accounts or API users, tenant or partition context, permissions, and HTTPS. | Martini can manage environment-specific credentials and endpoint configuration, acquire or renew tokens through reusable workflow logic, and keep secrets outside mappings and source code. |
| Scheduled synchronization | Yes | Scheduled workflows are suitable for Products, Customers, Price Lists, Price Records, Rebates, exports, reconciliations, and processes where callback coverage is limited. | Martini can trigger workflows on a schedule, maintain checkpoints, paginate through Pricefx data, throttle requests, and report processing outcomes. |
How Pricefx exposes data and business events
Pricefx REST APIs
Pricefx is primarily integrated through authenticated REST APIs that exchange JSON for master data, pricing calculations, price outputs, rebates, quotes, and related commercial processes. Endpoint names, permissions, and object availability can vary by tenant and module.
Martini implementation pattern
Martini consumes the documented Pricefx REST operations from workflows or exposed APIs. It stores tenant-specific configuration as secrets, maps source and target models, applies business rules, and records request, response, and correlation information for operational traceability.
Implementation sequence
Pricefx callbacks
Pricefx may provide callback or event-oriented notifications for selected processes, but broad webhook coverage for all objects and events was not confirmed. The notification may contain a full payload or only an identifier, and delivery behavior must be verified for the tenant.
Martini implementation pattern
Martini exposes an authenticated endpoint or webhook-consuming workflow for the supported Pricefx notification. The workflow validates the request, retrieves the current Pricefx object when necessary, applies deduplication, and starts downstream processing while retaining a reconciliation path.
Implementation sequence
Pricefx asynchronous and batch processing
Enterprise Pricefx deployments may use bulk imports, exports, or asynchronous calculation and job operations for larger datasets. Exact job endpoints, status values, and completion behavior require confirmation in the tenant documentation.
Martini implementation pattern
Martini submits a Pricefx job or batch request, persists the returned job identifier, and polls under controlled limits until completion or timeout. A completed result is transformed and delivered once, while failed or expired jobs follow an operational error path.
Implementation sequence
Common Pricefx integration patterns
Pattern 1: Synchronize Products and Customers to Pricefx
When to use this pattern
Use this pattern when an ERP or CRM is the system of record for commercial master data and Pricefx requires current Products and Customers for pricing, segmentation, or eligibility decisions.
Integration direction
Example Mapping
| Pricefx Field | Canonical Field | Target Field |
|---|---|---|
| Product.externalId | productId | Product identifier |
| Customer.accountNumber | customerId | Customer identifier |
| Product.unitOfMeasure | unitOfMeasure | Product unit of measure |
| Customer.marketSegment | customerSegment | Customer segment |
Martini implementation pattern
A scheduled or source-triggered Martini workflow retrieves changed master data, validates required identifiers and tenant context, maps the payload to Pricefx structures, and performs controlled upserts. It records rejected records, throttles large transfers, and retries only transient failures.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Publish Price Lists and Price Records
When to use this pattern
Use this pattern when Pricefx is the pricing authority and commerce, sales, or ERP applications need approved prices with correct currencies, effective dates, units, and customer context.
Integration direction
Example Mapping
| Pricefx Field | Canonical Field | Target Field |
|---|---|---|
| PriceRecord.productId | sku | Shopify product or variant identifier |
| PriceRecord.price | unitPrice | selling price |
| PriceRecord.currency | currencyCode | currency |
| PriceRecord.effectiveFrom | validFrom | publication start |
Martini implementation pattern
Martini retrieves Price Lists or Price Records through paginated or asynchronous Pricefx operations, filters approved and effective results, transforms the target representation, and publishes changes idempotently. Correlation identifiers and response statuses are stored to prevent duplicate publication after retries.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- pagination and checkpointing
- error handling
Pattern 3: Provide a Transactional Price or Quote API
When to use this pattern
Use this pattern when Salesforce, Dynamics 365, or another sales application needs a normalized API for customer-specific pricing or quote calculations without embedding Pricefx-specific logic in the client.
Integration direction
Example Mapping
| Pricefx Field | Canonical Field | Target Field |
|---|---|---|
| request.customerId | customerId | Pricefx Customer identifier |
| request.productLines | quoteLines | Pricefx Products and quantities |
| request.currency | currencyCode | Pricefx currency |
| response.calculatedPrice | unitPrice | sales application price |
Martini implementation pattern
Martini exposes a secured REST API, validates customer, product, quantity, currency, and market inputs, invokes the applicable Pricefx pricing or quote operation, and normalizes the response. Validation errors are returned immediately, while transient Pricefx failures follow bounded retry rules and include a correlation ID.
Martini capabilities used
- API exposure
- API consumption
- authentication and authorization
- data mapping
- business rules
- error handling
Pattern 4: Orchestrate an Asynchronous Pricing Job
When to use this pattern
Use this pattern for large pricing calculations, exports, or rebate processing where Pricefx returns a job identifier and completion must be handled separately from submission.
Integration direction
Example Mapping
| Pricefx Field | Canonical Field | Target Field |
|---|---|---|
| job.id | sourceJobId | loadJobId |
| job.status | processingStatus | load status |
| PriceRecord.price | calculatedPrice | analytics price |
| PriceRecord.effectiveTo | validTo | analytics validity end |
Martini implementation pattern
Martini submits the operation, stores the job ID and source correlation, polls with bounded intervals, and retrieves the completed output. It applies schema validation and decimal preservation before loading the target, and prevents duplicate delivery if the workflow is restarted after successful Pricefx processing.
Martini capabilities used
- workflows
- asynchronous orchestration
- scheduling
- data mapping
- checkpointing
- error handling
Applications commonly integrated with Pricefx
Pricefx commonly participates in enterprise pricing architectures alongside sales, ERP, commerce, workflow, and analytics applications. The exact integration scope depends on the tenant configuration, Pricefx modules, and the business process being implemented.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Use Pricefx pricing, quoting, and customer-specific calculations during sales processes. | Salesforce → Martini → Pricefx | Expose a Martini REST API for Salesforce, validate customer and product context, call the relevant Pricefx pricing or quote operation, normalize the response, and return calculated values to Salesforce. |
| SAP S/4HANA | Synchronize Products, Customers, costs, sales data, and published prices between the ERP and pricing platform. | SAP S/4HANA → Martini → Pricefx | Use scheduled Martini workflows to retrieve or receive master data, map ERP fields to Pricefx payloads, submit controlled upserts, and route validation failures for correction. |
| Oracle NetSuite | Exchange product, customer, cost, price-list, and order-related data with Pricefx. | Oracle NetSuite → Martini → Pricefx | Orchestrate bidirectional REST-based synchronization with checkpoints, business-key matching, currency preservation, and separate handling for transient and validation errors. |
| Microsoft Dynamics 365 | Support sales quoting, product pricing, customer segmentation, and price publication. | Microsoft Dynamics 365 → Martini → Pricefx | Expose or consume APIs at the integration boundary, transform Dynamics 365 and Pricefx models, apply pricing eligibility rules, and publish approved results to the required application. |
| Shopify | Publish approved Price Lists or Price Records to an online storefront and provide product or order context for pricing workflows. | Pricefx → Martini → Shopify | Retrieve approved Pricefx results, map currencies, effective dates, products, and customer segments to the Shopify model, then publish idempotently while recording response identifiers. |
| ServiceNow | Make pricing or approval information available to workflows involving commercial requests, procurement, or service-related offerings. | ServiceNow → Martini → Pricefx | Receive a ServiceNow request through an API, validate the business context, invoke Pricefx pricing logic, and return or persist the normalized result for the ServiceNow workflow. |
| Snowflake | Deliver pricing, rebate, and margin outputs for analytics and reporting. | Pricefx → Martini → Snowflake | Extract paginated, batch, or asynchronous Pricefx outputs, transform them into analytics-oriented structures, and load them into Snowflake with checkpoints and duplicate protection. |
| Workday | Exchange selected organization or finance-related reference data where pricing or rebate processes depend on it. | Workday → Martini → Pricefx | Use a scoped workflow for the required reference data, map only the fields needed by Pricefx, validate organizational and effective-date values, and preserve audit correlation identifiers. |
How to build a Pricefx integration in Martini
Objective
Establish tenant-specific Pricefx connectivity with environment-specific URLs, context, and authenticated service-account access.
Instructions in Martini
- Confirm the Pricefx token flow, required headers, tenant or partition context, and permissions.
- Store credentials, tokens, endpoint URLs, and identifiers in Martini secrets or environment configuration.
- Use separate Pricefx service accounts and configuration for development, test, and production.
Objective
Select a scheduled, API-led, or supported callback trigger based on the Pricefx process and its event coverage.
Instructions in Martini
- Use a scheduler for reconciliation, master-data synchronization, and periodic exports.
- Expose a secured Martini API for transactional pricing or quote requests.
- Use a callback trigger only after confirming the Pricefx event, delivery, and authentication behavior.
Objective
Read or receive Pricefx data using pagination, bulk operations, or asynchronous jobs appropriate to the volume.
Instructions in Martini
- Retrieve Products, Customers, Price Lists, Price Records, Rebates, or Quotes through documented REST operations.
- Persist cursors, offsets, checkpoints, or asynchronous job identifiers.
- Use bounded page sizes and controlled concurrency.
Objective
Coordinate Pricefx calls, target-system calls, validation, branching, and long-running processing in a maintainable Martini workflow.
Instructions in Martini
- Separate submission, polling, transformation, publication, and reconciliation stages where appropriate.
- Apply timeouts and maximum polling durations to asynchronous operations.
- Preserve source and Pricefx correlation identifiers across workflow steps.
Objective
Convert Pricefx JSON and commercial data into the canonical and target models without losing pricing semantics.
Instructions in Martini
- Map identifiers, currencies, decimal values, units of measure, customer segments, and effective dates explicitly.
- Validate required fields and tenant-specific custom attributes before submission.
- Use reusable transformations for Products, Customers, pricing outputs, Rebates, and Quotes.
Objective
Ensure that only valid, approved, and effective commercial data is published or used in downstream decisions.
Instructions in Martini
- Apply approval, effective-date, market, currency, and customer-segmentation rules.
- Do not implicitly convert currencies or overlap effective periods without an explicit rule.
- Route validation failures separately from transient transport failures.
Common Pricefx data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Products | Items for which prices, costs, margins, or pricing rules are calculated. | SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365, Salesforce, Shopify | Martini maps product identifiers, descriptions, units, attributes, and effective data to Pricefx or downstream models, using pagination, validation, and business-key upserts. |
| Customers | Customer accounts or commercial parties used in pricing, segmentation, and eligibility decisions. | SAP S/4HANA, Salesforce, Oracle NetSuite, Microsoft Dynamics 365 | Martini synchronizes customer identifiers, segments, markets, currencies, and eligibility attributes while preserving tenant context and rejecting incomplete payloads. |
| Price Lists | Collections of prices or pricing outputs associated with products, markets, currencies, or customer groups. | Shopify, Salesforce, SAP S/4HANA, Microsoft Dynamics 365, Snowflake | Martini retrieves or submits Price Lists, preserves effective dates and currencies, applies publication rules, and prevents duplicate downstream delivery. |
| Price Records | Product-level or customer-specific price values with related effective-date information. | Salesforce, Shopify, SAP S/4HANA, Microsoft Dynamics 365, Snowflake | Martini transforms decimal values, units, currencies, customer context, and effective dates, then applies idempotent upsert or publication logic. |
| Rebates | Rebate programs, agreements, calculations, eligibility data, and settlement-related outputs. | SAP S/4HANA, Oracle NetSuite, Snowflake, finance platforms | Martini retrieves or submits rebate-related data, validates agreement and date fields, handles batch results, and routes calculation or validation failures for review. |
| Quotes | Pricing proposals or quote calculations for specific customers, products, or transactions. | Salesforce, Microsoft Dynamics 365, Oracle NetSuite, sales applications | Martini exposes a normalized quote API, validates the request, invokes the relevant Pricefx operation, maps the response, and returns correlation and error details. |
Authentication and security considerations
Tenant-aware authentication
Pricefx integrations commonly use authenticated REST access with bearer-token-style credentials, service accounts or API users, tenant or partition context, permissions, and HTTPS. The exact token endpoint, grant type, scopes, and headers must be confirmed for the tenant.
Martini security practices
- Store Pricefx credentials, tokens, tenant identifiers, and API URLs as environment-specific Martini secrets.
- Use least-privilege Pricefx roles and separate service accounts for development, test, and production.
- Keep credentials out of workflow mappings and source code.
- Protect Martini APIs used for quote requests or callbacks with authentication and authorization.
Operational considerations for Pricefx integrations
Reliability and scale
- Confirm pagination, quotas, rate limits, and concurrency guidance for each Pricefx endpoint.
- Use bulk or asynchronous processing for large workloads where the tenant documents those operations.
- Persist cursors, checkpoints, job identifiers, and correlation IDs.
- Retry transient failures with bounded exponential backoff, but do not blindly retry validation or permission failures.
Pricing data integrity
- Preserve decimal precision, currency codes, units of measure, customer segments, and effective dates.
- Use stable identifiers or business keys to make upserts and downstream publication idempotent.
- Validate custom attributes, enumerations, and calculated fields because Pricefx configurations can vary by tenant and module.
- Maintain scheduled reconciliation even when callbacks are available because event coverage may be limited.
Why use Martini instead of scripts or point-to-point integrations?
Maintainable integration logic
Martini centralizes Pricefx authentication, API orchestration, mappings, business rules, retries, checkpoints, and monitoring in reusable workflows and APIs rather than duplicating logic across point-to-point scripts.
Adaptable enterprise delivery
Martini can expose a stable pricing or quote API to surrounding applications while keeping Pricefx-specific behavior behind the integration boundary. This supports changes in tenant configuration, target applications, payload formats, and processing models without requiring every client to change.
- Orchestrate real-time, scheduled, batch, and asynchronous Pricefx processes.
- Apply consistent validation, idempotency, error routing, and operational logging.
- Transform Pricefx data for ERP, CRM, commerce, finance, and analytics destinations.
Frequently asked questions
Pricefx is primarily integrated through authenticated REST APIs that exchange JSON for Products, Customers, Price Lists, Price Records, Rebates, Quotes, calculations, and related commercial data. Enterprise workflows can also use scheduled synchronization, bulk or asynchronous processing, file exchange where configured, and selected callbacks or event-oriented notifications.
Yes. Martini can consume Pricefx REST APIs, expose APIs for sales and commerce applications, orchestrate pricing and synchronization workflows, transform commercial data, and receive supported Pricefx callback or webhook-style notifications where the tenant provides them.
No. A dedicated Pricefx connector is not required. Martini can integrate using Pricefx's confirmed native REST APIs, authentication methods, supported asynchronous operations, configured file interfaces, and selected callback mechanisms.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Pricefx. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Pricefx, cloud infrastructure, or other third-party systems based on subscriptions, usage, and deployment model.
Authenticated Pricefx REST APIs are the primary and recommended method for new integrations. Bulk or asynchronous operations can be used for larger workloads when documented for the tenant. GraphQL and SOAP should not be assumed because they were not confirmed in the reviewed Pricefx sources.
Pricefx may provide callback or event-oriented mechanisms for selected processes, but broad coverage for all objects and events was not confirmed. Confirm the event scope, payload shape, authentication, retry behavior, and whether the notification requires a follow-up API retrieval. Scheduled reconciliation remains important.
Martini can run scheduled or event-driven workflows that retrieve or receive Pricefx data, paginate or process asynchronous jobs, map it to canonical and target models, and preserve currencies, decimals, units, customer context, and effective dates. Checkpoints and business-key matching support incremental and idempotent synchronization.
Martini can distinguish authentication, permission, validation, rate-limit, and server-side failures, retry transient failures with controlled backoff, and route rejected data to an operational error path. Stable identifiers, job IDs, correlation IDs, checkpoints, and idempotent publication help prevent duplicate Price Records, Quotes, Rebates, or job results.
Related Martini documentation
API Integration
Data Processing
Build a maintainable Pricefx integration with Martini
Use Martini to connect Pricefx with enterprise applications through secure APIs, orchestrated workflows, data transformation, and reliable synchronization patterns.