.png)
Autodesk Construction Cloud Integration Guide
Connect Autodesk Construction Cloud with enterprise systems through Autodesk Platform Services REST APIs, selected webhook events, OAuth 2.0, and Martini workflows.
Autodesk Construction Cloud integration options at a glance
Autodesk Construction Cloud integrations primarily use Autodesk Platform Services REST APIs for Projects, Issues, RFIs, Submittals, Assets, Forms, account administration, and related resources. APS OAuth 2.0 supports two-legged application access and three-legged user-authorized access. Selected Autodesk resources can emit webhook notifications, although coverage varies by resource and event. Data Management APIs support hubs, projects, folders, items, versions, and file-related operations. Martini can consume these APIs, expose endpoints for webhook callbacks, schedule paginated synchronization workflows, transform JSON payloads, and apply validation, idempotency, retry, and checkpointing controls.
| Integration point | Supported by Autodesk Construction Cloud? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | ACC APIs exposed through Autodesk Platform Services support Projects, Issues, RFIs, Submittals, Assets, Forms, Locations, account administration, and related construction resources. | Martini can consume APS REST endpoints, manage OAuth bearer tokens, pass account and project context, paginate responses, and map JSON request and response bodies. |
| Webhooks / outbound callbacks | Limited | APS Webhooks can notify applications about selected Autodesk resource events. Coverage depends on the resource, event, and subscription scope. | Martini can expose a REST API endpoint to receive notifications, validate and deduplicate them, then retrieve the current ACC resource before processing it. |
| File / attachment APIs | Yes | APS Data Management APIs provide access to hubs, projects, folders, items, versions, and file-related operations; business-object attachments may require separate resource APIs. | Martini can orchestrate metadata and file transfers, handle signed URLs, preserve identifiers and versions, and retry incomplete transfers. |
| Bulk / async / batch APIs | Limited | Some APS operations or resource families support specialized or asynchronous processing, but ACC has no universal bulk API for every business object. | Martini can implement controlled pagination, checkpointing, bounded concurrency, and resource-specific asynchronous handling without assuming a general bulk endpoint. |
| Authentication | Yes | APS uses OAuth 2.0 with two-legged application access and three-legged user-authorized access, scopes, client credentials, and short-lived bearer tokens. | Martini can store client secrets and token configuration securely, acquire or refresh tokens, and apply environment-specific account, project, and scope settings. |
| SDKs | Yes | Autodesk provides APS SDKs and examples for several API families and programming languages, while the underlying HTTP APIs remain the integration surface. | Martini can consume the HTTP APIs directly and use custom JVM-compatible logic where specialized payload handling or transformation is required. |
| GraphQL APIs | Not confirmed | No current public ACC GraphQL integration surface was identified in the reviewed Autodesk documentation. | Martini can consume GraphQL generally, but an ACC GraphQL endpoint should not be assumed for this integration. |
| SOAP APIs | No | ACC integrations are documented around Autodesk Platform Services REST APIs rather than SOAP services. | Martini should use the documented APS REST interfaces instead of treating SOAP as an ACC integration mechanism. |
| Database access | Not confirmed | No customer-facing direct relational database access for ACC transactional data was identified. | Martini should use Autodesk APIs and documented file or export mechanisms rather than a direct ACC database connection. |
How Autodesk Construction Cloud exposes data and business events
Autodesk Construction Cloud REST APIs
Autodesk Construction Cloud exposes its primary integration surface through Autodesk Platform Services REST APIs. These APIs cover construction resources such as Projects, Issues, RFIs, Submittals, Assets, Forms, Locations, account administration, and Data Management resources.
Martini implementation pattern
Martini implementation pattern: Martini obtains an OAuth 2.0 bearer token, calls the appropriate APS resource endpoint with account and project context, handles pagination and response validation, maps the JSON payload, and writes the result to the target system or exposes a controlled API response.
Implementation sequence
APS Webhooks
Autodesk Platform Services provides webhook notifications for selected Autodesk resource events. Coverage is resource- and event-specific, and a notification may contain an identifier or event reference rather than the complete changed object.
Martini implementation pattern
Martini implementation pattern: Martini exposes a REST endpoint for the callback, validates the notification and tenant or project context, deduplicates the event, retrieves the current ACC resource through REST, and sends the normalized object into the downstream workflow. Scheduled reconciliation supplements unsupported, expired, or missed notifications.
Implementation sequence
APS Data Management APIs
APS Data Management APIs provide access to Autodesk hubs, projects, folders, items, versions, and related document operations. ACC business objects and document files are separate models and may require different API calls.
Martini implementation pattern
Martini implementation pattern: Martini identifies eligible folders or items, compares item and version identifiers, obtains the required transfer URL, moves content to the target repository, and records source metadata for repeatable reconciliation.
Implementation sequence
Scheduled ACC synchronization
Scheduled synchronization is appropriate when a required ACC event is not supported or when periodic reconciliation is needed to detect missed webhook deliveries. REST list endpoints should be processed with pagination and documented incremental filters where available.
Martini implementation pattern
Martini implementation pattern: A scheduled workflow uses a persisted checkpoint and an overlap window, retrieves changed Projects, Issues, RFIs, or other selected resources, processes each page, applies idempotency checks, and advances the checkpoint only after successful target writes.
Implementation sequence
APS OAuth 2.0
APS uses OAuth 2.0. Two-legged OAuth supports application-level or server-to-server access, while three-legged OAuth supports user-authorized operations and user context. Scopes and Autodesk account or project permissions determine effective access.
Martini implementation pattern
Martini implementation pattern: Martini stores APS client credentials in secrets, requests tokens for the selected flow and scopes, applies the bearer token to API calls, and reacquires or refreshes tokens as required without embedding credentials in workflow definitions.
Implementation sequence
Common Autodesk Construction Cloud integration patterns
Pattern 1: Sync ACC Issues to ServiceNow
When to use this pattern
Use this pattern when construction Issues must become operational work items while retaining project, location, assignment, and source references. Webhooks can reduce latency for supported events, while scheduled reconciliation provides coverage for missed or unsupported notifications.
Integration direction
Example Mapping
| Autodesk Construction Cloud Field | Canonical Field | Target Field |
|---|---|---|
| Issue.id | sourceIssueId | u_acc_issue_id |
| Issue.title | title | short_description |
| Issue.description | description | description |
| Issue.status | status | state |
Martini implementation pattern
Martini receives a supported notification or retrieves changed Issues, fetches the current resource, validates project scope, maps assignment and priority rules, and upserts the ServiceNow work item. It stores the ACC Issue identifier, uses idempotent updates, and retries throttling or transient failures with bounded backoff.
Martini capabilities used
- workflows
- API consumption
- webhook consumption
- data mapping
- business rules
- error handling
Pattern 2: Synchronize ACC RFIs and Submittals with Salesforce
When to use this pattern
Use this pattern when project-delivery or customer-facing teams need RFI and Submittal visibility in Salesforce. The integration should define whether ACC or Salesforce owns status, due dates, participants, and project associations before enabling selected updates in both directions.
Integration direction
Example Mapping
| Autodesk Construction Cloud Field | Canonical Field | Target Field |
|---|---|---|
| RFI.id | sourceResourceId | ACC_RFI_ID__c |
| RFI.question | requestDescription | Description__c |
| RFI.status | reviewStatus | Status__c |
| Submittal.dueDate | dueDate | Due_Date__c |
Martini implementation pattern
Martini retrieves project-scoped RFIs and Submittals through APS REST APIs, normalizes dates and status values, links each record to a Salesforce project or account, and upserts using the ACC resource key. Validation failures are isolated for review, while transient API failures are retried without creating duplicates.
Martini capabilities used
- API consumption
- scheduled workflows
- data mapping
- validation
- idempotency
- retry handling
Pattern 3: Synchronize ACC project and cost information with NetSuite
When to use this pattern
Use this pattern when approved ACC project or cost-related information must be aligned with financial and operational records. Exact fields and resource availability depend on the ACC modules licensed and the APIs available in the target NetSuite environment.
Integration direction
Example Mapping
| Autodesk Construction Cloud Field | Canonical Field | Target Field |
|---|---|---|
| Project.id | projectId | externalid |
| Project.name | projectName | projectname |
| Cost Item.code | costCode | custbody_acc_cost_code |
| Project.status | projectStatus | status |
Martini implementation pattern
Martini retrieves approved ACC project and cost information, normalizes identifiers, applies financial ownership rules, and calls NetSuite APIs for controlled upserts. The workflow stores checkpoints for larger transfers, prevents duplicate financial records, and routes permission or validation conflicts separately from transient failures.
Martini capabilities used
- workflow orchestration
- API consumption
- data transformation
- business rules
- checkpointing
- error handling
Pattern 4: Copy ACC document versions to SharePoint
When to use this pattern
Use this pattern when selected ACC documents and metadata must be available in SharePoint for broader access, retention, or collaboration. It is appropriate for controlled folder and project allowlists rather than unrestricted replication.
Integration direction
Example Mapping
| Autodesk Construction Cloud Field | Canonical Field | Target Field |
|---|---|---|
| Item.id | sourceItemId | ACC_Source_Item_ID |
| Version.id | sourceVersionId | ACC_Source_Version_ID |
| Item.name | fileName | Name |
| Version.createdTime | sourceModifiedTime | Modified |
Martini implementation pattern
Martini uses APS Data Management APIs to enumerate approved folders, compare item and version identifiers, obtain signed transfer URLs, and upload eligible content to SharePoint. It preserves source metadata, handles expiring URLs and transfer retries, and records the last successful version.
Martini capabilities used
- scheduled workflows
- API consumption
- file orchestration
- data mapping
- duplicate prevention
- retry handling
Applications commonly integrated with Autodesk Construction Cloud
Autodesk Construction Cloud can be integrated with adjacent enterprise applications when project, construction, document, financial, or operational data must move between systems. These pairings generally require explicit API access and field-level ownership decisions rather than assuming a packaged Autodesk integration.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize project, customer, RFI, and issue information with customer-facing or project-delivery processes. | Autodesk Construction Cloud → Martini → Salesforce | Martini retrieves or receives selected ACC Projects, RFIs, Issues, and Submittals, maps project and resource identifiers to Salesforce objects, applies ownership rules, and sends controlled status updates back to ACC when required. |
| ServiceNow | Convert ACC Issues and selected project events into operational work items while retaining the source project and issue context. | Autodesk Construction Cloud → Martini → ServiceNow | Martini receives supported APS webhook notifications or runs scheduled incremental workflows, re-fetches the current ACC Issue, maps it to a ServiceNow work item, stores the ACC identifier for idempotency, and routes selected resolution updates back. |
| NetSuite | Connect project, procurement, cost, or vendor information with financial and operational records. | Autodesk Construction Cloud → Martini → NetSuite | A Martini workflow retrieves approved ACC project and cost-related information, normalizes identifiers, maps values to NetSuite records, and returns financial references or statuses where the agreed APIs support the flow. |
| SAP S/4HANA | Align construction project, procurement, cost, and financial data with enterprise resource planning processes. | Autodesk Construction Cloud → Martini → SAP S/4HANA | Martini orchestrates REST calls to ACC and SAP, applies project and cost-center mapping, enforces SAP ownership of financial values, and uses checkpoints and retries for controlled bidirectional synchronization. |
| Microsoft SharePoint | Replicate selected ACC documents, metadata, and project deliverables for broader document access and retention processes. | Autodesk Construction Cloud → Martini → Microsoft SharePoint | Martini uses APS Data Management APIs to identify hubs, folders, items, and versions, downloads eligible content through the relevant transfer URL, maps metadata, and uploads files to SharePoint with duplicate and version controls. |
| Microsoft Teams | Notify project teams about new or changed Issues, RFIs, Submittals, or Forms. | Autodesk Construction Cloud → Martini → Microsoft Teams | Martini consumes supported ACC notifications or scheduled changes, retrieves the current resource, formats a concise project-aware message, applies notification rules, and sends it to the appropriate Teams destination through the target API. |
| Procore | Exchange agreed project-management information when contractors operate both construction-management platforms. | Autodesk Construction Cloud → Martini → Procore | Martini maps only the jointly approved objects and fields between the two platforms, uses source identifiers for duplicate prevention, and applies conflict rules so each system remains authoritative for designated fields. |
| Jira | Route construction coordination, facilities, or engineering issues to delivery teams using Jira workflows. | Autodesk Construction Cloud → Martini → Jira | Martini transforms selected ACC Issues into Jira work items, preserves project and source URLs, applies routing and priority rules, and processes selected Jira status or comment updates back through ACC APIs when supported. |
How to build a Autodesk Construction Cloud integration in Martini
Objective
Establish OAuth 2.0 access to Autodesk Platform Services and configure the account, project, hub, and target-system identifiers required by the integration.
Instructions in Martini
- Store APS client credentials and target-system secrets in secure Martini configuration
- Choose two-legged OAuth for application access or three-legged OAuth for user-authorized operations
- Configure required APS scopes and account or project permissions
- Keep account IDs, project IDs, and hub IDs outside workflow logic where possible
Objective
Select the event or schedule that best matches the required latency and the confirmed ACC coverage.
Instructions in Martini
- Use an APS webhook for a supported resource and event
- Expose a Martini API endpoint for callback delivery
- Use a scheduler for incremental synchronization and reconciliation
- Define the checkpoint and overlap window for scheduled runs
Objective
Receive the notification or retrieve the current ACC resource before applying downstream business logic.
Instructions in Martini
- Validate the callback or scheduled request
- Re-fetch the current Project, Issue, RFI, Submittal, Asset, Form, or Data Management resource
- Process every paginated response page
- Handle signed URLs separately from business-object metadata
Objective
Coordinate source retrieval, validation, transformation, target writes, and checkpoint updates in a maintainable Martini workflow.
Instructions in Martini
- Separate authentication, retrieval, transformation, and target-write stages
- Route objects according to project, status, ownership, or resource type
- Persist correlation identifiers and synchronization checkpoints
- Use reusable workflow logic for common API and error-handling behavior
Objective
Convert ACC JSON structures into the target system model while preserving source identifiers and enforcing required business rules.
Instructions in Martini
- Map ACC resource fields to canonical and target fields
- Normalize dates, statuses, identifiers, locations, and participants
- Validate required fields and project or tenant scope
- Apply field-level system-of-record and conflict rules
Objective
Create or update downstream records and optionally send controlled updates back to ACC.
Instructions in Martini
- Use source keys for idempotent upserts
- Write only fields owned by the integration direction
- Store ACC project and resource identifiers in target records
- Apply bounded retries for throttling and transient failures
Common Autodesk Construction Cloud data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Projects | Provide construction project context, identifiers, and scope for downstream synchronization and resource lookups. | Salesforce, ServiceNow, NetSuite, SAP S/4HANA, Procore | Martini retrieves project metadata, validates account and project scope, stores source identifiers, and maps project ownership and status fields. |
| Issues | Track construction issues assigned to users or companies, including status, type, location, comments, and due dates. | ServiceNow, Jira, Salesforce, Procore | Martini can process webhook-assisted or scheduled changes, re-fetch the current Issue, apply routing and priority rules, and use source keys to prevent duplicates. |
| RFIs | Manage requests for information, questions, responses, participants, due dates, and review status. | Salesforce, ServiceNow, Procore, Microsoft Teams | Martini maps project and participant context, normalizes status and dates, synchronizes approved fields, and handles incomplete event coverage through reconciliation. |
| Submittals | Coordinate submittal packages, reviews, participants, and documentation workflows. | Salesforce, Microsoft Teams, SharePoint, Procore | Martini transforms review and project metadata, links related documents where available, and applies approval and notification rules. |
| Assets | Represent equipment, facilities, or other managed project assets. | ServiceNow, Salesforce, SAP S/4HANA | Martini maps asset identifiers and location data, validates project scope, and synchronizes selected lifecycle fields according to system ownership. |
| Forms | Represent project forms, checklists, inspections, and field records. | Salesforce, ServiceNow, Microsoft Teams, SharePoint | Martini retrieves form data through the applicable ACC API, maps structured fields, validates required values, and routes exceptions for review. |
Authentication and security considerations
OAuth 2.0 and access scope
Autodesk Platform Services uses OAuth 2.0. Two-legged OAuth supports application-level access, while three-legged OAuth supports user-authorized operations. Effective access also depends on scopes, Autodesk account configuration, application authorization, module permissions, and project permissions.
Credential protection
Store APS client secrets, tokens, and environment-specific identifiers in Martini secrets or secure configuration rather than workflow definitions. Treat access tokens as short-lived credentials and reacquire or refresh them as required by the selected flow.
Tenant and project isolation
- Validate account, hub, project, and resource scope before processing data.
- Use least-privilege scopes and restrict target-system access to the required workflows.
- Validate webhook authenticity and subscription context according to the documented APS behavior.
Operational considerations for Autodesk Construction Cloud integrations
Rate limits and retries
Detect throttling responses, honor Retry-After when provided, use bounded backoff, and avoid uncontrolled parallel requests. Classify authentication, permission, validation, transient, and business-conflict errors separately.
Pagination and checkpoints
List endpoints may be paginated. Persist checkpoints and process an overlap window so delayed indexing, clock differences, or failed executions do not silently omit changes.
Webhooks and idempotency
Webhook coverage is selected rather than universal. Account for duplicate, out-of-order, expired, or missed notifications. Re-fetch the current resource and use project-plus-resource identifiers or item and version identifiers to prevent duplicate writes.
Files and schema changes
Business objects and file content may require separate API calls and signed transfer URLs. Preserve version identifiers, handle expiring URLs, and maintain explicit mappings against the relevant APS API family and version.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrated integration logic
Scripts often combine authentication, pagination, mapping, retries, and target writes into code that is difficult to govern. Martini separates these concerns within reusable workflows and APIs while allowing custom JVM-compatible logic where specialized handling is required.
Reliable synchronization
Martini can combine APS webhooks with scheduled reconciliation, checkpoints, validation, idempotency, and controlled retries. This is useful when Autodesk event coverage is limited or when large project and document synchronizations require operational controls.
Maintainable enterprise contracts
Martini can expose a controlled API façade, map ACC objects to canonical models, apply system-of-record rules, and route errors for review. This reduces point-to-point coupling while preserving flexibility across ServiceNow, Salesforce, financial systems, document repositories, and other targets.
Frequently asked questions
Autodesk Construction Cloud is integrated primarily through Autodesk Platform Services REST APIs, using OAuth 2.0 and project or account context. Selected Autodesk resources support webhook notifications, while scheduled REST workflows can provide incremental synchronization and reconciliation. Data Management APIs support hubs, folders, items, versions, and file-related operations.
Yes. No documented native Martini connector was identified, but Martini can integrate with Autodesk Construction Cloud by consuming Autodesk Platform Services REST APIs, implementing OAuth 2.0, receiving supported webhook notifications through a Martini API, and orchestrating mappings, synchronization, file handling, and error processing.
No. A dedicated Autodesk Construction Cloud connector is not required. Martini can use Autodesk's confirmed native integration mechanisms, including APS REST APIs, OAuth 2.0, selected webhooks, Data Management APIs, and documented file transfer operations.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Autodesk Construction Cloud with Martini. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from Autodesk, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
Use ACC APIs exposed through Autodesk Platform Services for Projects, Issues, RFIs, Submittals, Assets, Forms, Locations, and account administration. Use APS Data Management APIs for hubs, projects, folders, items, versions, and related document operations. No current ACC GraphQL or SOAP API should be assumed.
Yes, Martini can expose an API endpoint to receive APS webhook HTTP requests. Autodesk webhook coverage is limited to selected resources and events, so the required coverage must be confirmed for each integration. A scheduled reconciliation workflow should supplement webhook processing.
A robust synchronization uses paginated REST requests, a persisted checkpoint, an overlap window, deterministic source keys, and periodic reconciliation. Martini can re-fetch the current resource after a webhook, deduplicate by project and resource identifiers, and retry throttling or transient failures with bounded backoff.
Yes. Martini can expose a controlled REST API that presents a stable enterprise-facing contract while orchestrating calls to APS. The façade can enforce authentication and authorization, validate inputs, apply business rules, normalize ACC responses, and shield consumers from resource-specific API details.
Related Martini documentation
Workflows
Mapping
Plan your Autodesk Construction Cloud integration
Use Martini to connect Autodesk Construction Cloud and Autodesk Platform Services with enterprise applications through secure APIs, webhook endpoints, scheduled workflows, data mapping, and controlled synchronization.