.png)
Oracle Aconex Integration Guide
Connect Oracle Aconex project documents, correspondence, users, and workflows with enterprise systems through REST APIs, OAuth, scheduled workflows, and selected event notifications.
Oracle Aconex integration options at a glance
Oracle Aconex integrations primarily use documented REST APIs protected by Oracle/Aconex application registration and OAuth-based authorization. Depending on the tenant, enabled modules, and project permissions, these APIs can expose Projects, Documents, Mail, Users, Workflows, Packages, metadata, and selected file operations. Aconex may provide notification or callback capabilities for selected collaboration activities, but broad event coverage should be confirmed. Where events are unavailable, Martini can run scheduled workflows using modified-date, version, status, or change filters. Martini can paginate, batch, map, validate, checkpoint, and retry API exchanges while storing OAuth credentials and tokens in environment secrets.
| Integration point | Supported by Oracle Aconex? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Read Projects, Documents, Mail, Users, Workflows, Packages, metadata, and selected update operations. File transfers may be available for supported resources. | Martini can consume authenticated REST endpoints, paginate responses, transform JSON, apply rules, and expose reusable APIs or workflows. |
| Webhooks / outbound callbacks | Limited | Aconex may provide notifications or callbacks for selected collaboration activities, but coverage across all objects and events is not confirmed. | Martini can expose an API endpoint or receive webhook-style events when the target tenant supports the required callback mechanism; otherwise it can use polling. |
| File / attachment APIs | Yes | Documents and Mail may include binary files, attachments, metadata, revisions, and versions. Exact operations depend on the resource and tenant. | Martini can handle JSON and multipart exchanges, map metadata, transfer bounded files, and preserve parent-object and version identifiers. |
| Bulk / async / batch APIs | Limited | Aconex supports project-scale information exchange, but resource-specific bulk or asynchronous operations require confirmation for the selected API. | Martini can batch work, checkpoint progress, paginate collections, and avoid unbounded single-record loops. |
| Authentication | Yes | API access uses Oracle/Aconex application registration and OAuth-based authorization where enabled, with tenant approval and project permissions. | Martini can use configured OAuth authentication and store client credentials, secrets, refresh tokens, and access tokens in environment secrets. |
| Scheduled synchronization | Yes | Scheduled polling can retrieve changed Documents, Mail, Users, Projects, or other supported resources when event delivery is unavailable. | Martini scheduler-triggered workflows can use timestamps, versions, statuses, filters, durable checkpoints, and bounded retries. |
| SDKs | Not confirmed | No specific official SDK was confirmed as required. HTTP-based REST access is the expected implementation approach. | Martini can call APIs directly without depending on an unconfirmed vendor SDK. |
| Database access | No | Direct access to Oracle-managed Aconex production data is not an expected integration method. | Martini should use supported Aconex APIs, files, and notifications rather than direct database connectivity. |
How Oracle Aconex exposes data and business events
Oracle Aconex REST APIs
Oracle Aconex provides documented REST APIs for selected project and collaboration resources. Availability, operations, and fields depend on the tenant, enabled modules, project permissions, and current API program.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates with the configured OAuth strategy, calls the relevant Aconex resource, follows pagination, maps and validates the response, applies business rules, writes to the target system, and stores a checkpoint after successful processing.
Implementation sequence
Aconex file and attachment APIs
Aconex Documents and Mail can contain files or attachments, with resource-specific operations for metadata and binary transfer subject to tenant permissions and API availability.
Martini implementation pattern
Martini implementation pattern: retrieve the parent object and file metadata, transfer the binary in bounded stages where supported, validate content and identifiers, and write the file or reference to the target while preserving version information.
Implementation sequence
Aconex callbacks and notifications
Aconex may provide event or notification capabilities for selected collaboration activities, but broad coverage for every Document, Mail, Workflow, or User change is not confirmed.
Martini implementation pattern
Martini implementation pattern: expose a secured API endpoint when the tenant supports the required callback, validate the notification, retrieve the current Aconex resource, and process it idempotently. Scheduled polling remains the fallback for uncovered events.
Implementation sequence
Scheduled Aconex synchronization
Scheduled polling is appropriate when the required Aconex event is unavailable. Modified dates, versions, status values, or change identifiers can narrow the synchronization scope where supported.
Martini implementation pattern
Martini implementation pattern: a scheduler starts a workflow, obtains the next checkpoint, retrieves changed resources page by page, processes each item with idempotency controls, and advances the checkpoint only after downstream success.
Implementation sequence
Common Oracle Aconex integration patterns
Pattern 1: Synchronize Aconex Documents to a repository
When to use this pattern
Use this pattern when project teams need selected Aconex document metadata or files available in another repository or project system. It supports incremental synchronization while distinguishing logical documents, revisions, versions, and binaries.
Integration direction
Example Mapping
| Oracle Aconex Field | Canonical Field | Target Field |
|---|---|---|
| Document ID | sourceDocumentId | External ID |
| Revision or version | documentVersion | Version |
| Status | documentStatus | Approval Status |
| Project ID | projectId | Project Reference |
Martini implementation pattern
A scheduled workflow retrieves changed Documents using supported filters, follows pagination, validates project scope, maps metadata, and transfers supported files in bounded stages. It uses Document and version identifiers for idempotency, updates the checkpoint only after the target write succeeds, and routes throttling or temporary failures to bounded retry handling.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- file handling
- business rules
- error handling
Pattern 2: Synchronize Aconex Mail and attachments
When to use this pattern
Use this pattern when formal Aconex correspondence must be represented in ServiceNow, Salesforce, or another records-management application without losing Mail, recipient, response, attachment, and document-reference context.
Integration direction
Example Mapping
| Oracle Aconex Field | Canonical Field | Target Field |
|---|---|---|
| Mail ID | sourceCorrespondenceId | External Reference |
| Subject | correspondenceSubject | Short Description |
| Sender and recipients | participants | Caller and Watch List |
| Attachments | files | Attachments |
Martini implementation pattern
Martini polls or receives supported Mail notifications, retrieves the current Mail and attachments, validates project and Mail-type rules, and maps the correspondence into ServiceNow. The Mail ID is used as an idempotency key; attachment failures are isolated and retried without recreating the parent correspondence.
Martini capabilities used
- workflows
- API consumption
- mapping
- validation
- idempotency
- file handling
- retry handling
Pattern 3: Return an external approval to Aconex
When to use this pattern
Use this pattern when an external application submits an approval or project update that must be reflected in an Aconex document, workflow-related status, or supported project resource.
Integration direction
Example Mapping
| Oracle Aconex Field | Canonical Field | Target Field |
|---|---|---|
| External approval ID | approvalId | Aconex Correlation Reference |
| Approval status | approvalStatus | Supported Status Field |
| Document reference | documentId | Document ID |
| Decision timestamp | decisionAt | Status Date |
Martini implementation pattern
Martini exposes a secured REST API, validates the incoming approval and source identifiers, checks that the requested Aconex operation is supported, applies project and status rules, and calls the authenticated Aconex API. It records the response and prevents duplicate writes using the external approval ID.
Martini capabilities used
- API exposure
- authentication
- validation
- business rules
- API consumption
- data mapping
- error handling
Pattern 4: Synchronize Aconex Projects and Users
When to use this pattern
Use this pattern when project-management, reporting, or access-governance processes need current Aconex Projects, Users, organizations, and project associations.
Integration direction
Example Mapping
| Oracle Aconex Field | Canonical Field | Target Field |
|---|---|---|
| Project ID | projectId | Project Code |
| Project status | projectStatus | Status |
| User ID | userId | External User ID |
| Organization | organizationName | Company |
Martini implementation pattern
A scheduled Martini workflow retrieves permitted Projects and Users, applies active-project and user-status rules, maps project associations, and writes changes to the target system. It stores checkpoints, flags unmatched users for review, and retries only transient API or downstream failures.
Martini capabilities used
- scheduling
- API consumption
- data mapping
- business rules
- checkpointing
- exception handling
Applications commonly integrated with Oracle Aconex
Oracle Aconex can be integrated with adjacent project, enterprise, finance, document, and service-management applications. The exact object-level flows depend on the Aconex tenant, enabled modules, permissions, and currently supported API operations.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Oracle Primavera Cloud | Align project structures, schedules, activities, and delivery information with Aconex collaboration data. | Oracle Primavera Cloud → Martini → Oracle Aconex | Martini retrieves or receives approved project and schedule context, maps identifiers and status values, validates project membership, and calls supported Aconex APIs. It can also return selected document or delivery metadata when the target Aconex operation is enabled. |
| Oracle Primavera P6 | Exchange schedule and activity context with Aconex for construction delivery and reporting. | Oracle Primavera P6 → Martini → Oracle Aconex | A scheduled or API-led workflow retrieves changed schedule data, maps projects and activities to Aconex context, applies project-specific rules, and records source and target identifiers. Unsupported write operations are routed to an exception process. |
| Oracle Primavera Unifier | Connect cost, funding, business-process, and project-control information with Aconex documents and correspondence. | Oracle Primavera Unifier → Martini → Oracle Aconex | Martini orchestrates calls to both systems, normalizes project and commercial identifiers, applies approval rules, and transfers supported document, Mail, or metadata references with retry and audit handling. |
| Oracle NetSuite | Associate Aconex project documents and correspondence with finance, vendor, and business-management processes. | Oracle Aconex → Martini → Oracle NetSuite | Martini polls or receives eligible Aconex changes, maps project, document, Mail, and supplier references into NetSuite payloads, checks idempotency keys, and records downstream response identifiers. |
| Salesforce | Link customer, account, opportunity, or program information with project documents and correspondence. | Salesforce → Martini → Oracle Aconex | An API-led Martini workflow accepts project context from Salesforce, validates the Aconex project scope, maps fields and references, and invokes supported Aconex REST operations. Selected Aconex status can be synchronized back to Salesforce. |
| SAP S/4HANA | Connect procurement, supplier, finance, and project-control processes with construction documentation and approvals. | SAP S/4HANA → Martini → Oracle Aconex | Martini transforms SAP master and commercial context into Aconex-compatible requests, separates metadata from binary documents, applies authorization and validation rules, and retries only transient failures. |
| ServiceNow | Route project-related issues, requests, or correspondence into service-management workflows while retaining Aconex references. | Oracle Aconex → Martini → ServiceNow | Martini polls supported Aconex Mail or document changes, maps them to ServiceNow records, preserves Aconex identifiers and attachments, and can expose an API for approved ServiceNow updates to Aconex. |
| Microsoft SharePoint | Publish selected project document metadata or approved files outside Aconex when business processes require it. | Oracle Aconex → Martini → Microsoft SharePoint | A Martini workflow retrieves eligible Aconex Documents and files, validates project and document status, transforms metadata, transfers bounded file payloads, and stores source-to-target relationships. |
How to build a Oracle Aconex integration in Martini
Objective
Establish the Aconex application registration, tenant approval, project permissions, and OAuth configuration required for the integration.
Instructions in Martini
- Confirm the target tenant, API resources, scopes, and project memberships.
- Store OAuth client credentials, secrets, and refresh configuration in Martini environment secrets.
- Test access using the same project permissions intended for production.
Objective
Select an event-driven or scheduled initiation method based on the actual Aconex resource coverage available in the tenant.
Instructions in Martini
- Use a supported callback or notification when the required event is confirmed.
- Use a scheduler for polling when event coverage is unavailable or incomplete.
- Define the synchronization interval and checkpoint strategy.
Objective
Request Aconex resources and related files while respecting pagination, project scope, permissions, and API limits.
Instructions in Martini
- Retrieve Projects, Documents, Mail, Users, Workflows, or Packages through supported REST operations.
- Follow pagination until the collection is complete.
- Retrieve file metadata and binaries only when required by the target process.
Objective
Coordinate the end-to-end Martini workflow from source retrieval through target write and checkpoint persistence.
Instructions in Martini
- Separate authentication, retrieval, transformation, target writing, and checkpoint stages.
- Use correlation identifiers for each execution and source object.
- Route authorization, validation, throttling, and downstream failures to appropriate handling paths.
Objective
Convert Aconex structures and project-specific metadata into a canonical model and target payload.
Instructions in Martini
- Map stable Aconex identifiers, versions, statuses, participants, dates, and references.
- Treat optional project-specific fields as nullable and validate required target fields.
- Apply project, document-status, Mail-type, and attachment rules before writing.
Objective
Create or update the target application without duplicating correspondence, documents, users, or project associations.
Instructions in Martini
- Use source IDs and version identifiers as idempotency keys.
- Write metadata and binary content in bounded stages where appropriate.
- Persist source-to-target identifiers and response status after successful writes.
Common Oracle Aconex data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Projects | Defines the collaboration scope for documents, Mail, users, workflows, and project information. | Oracle Primavera Cloud, Oracle Primavera P6, Oracle Primavera Unifier, SAP S/4HANA | Martini uses project identifiers and permissions to scope requests, validate membership, and correlate downstream records. |
| Documents | Represents project files with metadata, revisions, versions, attributes, and status. | Microsoft SharePoint, SAP S/4HANA, Oracle Primavera Cloud, Salesforce | Martini retrieves changed metadata or supported binaries, distinguishes logical documents from versions, maps fields, and checkpoints successful transfers. |
| Formal project correspondence containing recipients, subjects, content, responses, attachments, and document references. | ServiceNow, Salesforce, Microsoft SharePoint, records-management applications | Martini preserves Mail IDs as idempotency keys, maps correspondence fields, handles attachments separately, and records source references. | |
| Users | People and organizations participating in Aconex projects. | Oracle Primavera Unifier, Salesforce, SAP S/4HANA, identity administration applications | Martini synchronizes permitted user and organization attributes, applies active-status rules, and produces exceptions for unmatched downstream accounts. |
| Workflows | Controlled review, approval, and distribution processes with steps, participants, statuses, actions, and dates. | Oracle Primavera Cloud, ServiceNow, SAP S/4HANA | Martini reads supported workflow information, maps statuses and participants, and only performs updates where the tenant API and permissions allow them. |
| Packages | Bundles project information for controlled distribution or exchange, potentially including documents or transmittals. | Microsoft SharePoint, Oracle Primavera Cloud, SAP S/4HANA | Martini retrieves supported package metadata and related references, validates project scope, and transfers selected content with audit identifiers. |
Authentication and security considerations
OAuth and application registration
Oracle Aconex API access is associated with application registration, tenant approval, OAuth-based authorization where enabled, and the permissions of the Aconex user or application context.
Least-privilege access
- Limit access to required projects, Documents, Mail, Users, Workflows, Packages, and operations.
- Confirm project membership and roles in a non-production project before deployment.
- Store client credentials, secrets, refresh tokens, and access tokens in Martini environment secrets.
- Never write access tokens or sensitive payloads to workflow logs.
Operational considerations for Oracle Aconex integrations
Reliability controls
- Respect pagination and do not rely on fixed page counts.
- Use bounded retries with exponential backoff for transient failures and honor Retry-After when provided.
- Monitor HTTP 429 responses and pace large-project requests.
- Use stable Aconex identifiers and version values for idempotency.
Data and change management
- Separate logical Documents, revisions, versions, metadata, binaries, Mail, and workflow references.
- Validate project-specific metadata and treat optional fields as nullable.
- Record API versions, endpoint configuration, source IDs, target IDs, timestamps, and workflow execution IDs.
- Test mapping and write operations in a non-production project before release.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond point-to-point calls
Martini combines Aconex API consumption, scheduled or event-driven triggers, transformations, validation, business rules, target-system writes, and checkpoint management in maintainable workflows.
Reusable and observable integration assets
Instead of maintaining isolated scripts, teams can expose controlled APIs, reuse authentication and mapping logic, handle files and attachments consistently, and centralize error handling, retries, correlation, and operational monitoring.
Adaptable implementation
Because Aconex resources, permissions, project metadata, and event coverage vary by tenant, Martini provides a flexible integration layer that can use REST APIs, callbacks where available, and scheduled polling where necessary.
Frequently asked questions
Oracle Aconex can be integrated primarily through its documented REST APIs, OAuth-based authorization, supported file and attachment operations, and selected notification or callback capabilities. Scheduled polling with filters and checkpoints can support synchronization where event coverage is unavailable.
Yes. Martini can consume Oracle Aconex REST APIs, authenticate through the tenant's approved OAuth configuration, orchestrate synchronization workflows, map project data, handle files, and expose an API for supported callback or update scenarios.
No. A dedicated Oracle Aconex connector is not required. Martini can use Aconex's confirmed native REST APIs, OAuth authentication, supported callbacks or notifications, file operations, and scheduled synchronization mechanisms.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Oracle Aconex. The integration is subject to the provisioned capacity of the Martini environment. Separate Oracle Aconex, infrastructure, or other third-party costs may apply based on subscriptions, usage, and deployment model.
REST APIs should be the primary approach for new integrations. File and attachment operations are relevant for Documents and Mail, while callbacks or notifications should be used only for confirmed tenant-supported events. GraphQL and current SOAP support were not confirmed.
Aconex may support notifications, callbacks, or event capabilities for selected collaboration activities, but broad coverage should not be assumed. Martini can receive a supported callback through an exposed API; otherwise, scheduled polling is the appropriate fallback.
Martini can use modified dates, versions, statuses, or change identifiers to retrieve incremental changes. Durable checkpoints should advance after successful target writes, while stable Project, Document, version, and Mail identifiers provide idempotency and correlation keys.
Yes. Martini can expose a REST API that validates incoming data, applies business rules, maps the request, and calls the appropriate Aconex REST operation when that operation is available and authorized. It can also return controlled responses and correlation identifiers to the caller.
Related Martini documentation
Workflows
Data handling
Connect Oracle Aconex with Martini
Use Martini to build secure, maintainable Oracle Aconex integrations for project data, documents, correspondence, workflows, and enterprise applications.