Altium Design Software API

Created: June 6, 2016 | Updated: September 26, 2016
This documentation page references Altium NEXUS/NEXUS Client (part of the deployed NEXUS solution), which has been discontinued. All your PCB design, data management and collaboration needs can now be delivered by Altium Designer (with Altium Designer Enterprise Subscription) and a connected Altium 365 Workspace. Check out the FAQs page for more information.
Please note that this documentation was last updated for an older version of Altium NEXUS. While many of the principles and approaches will remain the same, be aware that interfaces, objects, methods, properties, and the like will have changed since then, and will not reflect the entirety of those found in later versions of the software.

The Altium NEXUS Application Programming Interface (API) exposes program functionality to external sources, such as the Altium NEXUS scripting system.

The API is composed of sub APIs, such as those offered by Altium NEXUS's range of design editors. For example the PCB editor has the PCB API, the Schematic editor has the Schematic API, the Project Manager has the Workspace manager API, Altium NEXUS platform has its own Client API, and so on.

Each API can compose of object interfaces, classes, routines and enumerated constants. The editor-specific APIs have their own Object Model, which in itself is a hierarchical system of Object Interfaces. These object interfaces represent Altium NEXUS's objects.

The Altium NEXUS API, its sub APIs and their Object Models

Object Model Hierarchy

Object Interfaces represent design objects, and can be used in scripts to access data in design documents that are open in Altium NEXUS.

Object Interfaces have properties and methods:

  • Methods of Object Interfaces are the actions an Object Interface can perform.
  • Properties of Object Interfaces represent the data contained in the object that's represented by the interface.

A parent object interface can have child object interfaces, and in turn, child object interfaces can act as parent object interfaces to child object interfaces, and so on down the chain.

This forms an Object Model Hierarchy. For example, in the Workspace Manager Object Model, the IWorkspace Object Interface is the top level interface representing the Workspace manager in Altium NEXUS. Projects are part of the Workspace Manager, therefore an IProject interface is a child interface to the parent IWorkspace interface.

Continuing on, documents are part of a project, so the IProject interface is the parent interface and IDocument is a child interface. Design objects such as sheet symbols, components and buses are child objects of the document object (represented by the IDocument interface).

This can be illustrated in the following simple example hierarchy:

.  IProject
.  .  IDocument
.  .  .  ISheetSymbol
.  .  .  IComponent
.  .  .  IBus

The figure below is an illustration of the relationship between objects in Altium NEXUS, and the object Interfaces supported by the various Object Models from Altium NEXUS API.

Projects and the corresponding documents are managed by the Workspace Manager. A project open in Altium NEXUS is represented by the IProject object interface, and the documents from this project are represented by the IDocument interfaces.

As also shown, the PCB documents and PCB design objects are managed by the PCB Editor and its PCB Object Model. The open PCB document is represented by its IPCB_Board interface and the design objects, in this case the pad and track objects, are represented by IPCB_Pad and IPCB_Track interfaces.

Using the API in scripts

The scripting engine in Altium NEXUS has built in PCB, Schematic and Workspace Manager APIs as well as a subset of Embarcadero Delphi's Run Time Library. The PCB, Schematic, Workspace Manager Object Models from the scripting engine enable you to write scripts that act on PCB or Schematic documents, or invoke one of the file management routines.

The Object Models from the Altium NEXUS API are accessible in scripts, so you can code the object and method names (with appropriate parameter values) using one of the several supported scripting languages, such as EnableBasic, Visual Basic, Javascript, TCL and the most commonly-used DelphiScript (which is very much like Embarcadero Delphi).

DelphiScript Example
Procedure PadCount;
 Board : IPCB_Board;
 Pad : IPCB_Primitive;
 Iterator : IPCB_BoardIterator;
 PadNumber : Integer;
 PadNumber := 0;
 Board := PCBServer.GetCurrentPCBBoard;
 If Board = Nil Then Exit;
 Iterator := Board.BoardIterator_Create;
 Pad := Iterator.FirstPCBObject;
 While (Pad <> Nil) Do
   Pad := Iterator.NextPCBObject;
 ShowMessage('Pad Count = ' + IntToStr(PadNumber));

Using the API for server development

The Altium NEXUS scripting system implements a subset of the complete Altium NEXUS API and its Object Interfaces. The Altium DXP Developer, used for developing Altium NEXUS server Extensions, has access to the full Altium NEXUS API via a set of API SDK source units.

More information

Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

Contact Us

Contact our corporate or local offices directly.

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: