Developer

Developer Documentation

This page sets out how IntelliGrid technical documentation is organised and how to obtain access. Specifications are released to authorised integration partners and customers under agreement.

Request a Demo See API & Webhooks

The business problem

Why the specification is not published openly

Interface specifications for a platform that controls access permissions, holds asset registers and drives building operations are released under agreement rather than published. This lets us confirm the integration scope, issue scoped credentials, and provide a test environment appropriate to what is being built.

Access and asset data require scoped, accountable credentialsIntegration scope confirmed before credentials are issuedTest environments provisioned per integrationInterface changes communicated directly to holders

The IntelliGrid approach

How to obtain access

Contact partners@intelligrid.asia with the systems you intend to connect and the data flow required. We will confirm the relevant interfaces, provide the documentation set and provision test credentials.

Describe the systems and the direction of data flowReceive the relevant documentation setTest environment credentials provisionedProduction access issued after validation

Documentation set

What the reference covers

Each section below exists in the documentation issued to authorised partners. No endpoint paths, keys or payload specifications are published on this page.

Getting started

Environments, base URLs, versioning policy and rate limits.

Authentication

Credential types, token lifecycle, scopes and rotation.

Assets

Asset, location and condition objects with read and write scope.

Work orders

Creation, status transitions, assignment and evidence attachment.

Users

User provisioning, roles and permission assignment.

Events

Event types emitted on core object changes.

Webhooks

Subscription, delivery guarantees, retry behaviour and signature verification.

Errors

Error codes, meanings and recommended handling.

Environments

Test and production separation, and promotion process.

Business benefits

Integration scope agreed before development starts Credentials scoped to the integration’s actual needs A test environment separated from production data Interface changes communicated to credential holders Technical support during integration development