01
Documented
Bentley developer APIs
Bentley publishes iTwin Platform APIs for supported project, storage, issue, form, and synchronization services.
Bentley Systems / Engineering information and document management
Evaluate Bentley ProjectWise by its exact product boundary, configuration, native identities, permissions, documented interfaces, source authority, and the human decisions surrounding connected work.
What it is designed to do
Managing engineering information, project structures, document identity, versions, metadata, workflow state, and controlled access.
Best suited for
Organizations already using Bentley ProjectWise for engineering documents, metadata, versions, workflows, and access control and needing governed connections without assuming the platform owns every downstream record or decision.
Buyer boundary
This profile explains documented product and integration surfaces. It is not an endorsement, procurement recommendation, guarantee of compatibility, or substitute for checking the buyer’s product, edition, region, licences, configuration, terms, permissions, and workflow.
Normal operating records
Bentley ProjectWise may remain authoritative for accepted records within its configured role. A copy, export, dashboard, integration run, AI index, or downstream display does not inherit that authority automatically.
Typical AEC uses
Records and information
Datasource and project
Document and version
Engineering metadata
Folder and storage
Workflow state
User and access control
Documented access routes
A vendor interface establishes a possible technical route. It does not establish record authority, downstream security, correct mapping, complete processing, accepted output, or permission to act.
Documented
Bentley publishes iTwin Platform APIs for supported project, storage, issue, form, and synchronization services.
Product-dependent
APIs, SDKs, connectors, and desktop dependencies vary by product and deployment.
Native IDs and crosswalks
Identity, permission, and authority
Known implementation limits
Do not replace Bentley ProjectWise from a directory label alone. First establish its current records, users, dependencies, support condition, interfaces, source authority, migration constraints, and whether the real need is to keep, connect, contain, consolidate, or reassess it.
The iTwin API catalogue is not a universal contract for every ProjectWise deployment
Desktop, cloud, and legacy environments expose different interfaces
Documentation for one edition, module, region, deployment, or version does not establish availability in another
A successful request, sync, run, generation, or export does not prove completeness, correctness, review, or business acceptance
Where StructuredLayer may connect it
The actual implementation boundary is confirmed from the buyer's product, workflow, records, permissions, difficult cases, required direction, consequences, and acceptance conditions.
Crosswalk native identities to governed company, project, document, work, and decision records
Retrieve or move only approved fields and files through documented interfaces
Route unmatched, conflicting, stale, failed, or permission-hidden records for review
Keep deterministic validation, AI assistance, human review, and accepted business state distinct
Document mappings, credentials ownership, monitoring, retries, recovery, handover, and maintenance responsibility
Questions before scope
Which Bentley ProjectWise product, edition, module, version, region, and deployment are in scope?
Which native records and fields are authoritative?
Which documented interfaces and permissions are available to this buyer?
Is read-only retrieval sufficient, and who can approve consequential writes?
How will failures, duplicates, conflicts, permission loss, API changes, and manual fallback be handled?
Who owns the connection, documentation, monitoring, support, and exit path after handover?
Official vendor documentation
Features, endpoints, scopes, licences, regions, plans, limits, and vendor terms can change. The implementation must confirm the current documentation for the buyer's actual environment.
Related system profiles
Primary operating system
Controlled documents, correspondence, workflows, and project information
Inspect profileSpecialist validation system
Model validation, rules, classifications, issues, BCF, and review evidence
Inspect profilePrimary operating system
Project execution and construction records
Inspect profileBentley ProjectWise and one workflow
Bring the exact product, module, environment, workflow, records, users, permissions, required access direction, current failure, and intended buyer decision.
Next best page
Move from evaluating the operating conditions to choosing a bounded response and assessing one real workflow.