.png)
OneStream Integration Guide
Connect OneStream financial models, workflows, and data-management processes with enterprise systems through REST APIs, batch loads, files, and scheduled Martini workflows.
OneStream integration options at a glance
OneStream integrations primarily use REST APIs, data-management processes, financial-data loads, and file-based imports or exports. Exact endpoints, authentication requirements, asynchronous job behavior, and supported formats depend on the platform release, licensed modules, API gateway, and deployment model. General-purpose webhooks and GraphQL APIs were not confirmed, so event-like integrations should use scheduled polling or approved exports where necessary. Martini can authenticate against the customer’s OneStream environment, retrieve or submit data, transform dimensional payloads and files, invoke supported batch operations, poll processing status, validate business rules, and expose REST APIs for upstream applications.
| Integration point | Supported by OneStream? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Interact with OneStream applications, metadata, financial data, workflow-related operations, and data-management processes where enabled by the deployment. | Martini can consume OneStream REST endpoints, map request and response payloads, apply validation and business rules, and expose separate REST APIs for downstream systems. |
| Bulk, asynchronous, and batch processing | Limited | Submit or monitor financial-data loads, Data Management sequences, validations, consolidations, and other batch-oriented operations. | Martini can invoke supported batch operations, persist correlation or batch identifiers, poll status where available, and distinguish submission from business-process completion. |
| File import and export | Limited | Load or export structured financial data through Data Management, transformation rules, workflow profiles, or approved repositories. | Martini can generate, transform, validate, transmit, and archive files when the OneStream environment exposes a supported API, file location, or transfer mechanism. |
| Webhooks and outbound callbacks | Limited | Specific callback or notification capabilities may exist in some releases or deployments, but no general-purpose event framework covering OneStream operations was confirmed. | Martini can receive a verified callback or, where none exists, use scheduled workflows to poll supported endpoints or process approved exports. |
| Authentication | Limited | Authentication may use OAuth 2.0, API credentials, or service-account mechanisms depending on the API gateway, release, tenant, and deployment model. | Martini can use configured API authentication and secrets, keep credentials outside workflow source, and apply environment-specific security configuration. |
| GraphQL APIs | Not confirmed | No official OneStream GraphQL API was confirmed; a customer-specific API façade would need separate verification. | Martini can consume GraphQL when a separately deployed and authorized façade exists, but this is not assumed for OneStream. |
| SOAP APIs | Not confirmed | Older or customer-specific web services may exist, but a current generally recommended OneStream SOAP surface was not confirmed. | Martini can consume a verified SOAP service if the customer requires it, while new designs should first evaluate the supported REST API. |
| Database access | Not confirmed | Direct access to OneStream’s internal application database is not treated as a supported integration contract. | Martini can connect to an approved external database or warehouse, but should use OneStream APIs, exports, or reporting interfaces for OneStream data. |
How OneStream exposes data and business events
OneStream REST APIs
REST is the primary OneStream integration mechanism to investigate. Platform and application APIs may support metadata, financial data, workflow-related operations, and Data Management processes, subject to release, licensing, and deployment configuration.
Martini implementation pattern
Martini implementation pattern: Martini authenticates to the customer’s configured OneStream API service, retrieves or submits the required resource, transforms the payload, applies dimensional and business validation, and records the response and processing identifiers.
Implementation sequence
OneStream batch processing
OneStream is designed for batch-oriented financial loads, Data Management sequences, validations, consolidations, and workflow processing. Exact asynchronous behavior and job-status endpoints must be confirmed for the deployed version.
Martini implementation pattern
Martini implementation pattern: Martini submits a supported batch or Data Management operation, persists a deterministic load key and correlation identifier, polls status where supported, and routes business failures separately from transport failures.
Implementation sequence
OneStream file imports and exports
File-oriented loading and export scenarios are relevant for structured financial data, transformation rules, validation, and loading into a cube or workflow profile. Formats, repositories, and upload interfaces vary by deployment.
Martini implementation pattern
Martini implementation pattern: Martini receives or creates the source file, converts it to the approved OneStream structure, validates headers and dimensional values, transfers it through the supported mechanism, and monitors the resulting process.
Implementation sequence
Scheduled OneStream synchronization
A general-purpose OneStream webhook framework was not confirmed. Scheduled synchronization is therefore an appropriate fallback for polling supported APIs or processing approved exports when outbound notifications are unavailable.
Martini implementation pattern
Martini implementation pattern: a scheduler starts the workflow, Martini retrieves changes or an export for the defined scope, applies incremental and duplicate controls, and records the checkpoint and reconciliation outcome.
Implementation sequence
Common OneStream integration patterns
Pattern 1: Load ERP actuals into OneStream
When to use this pattern
Use this pattern when approved actuals from an ERP must be loaded into OneStream for consolidation, close, or reporting. It is suitable for periodic batch processing where account, entity, currency, scenario, and period mappings must be controlled.
Integration direction
Example Mapping
| OneStream Field | Canonical Field | Target Field |
|---|---|---|
| GeneralLedgerAccount | accountCode | Account member |
| CompanyCode | entityCode | Entity member |
| FiscalPeriod | period | Time member |
| LedgerAmount | amount | Data Unit value |
Martini implementation pattern
A scheduled Martini workflow retrieves approved ERP actuals, applies account and entity cross-references, validates fiscal calendars, currencies, signs, and balancing totals, then submits a supported OneStream API or file-based Data Management load. The workflow persists a deterministic source batch key, polls processing status where possible, and routes rejected rows separately from transport failures.
Martini capabilities used
- scheduled workflows
- API consumption
- file processing
- data mapping
- business rules
- validation
- error handling
Pattern 2: Publish OneStream planning data to a warehouse
When to use this pattern
Use this pattern to make planning, forecast, or consolidation results available for enterprise analytics while preserving OneStream dimensional context and reconciliation totals.
Integration direction
Example Mapping
| OneStream Field | Canonical Field | Target Field |
|---|---|---|
| Member | dimensionMember | member_key |
| Scenario | scenarioCode | scenario_code |
| Time | periodCode | period_code |
| Data Unit value | amount | amount |
Martini implementation pattern
Martini retrieves approved OneStream data or processes an approved export, normalizes dimensional coordinates, preserves source keys, and loads Snowflake in controlled batches. It can filter by scenario, period, workflow profile, or load timestamp and compares source and target totals before marking the extraction complete.
Martini capabilities used
- API consumption
- workflow orchestration
- data mapping
- JSON handling
- file processing
- reconciliation
- error handling
Pattern 3: Orchestrate workflow submissions
When to use this pattern
Use this pattern when an upstream planning or business application needs a controlled API for submitting OneStream data or requesting a workflow or Data Management operation.
Integration direction
Example Mapping
| OneStream Field | Canonical Field | Target Field |
|---|---|---|
| Entity | entityCode | Entity member |
| Account | accountCode | Account member |
| Scenario | scenarioCode | Scenario member |
| SubmissionId | correlationId | OneStream process reference |
Martini implementation pattern
Martini exposes a secured REST API that validates the incoming entity, account, scenario, and period context, applies authorization and duplicate-submission rules, invokes the appropriate OneStream operation, and returns a correlation identifier. A follow-up workflow polls status where supported and reports business-process failures distinctly from HTTP or transport errors.
Martini capabilities used
- API exposure
- authentication and authorization
- workflows
- data mapping
- business rules
- asynchronous orchestration
- error handling
Pattern 4: Synchronize finance master data
When to use this pattern
Use this pattern when approved organizational, account, or other master-data structures must be synchronized into OneStream dimensions and members.
Integration direction
Example Mapping
| OneStream Field | Canonical Field | Target Field |
|---|---|---|
| SourceAccount | accountCode | Account member |
| CompanyCode | entityCode | Entity member |
| ParentAccount | parentMember | Dimension hierarchy parent |
| EffectiveFrom | effectiveDate | Metadata validity rule |
Martini implementation pattern
Martini retrieves approved source structures, detects additions and changes, validates member-name uniqueness and parent-child relationships, and submits updates through supported OneStream APIs or controlled metadata-load processes. Structural changes can be held for approval, while failed mappings and hierarchy violations are reported without applying partial unsafe updates.
Martini capabilities used
- scheduled workflows
- API consumption
- data mapping
- business rules
- validation
- conditional routing
- error handling
Applications commonly integrated with OneStream
OneStream commonly participates in enterprise finance, planning, consolidation, and analytics architectures. The following applications represent practical integration targets and sources; the exact OneStream API, file, export, or warehouse path should be confirmed for the customer’s deployment.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Transfer general-ledger actuals, cost-center data, company-code balances, and master data into OneStream for consolidation and reporting. | SAP S/4HANA → Martini → OneStream | Martini retrieves approved SAP financial data, maps accounts and organizational values to OneStream members, validates dimensional completeness, submits a supported API or file-based load, and records processing status. |
| Oracle ERP Cloud | Load ledger, account, entity, currency, and period data into OneStream for close, consolidation, and planning. | Oracle ERP Cloud → Martini → OneStream | A scheduled Martini workflow extracts approved Oracle data, applies cross-reference and period rules, generates the required OneStream payload or file, invokes the supported data-management process, and reconciles totals. |
| NetSuite | Consolidate subsidiary financial data and synchronize accounts, entities, currencies, and periods with OneStream. | NetSuite → Martini → OneStream | Martini retrieves NetSuite financial and master data, normalizes currencies and fiscal periods, maps values to OneStream dimensions, prevents duplicate loads with a source batch key, and monitors completion. |
| Workday | Combine workforce plans, organizational structures, and workforce-related financial drivers with OneStream planning models. | Workday → Martini → OneStream | Martini consumes approved Workday data through the available tenant interface, validates organization and effective-date mappings, transforms the result into OneStream-compatible structures, and routes rejected mappings for review. |
| Salesforce | Use pipeline, bookings, customer, or revenue-driver data in OneStream planning and forecasting models. | Salesforce → Martini → OneStream | Martini retrieves selected Salesforce business data on a schedule or through an approved trigger, enriches it with finance mappings, validates scenario and period context, and submits a controlled OneStream load. |
| Snowflake | Publish OneStream actuals, forecasts, and consolidated results for enterprise analytics and downstream reporting. | OneStream → Martini → Snowflake | Martini extracts approved OneStream data or exports, preserves dimensional keys, normalizes the analytical model, loads Snowflake in batches, and performs reconciliation checks against source totals. |
| Microsoft Power BI | Make OneStream financial and planning data available for reporting through an approved warehouse, export, or semantic-model architecture. | OneStream → Martini → Microsoft Power BI | Martini retrieves approved OneStream outputs, publishes them to an analytical store or supported reporting layer, and applies refresh, completeness, and reconciliation controls before Power BI consumption. |
| Azure Data Factory | Coordinate file or API movement between enterprise systems and OneStream-related data stores. | Azure Data Factory → Martini → OneStream | Martini owns the transformation, validation, OneStream submission, and status workflow while Azure Data Factory may provide adjacent data movement or scheduling according to the target architecture. |
How to build a OneStream integration in Martini
Objective
Establish the OneStream connection using the authentication method supported by the target release, API gateway, and deployment model.
Instructions in Martini
- Confirm the OneStream version, deployment model, API base URL, and enabled services.
- Use a dedicated service account or client where supported.
- Store tokens, client secrets, and credentials in Martini secrets or environment configuration.
- Confirm application, cube, workflow, Data Management, and metadata permissions.
Objective
Select an integration trigger that reflects OneStream’s available mechanisms and the required business cadence.
Instructions in Martini
- Use a scheduled workflow for polling or periodic financial loads when no suitable outbound event exists.
- Expose a Martini REST API for upstream submission requests.
- Use a verified callback only when the customer’s OneStream release explicitly supports it.
- Define the extraction scope, load period, scenario, workflow profile, or source batch boundary.
Objective
Obtain OneStream data, source-system data, approved exports, or structured files through supported endpoints and transfer mechanisms.
Instructions in Martini
- Retrieve resources through the supported OneStream REST API or receive an approved input file.
- Prefer batch, export, or Data Management operations for larger volumes.
- Capture pagination, filtering, process identifiers, and source-file metadata.
- Persist checkpoints and source batch identifiers for repeatable processing.
Objective
Coordinate API calls, file operations, status checks, validation, and target writes in a maintainable Martini workflow.
Instructions in Martini
- Separate submission from asynchronous process completion.
- Use conditional routing for accepted, rejected, pending, and failed outcomes.
- Poll status only within bounded retry and timeout policies.
- Keep transport errors separate from OneStream business-validation errors.
Objective
Convert source financial and operational structures into OneStream’s dimensional model or normalize OneStream outputs for downstream systems.
Instructions in Martini
- Map Account, Entity, Scenario, Time, Flow, and other required dimensions explicitly.
- Validate member existence, hierarchy relationships, fiscal periods, currencies, signs, and precision.
- Transform JSON, structured files, and export formats as required by the target operation.
- Preserve source identifiers and OneStream processing references.
Objective
Protect financial integrity by applying duplicate, authorization, balancing, and reconciliation controls before and after processing.
Instructions in Martini
- Use deterministic load keys based on source, cube, workflow, scenario, entity, period, and batch identifiers.
- Reject incomplete or unauthorized dimensional combinations before submission.
- Compare source totals with OneStream or warehouse totals after processing.
- Route unmapped members, rejected rows, and reconciliation differences for review.
Common OneStream data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Application | Contains the OneStream financial model, metadata, workflows, and security configuration. | Enterprise planning systems, data warehouses, governance stores | Martini can retrieve application-related information through supported APIs and use it to parameterize mappings, validation, and routing. |
| Cube | Stores and analyzes multidimensional financial or operational data. | ERP systems, data warehouses, reporting platforms | Martini uses supported REST, export, or Data Management operations to submit or extract cube data without relying on internal database tables. |
| Dimension | Defines structural axes such as Account, Entity, Scenario, Time, or Flow. | ERP master data, planning applications, analytics stores | Martini maintains cross-reference mappings, validates dimension values, and applies approved metadata-load processes where available. |
| Member | Represents an individual value within a dimension, such as an account, entity, or scenario. | ERP master data, finance systems, reporting models | Martini validates member existence, maps source values, checks hierarchy rules, and rejects unmapped or unauthorized members before loading. |
| Workflow Profile | Provides the workflow and submission context for data loading, validation, certification, and approval. | Planning applications, finance workflow systems, operational approval processes | Martini selects and validates the target workflow context, submits data or actions, and records resulting status and correlation identifiers. |
| Data Unit | Represents a dimensional slice of data used in consolidation and workflow processing. | ERP systems, data warehouses, reconciliation platforms | Martini preserves dimensional coordinates, applies period and currency rules, submits batches, and reconciles source and OneStream totals. |
Authentication and security considerations
Authentication depends on the deployment
OneStream authentication should be confirmed against the tenant’s release, API gateway, and hosting model. OAuth 2.0, API credentials, and service-account mechanisms may be available, but grant types, token endpoints, scopes, and client requirements must be verified.
Use controlled identities and secrets
- Use dedicated service accounts or clients for scheduled and server-to-server Martini workflows.
- Grant only the application, cube, workflow, Data Management, and metadata permissions required by the integration.
- Store client secrets, tokens, and credentials in Martini secrets or environment configuration rather than workflow source.
- Use TLS and avoid writing financial payloads or authentication material to logs.
Operational considerations for OneStream integrations
Plan for financial-process behavior
- Confirm pagination, filtering, maximum page sizes, and tenant-specific rate or concurrency limits.
- Prefer batch, file, export, or Data Management operations for large cube extracts and loads.
- Persist correlation identifiers and poll asynchronous process status where supported.
- Use deterministic batch keys and checkpoints to prevent duplicate submissions.
- Maintain explicit mappings for Account, Entity, Scenario, Time, Flow, and other dimensions.
- Validate fiscal calendars, currencies, signs, precision, hierarchies, and balancing totals.
- Separate transport retries from business-process retries and use bounded exponential backoff.
- Monitor schema, metadata, workflow-profile, and member changes with contract tests and reconciliation checks.
Why use Martini instead of scripts or point-to-point integrations?
Centralize integration logic
Martini provides a maintainable workflow layer for OneStream integrations instead of scattering authentication, mappings, batch submission, polling, and error handling across scripts or point-to-point interfaces.
Support controlled financial automation
- Consume OneStream REST APIs and invoke supported processing operations.
- Transform files and dimensional payloads between ERP, planning, warehouse, and reporting models.
- Expose stable REST APIs for upstream applications that need to submit data or request processing.
- Apply reusable validation, business rules, idempotency, reconciliation, and retry behavior.
- Use schedules, orchestration, monitoring, and environment-specific secrets for operational reliability.
Frequently asked questions
OneStream can be integrated primarily through its supported REST APIs, Data Management and batch processes, and file-based financial-data imports or exports. The exact endpoints, formats, authentication, and asynchronous behavior depend on the platform release, licensed modules, API gateway, and deployment model. Scheduled polling may be required where a general-purpose webhook framework is unavailable.
Yes. Martini can integrate with OneStream by consuming supported REST APIs, invoking available Data Management or batch operations, processing approved files and exports, transforming dimensional data, and exposing REST APIs for upstream systems. A specific OneStream capability should be confirmed against the customer’s release and tenant configuration.
No. A dedicated OneStream connector is not required. Martini can use OneStream’s confirmed native integration mechanisms, including supported REST APIs, batch or Data Management operations, files, exports, and the authentication methods configured for the customer’s deployment.
Lonti does not charge an additional per-connector or per-vendor fee to integrate OneStream. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from OneStream, cloud infrastructure, or other third-party systems depending on subscription, usage, licensing, and deployment model.
REST APIs should generally be evaluated first for supported platform, application, metadata, workflow, and financial-data operations. For larger loads, Data Management, batch processing, or approved file imports and exports are usually more appropriate than one request per financial value. SOAP and GraphQL should not be assumed because current generally recommended OneStream surfaces were not confirmed.
A general-purpose OneStream webhook framework covering data, workflow, consolidation, and metadata events was not confirmed. A specific callback may exist in a particular release or deployment and must be verified. Otherwise, Martini can use scheduled workflows to poll supported endpoints or process approved exports.
Martini can run scheduled or API-led synchronization using scopes such as scenario, period, workflow profile, load timestamp, or source batch. Deterministic load keys, persisted checkpoints, prior-status checks, dimensional validation, and reconciliation totals help prevent duplicate financial loads and make retries safe.
Yes. Martini can expose a secured REST API that accepts data or process requests, validates Account, Entity, Scenario, Time, and other required dimensions, orchestrates supported OneStream calls, and returns synchronous or asynchronous status information. This can provide a stable interface while OneStream-specific endpoint details remain inside the workflow.
Related Martini documentation
Workflows
Data
Connect OneStream with Martini
Use Martini to build governed OneStream integrations for financial data loads, planning synchronization, workflow orchestration, and enterprise reporting.