.png)
Jedox Integration Guide
Integrate Jedox planning and analytics data with enterprise systems through REST APIs, scheduled workflows, batch processing, and controlled data transformation.
Jedox integration options at a glance
Jedox primarily integrates through REST APIs covering authentication, metadata, Databases, Cubes, Dimensions, Elements, and data operations. Jedox Integrator supports scheduled, batch-oriented loading, transformation, and file-based exchanges such as CSV or Excel planning inputs. A general-purpose webhook model for cube, cell, or dimension changes was not confirmed, so Martini can use scheduled workflows, polling, external orchestration, or a controlled Martini API instead. Martini stores Jedox credentials and tokens in protected configuration, calls the applicable REST endpoints, maps multidimensional data into target models, applies validation and business rules, and handles retries, reconciliation, and partial failures.
| Integration point | Supported by Jedox? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Authenticate clients, inspect Databases, Cubes, Dimensions, and Elements, read metadata, and read or write supported data values. Exact operations vary by Jedox release and deployment. | Martini can consume Jedox REST endpoints from workflows, store environment-specific configuration securely, transform responses, and expose reusable APIs around Jedox operations. |
| Authentication | Yes | Authenticate against the Jedox server and reuse the resulting session or token for subsequent REST requests while permissions remain governed by Jedox security settings. | Martini can keep credentials, tokens, base URLs, and client settings in protected secrets or environment configuration and pass authenticated context to workflow calls. |
| Bulk, asynchronous, and batch processing | Limited | Jedox Integrator supports batch-oriented loading, transformation, and process execution. REST bulk or asynchronous behavior depends on the endpoint and release. | Martini can orchestrate Integrator-related processes or chunk REST requests, schedule large loads, separate metadata from value processing, and track batch identifiers. |
| File import and export | Limited | Jedox Integrator supports file-oriented scenarios such as budget templates, planning input files, CSV or Excel exports, and staged data exchanges. | Martini can process structured files, validate rows, transform them into Jedox-compatible data, and coordinate file-based loads or exports with workflow checkpoints. |
| Scheduled synchronization | Yes | Scheduled or manually initiated processing is appropriate where universal change notifications are unavailable, including periodic planning extracts and incremental loads where markers exist. | Martini can trigger workflows on a schedule, maintain watermarks or run identifiers, prevent overlapping executions, and reconcile each completed run. |
| Webhooks and outbound callbacks | Not confirmed | A general-purpose webhook model for all Jedox cube, cell, dimension, or element changes was not confirmed. External orchestration or polling may be required for event-driven behavior. | Martini can expose a controlled API for approved callers or use scheduled polling, but it should not assume that Jedox emits notifications for every data change. |
| Database and analytics access | Limited | Jedox Integrator can connect to external data sources and perform ETL. Direct querying of internal Jedox application tables should not be assumed. | Martini can use supported Jedox APIs, Integrator processes, or external database endpoints without depending on undocumented internal platform tables. |
| GraphQL APIs | Not confirmed | No official Jedox GraphQL API was confirmed in the supplied research, so GraphQL should not be treated as a Jedox integration boundary. | Martini can consume GraphQL when a separate confirmed system provides it, but Jedox integrations should use confirmed REST or Integrator mechanisms. |
How Jedox exposes data and business events
Jedox REST APIs
Jedox REST APIs provide the primary integration boundary for authentication, administration, metadata, Databases, Cubes, Dimensions, Elements, and supported data operations. Endpoint availability and request formats can vary by release and deployment model.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates against the configured Jedox server, calls the required REST operation, validates the response, maps the result into a canonical or target model, and records identifiers and checkpoints for reconciliation.
Implementation sequence
Jedox Integrator batch processing
Jedox Integrator supports process-oriented data loading, transformation, and batch integration, including file-based exchanges and external data-source scenarios. Its use is particularly relevant for larger or staged transfers.
Martini implementation pattern
Martini implementation pattern: a scheduled or API-triggered workflow prepares validated input, invokes or coordinates the approved Integrator process, monitors the result where supported, and routes failures or reconciliation differences for follow-up.
Implementation sequence
Scheduled Jedox synchronization
A general-purpose Jedox webhook model for all data changes was not confirmed. Scheduled polling, incremental extraction where supported, and manually initiated processing are therefore practical integration approaches.
Martini implementation pattern
Martini implementation pattern: a scheduler starts a workflow, the workflow retrieves changed or scoped data using an available watermark or performs a controlled extract, compares the result with the prior checkpoint, and delivers changes downstream.
Implementation sequence
Jedox file-based exchange
Jedox Integrator supports file-oriented loading and exporting for planning templates, CSV or Excel exchanges, and staged data movement. A general-purpose attachment API was not confirmed.
Martini implementation pattern
Martini implementation pattern: a workflow receives or retrieves the approved file, validates its structure and business content, converts rows into Jedox dimensions and values, and coordinates the load with an auditable batch reference.
Implementation sequence
Common Jedox integration patterns
Pattern 1: Load ERP actuals into Jedox planning Cubes
When to use this pattern
Use this pattern when financial actuals, chart-of-accounts structures, organizational data, and periods from an ERP must populate Jedox for budgeting, forecasting, or variance analysis. It is suitable for scheduled loads with clear batch boundaries and reconciliation requirements.
Integration direction
Example Mapping
| Jedox Field | Canonical Field | Target Field |
|---|---|---|
| account | accountCode | Account Element |
| company or legal entity | organizationCode | Organization Element |
| posting period | fiscalPeriod | Time Element |
| amount | actualValue | Cube Cell value |
Martini implementation pattern
Martini retrieves approved ERP data, normalizes accounts, entities, currencies, and periods, resolves the target Jedox Database and Cube, validates that required Elements exist, writes values through the applicable REST or Integrator process, and records a source batch identifier. Transient failures are retried with bounded backoff, while rejected mappings are isolated for review.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
- reconciliation
Pattern 2: Synchronize workforce planning data
When to use this pattern
Use this pattern when Workday worker, organization, position, compensation, or headcount data must support workforce planning in Jedox. The workflow should distinguish approved planning inputs from incomplete or inactive workforce data.
Integration direction
Example Mapping
| Jedox Field | Canonical Field | Target Field |
|---|---|---|
| worker ID | workerIdentifier | Worker Element |
| supervisory organization | organizationCode | Organization Element |
| effective date | planningPeriod | Time Element |
| compensation or headcount | workforceValue | Cube Cell value |
Martini implementation pattern
A scheduled Martini workflow retrieves approved Workday data, maps organizational and workforce identifiers to Jedox Elements, validates effective dates and required dimensions, and updates the relevant planning Cube. The workflow rejects missing members, prevents overlapping runs, and returns a run result for operational review.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- validation
- business rules
- idempotency
- monitoring
Pattern 3: Load CRM pipeline data for revenue forecasting
When to use this pattern
Use this pattern when Salesforce or Microsoft Dynamics 365 Sales pipeline information is used to build revenue forecasts in Jedox. It supports periodic extraction, currency normalization, fiscal-period alignment, and optional publication of approved forecast results.
Integration direction
Example Mapping
| Jedox Field | Canonical Field | Target Field |
|---|---|---|
| opportunity amount | pipelineAmount | Revenue Cube Cell value |
| close date | forecastPeriod | Time Element |
| forecast category | forecastScenario | Scenario Element |
| account or territory | commercialOrganization | Organization Element |
Martini implementation pattern
Martini retrieves selected CRM Opportunities and related context, normalizes currency and fiscal periods, applies inclusion rules for stage and forecast category, resolves Jedox Dimensions and Elements, and writes the forecast inputs. Duplicate batches, missing members, and transient API failures are handled without silently overwriting approved planning data.
Martini capabilities used
- workflows
- API consumption
- data transformation
- business rules
- scheduled synchronization
- error handling
- audit logging
Pattern 4: Publish approved Jedox results to analytics
When to use this pattern
Use this pattern when approved planning outputs must be delivered to Power BI, Snowflake, or another reporting layer. It is useful for flattening multidimensional data into a stable tabular contract and preserving run-level reconciliation.
Integration direction
Example Mapping
| Jedox Field | Canonical Field | Target Field |
|---|---|---|
| Cube and coordinate | planningMetricContext | Metric dimensions |
| Element caption or key | dimensionMember | Dimension member column |
| Cell value | approvedPlanValue | Measure value |
| run identifier | integrationBatchId | Load batch key |
Martini implementation pattern
A Martini workflow extracts approved values from the selected Jedox Cubes, converts coordinates into dimensional rows, validates totals and data types, and loads the target data service. It stores the Jedox run and destination batch identifiers, retries transient destination failures, and prevents duplicate publication.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- JSON handling
- business rules
- idempotency
- reconciliation
Applications commonly integrated with Jedox
Jedox commonly participates in planning, forecasting, financial, workforce, and analytics architectures. Martini can connect these named applications to Jedox through their supported interfaces and Jedox REST APIs or Integrator-based processes, while keeping mappings, validation, scheduling, and error handling in reusable workflows.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Move Accounts, Opportunities, pipeline amounts, quota data, and forecast inputs into Jedox for revenue planning and optionally return approved forecast values. | Salesforce → Martini → Jedox | A scheduled Martini workflow retrieves Salesforce data, normalizes currencies and fiscal periods, resolves Jedox Dimensions and Elements, writes values to the appropriate Cubes, and records a batch identifier for reconciliation. |
| NetSuite | Load financial actuals, accounts, subsidiaries, and budgets into Jedox for planning and variance analysis. | NetSuite → Martini → Jedox | Martini consumes the NetSuite API, maps accounts, entities, periods, and currencies to Jedox metadata, validates totals, and performs an idempotent cube load with retry and exception handling. |
| SAP S/4HANA | Transfer financial actuals, master data, cost centers, and operational planning inputs into Jedox. | SAP S/4HANA → Martini → Jedox | A Martini workflow retrieves approved SAP data, applies canonical mappings for organizational and financial dimensions, stages large volumes where appropriate, and loads Jedox through REST or an approved Integrator process. |
| Microsoft Dynamics 365 Finance | Synchronize ledgers, legal entities, accounts, budgets, and actuals for enterprise financial planning. | Microsoft Dynamics 365 Finance → Martini → Jedox | Martini orchestrates incremental or scheduled extraction, validates financial periods and identifiers, resolves Jedox Elements before writing Cells, and reconciles source and destination totals. |
| Workday | Provide worker, organization, position, compensation, and headcount information for workforce planning. | Workday → Martini → Jedox | A scheduled workflow retrieves approved Workday data, converts organizational and workforce identifiers into Jedox dimension members, updates planning Cubes, and returns load results to an operations endpoint. |
| Power BI | Publish Jedox planning and performance data for enterprise dashboards and reporting. | Jedox → Martini → Power BI | Martini extracts approved cube values, flattens multidimensional data into a tabular structure, applies data-quality checks, and sends the result to the selected Power BI or intermediary data service. |
| Snowflake | Centralize Jedox planning outputs with other enterprise data for analytics, reconciliation, and historical reporting. | Jedox → Martini → Snowflake | Martini retrieves scoped Jedox data, adds run and batch metadata, transforms it into warehouse-ready structures, and writes it to Snowflake using the approved data-loading interface. |
| ServiceNow | Align financial or workforce planning inputs with operational demand, projects, or service portfolios. | ServiceNow → Martini → Jedox | Martini retrieves selected ServiceNow planning inputs, maps them to Jedox Dimensions and Elements, applies scope and period rules, and loads approved values through Jedox REST operations. |
How to build a Jedox integration in Martini
Objective
Establish the Jedox endpoint and authentication approach for the target deployment without embedding credentials in workflow logic.
Instructions in Martini
- Configure the Jedox base URL and deployment-specific settings
- Use a dedicated least-privilege integration account
- Store credentials, tokens, and client settings in Martini secrets or protected environment configuration
- Confirm the deployed Jedox version and applicable REST API contract
Objective
Select a trigger that reflects Jedox change-notification coverage and the business freshness requirement.
Instructions in Martini
- Use a scheduler for periodic polling or batch synchronization
- Use an approved external caller when a process must initiate the workflow
- Do not assume universal Jedox webhooks for Cube, Cell, Dimension, or Element changes
- Prevent overlapping runs when prior loads may still be executing
Objective
Authenticate and retrieve the required Jedox metadata or values before attempting a downstream transformation or write.
Instructions in Martini
- Authenticate with the Jedox server
- Resolve Databases, Cubes, Dimensions, and Elements before processing values
- Use scoped or incremental retrieval where a supported watermark exists
- Checkpoint progress for large metadata or data extracts
Objective
Coordinate source retrieval, Jedox operations, validation, target delivery, and reconciliation as a maintainable Martini workflow.
Instructions in Martini
- Separate metadata preparation from value processing where appropriate
- Use reusable workflow logic for authentication, mapping, and error handling
- Track source batches, Jedox identifiers, and destination runs
- Route partial failures to an exception path rather than discarding context
Objective
Convert multidimensional Jedox structures into the canonical and target models required by connected systems.
Instructions in Martini
- Map Dimensions and Elements explicitly
- Resolve names, keys, aliases, or captions according to the deployed contract
- Normalize currencies, periods, scenarios, and organizational identifiers
- Convert cube coordinates and Cells into the target tabular or application structure
Objective
Validate data quality and enforce planning, security, period, and idempotency rules before writing values.
Instructions in Martini
- Reject missing or inactive Elements before value loads
- Validate numeric, string, consolidated, and scenario-specific values
- Use stable source keys, periods, scenarios, and batch identifiers
- Separate controlled structural changes from ordinary data loads
Common Jedox data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Databases | Logical Jedox environments containing models and multidimensional data. | ERP platforms, data warehouses, reporting platforms, and Martini-managed integration processes. | Martini resolves the target Database before processing metadata or data, validates the configured identifier, and records it with the integration run. |
| Cubes | Multidimensional structures containing planning, reporting, and analytical measures. | ERP platforms, CRM systems, workforce systems, data warehouses, and reporting services. | Martini maps source measures and dimensional context to the correct Cube, applies value and period rules, and supports reconciliation after reads or writes. |
| Dimensions | Structures organizing cube data by time, organization, product, account, scenario, or other planning axes. | ERP master data, HR systems, CRM systems, and data warehouses. | Martini maintains explicit mappings, validates required Dimensions, and separates structural changes from value loads. |
| Elements | Members within Dimensions, such as departments, products, accounts, entities, scenarios, or periods. | ERP master data, Workday, Salesforce, and planning source systems. | Martini resolves names, keys, aliases, or captions according to the deployment contract, detects missing or inactive members, and applies controlled creation or rejection rules. |
| Cells | Individual cube intersections containing values that can be read or written through applicable API operations. | ERP actuals, CRM forecasts, workforce planning sources, reporting platforms, and warehouses. | Martini constructs dimensional coordinates, validates numeric or string values, applies idempotency and batch rules, and records request and response identifiers. |
| Integrator jobs | Jedox-managed data loading, transformation, and process execution for batch-oriented integration. | Files, external databases, enterprise applications, and Jedox Cubes. | Martini can orchestrate approved job invocations or coordinate surrounding API and file workflows while tracking execution status and exceptions. |
Authentication and security considerations
Authentication model
Jedox REST clients authenticate against the Jedox server and reuse the resulting authenticated session or token for subsequent requests. The exact flow should be verified for the deployed Jedox version and identity configuration.
Credential protection
- Use a dedicated least-privilege Jedox integration account.
- Store credentials, tokens, hostnames, and environment-specific settings in Martini secrets or protected configuration.
- Do not log passwords, authentication headers, or response tokens.
- Confirm TLS and certificate requirements for self-hosted deployments.
Authorization
Jedox permissions govern access to Databases, Cubes, Dimensions, and other objects. Martini workflows should request only the permissions required for their integration responsibilities.
Operational considerations for Jedox integrations
Versioning and schemas
Jedox endpoint availability and request formats can vary by release and deployment model. Validate the target API reference, avoid undocumented fields, and keep endpoint settings configurable.
Volume and pagination
Confirm pagination behavior for metadata and list operations. Use bounded page sizes, checkpoints, chunked requests, or Jedox Integrator processing for large transfers, and avoid one request per Cell when a suitable batch operation exists.
Idempotency and reconciliation
Use stable source keys, periods, scenarios, and batch identifiers. Determine whether writes replace, append, or increment values, and reconcile source totals with Cube totals after each load.
Scheduling and retries
Because universal change notifications were not confirmed, use scheduled polling or process orchestration where appropriate. Retry only transient failures with bounded backoff and prevent overlapping runs.
Testing and monitoring
Test metadata changes, missing Elements, hierarchy changes, late corrections, partial failures, and version-specific responses. Monitor workflow logs and preserve request, response, source batch, and Jedox identifiers without exposing sensitive planning data.
Why use Martini instead of scripts or point-to-point integrations?
Reusable orchestration
Martini coordinates authentication, REST calls, scheduled triggers, Jedox Integrator processes, transformations, validations, target writes, and reconciliation in maintainable workflows rather than isolated scripts.
Stable enterprise contracts
Martini can expose APIs that hide Jedox-specific endpoint details from consuming applications. This allows downstream systems to use a controlled contract while the Jedox implementation evolves behind it.
Reliable data processing
Workflows can apply explicit mappings for Dimensions, Elements, Cubes, and Cells; enforce business rules; checkpoint large loads; isolate rejected data; and retry transient failures without duplicating successful writes.
Operational visibility
Centralized workflow logic provides a consistent place to manage protected configuration, run identifiers, error paths, monitoring, and deployment changes across Jedox environments and connected applications.
Frequently asked questions
Jedox can be integrated primarily through its REST APIs for authentication, metadata, Databases, Cubes, Dimensions, Elements, and supported data operations. Jedox Integrator also supports scheduled, batch-oriented loading, transformation, and file-based exchanges. Because general-purpose webhooks for all Jedox data changes were not confirmed, scheduled polling or external orchestration may be required.
Yes. Martini can integrate with Jedox by consuming its REST APIs, orchestrating scheduled or API-triggered workflows, coordinating approved Integrator processes, transforming multidimensional data, and exposing controlled APIs for downstream or upstream applications.
No. A dedicated Jedox connector is not required. Martini can use Jedox's confirmed native integration mechanisms, primarily REST APIs, authentication sessions or tokens, scheduled processing, approved Integrator jobs, and file-based exchanges where applicable.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Jedox. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Jedox, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.
REST APIs should be treated as the primary integration method for authentication, metadata, Databases, Cubes, Dimensions, Elements, and data operations. Jedox Integrator is relevant for batch loading, transformation, and file-oriented processes. Current GraphQL and SOAP APIs were not confirmed for new Jedox integrations.
A general-purpose Jedox webhook model covering every Cube, Cell, Dimension, or Element change was not confirmed. Event-driven behavior may therefore require scheduled polling, a Jedox Integrator process, external orchestration, or a Martini API invoked by an approved process.
Martini can use scheduled or manually initiated workflows to retrieve scoped or incremental data where a supported watermark exists. It maps Jedox Dimensions, Elements, Cubes, and Cells into canonical or target models, validates periods and identifiers, applies business rules, and records checkpoints and batch identifiers for reconciliation.
Martini can distinguish authentication, authorization, validation, throttling, transient network, and server failures. Workflows can retry transient failures with bounded backoff, isolate rejected rows, use stable source and batch identifiers for idempotency, and reconcile source totals with Jedox results. Exact retry behavior should reflect the deployed API operations.
Yes. Martini can expose a REST API that invokes a workflow, calls Jedox, applies validation and transformation, and returns a stable enterprise-facing contract. This can hide Jedox-specific endpoint details from consuming applications while allowing the implementation behind the API to evolve.
Related Martini documentation
Workflows
Data
Plan your Jedox integration with Martini
Use Martini to connect Jedox REST APIs and Integrator-based processes with enterprise applications through secure, observable workflows, reusable mappings, and controlled APIs.