Developer portal

Connect software and agents to LegoTechApps.

Use versioned REST discovery, a complete OpenAPI contract, public Streamable HTTP MCP discovery, and a separate authenticated MCP server for permitted business data and workflows.

Read OpenAPI Try API v1 View MCP metadata

Quickstart

From discovery to a scoped connection.

Public discovery needs no credentials. Product tools require a key created by an authorized dashboard user. A key inherits that user's business and module permissions, starts read-only unless write access is granted, and can be revoked at any time.

1. Discover

Fetch the stable API index and version policy.

curl https://legotechapps.com/api/v1/
curl https://legotechapps.com/api/v1/policy

2. Create a key

3. Test public MCP

Connect any compatible MCP host to the read-only public discovery server without credentials.

URL: https://legotechapps.com/mcp
Transport: Streamable HTTP

Contracts

Predictable enough for an agent.

Versioned REST

Major versions live in the URL, beginning with /api/v1/. Compatible fields may be added inside v1. Breaking changes require a new major path.

Read lifecycle policy

Typed errors

REST failures use RFC 9457 application/problem+json, including a stable code and a safe resolution hint.

Error conventions

Live limits

Responses expose RateLimit-Policy and RateLimit. A 429 also supplies Retry-After so clients can self-throttle.

Model Context Protocol

One permission-aware connection.

The public MCP server at https://legotechapps.com/mcp uses Streamable HTTP and JSON-RPC 2.0 to expose read-only developer discovery tools. The separate authenticated business endpoint at https://legotechapps.com/lt/api/mcp can expose permitted tools for clients, orders, invoices, stock, suppliers, expenses, buildings, residents, units, vehicles, maintenance missions, reviews, QR codes, forms, media, chatbot knowledge, and account spending.

MCP tools never bypass dashboard permissions. Treat keys as secrets, choose the narrowest useful module scope, and revoke a key immediately when it is no longer needed.

Errors and deprecation

Machine-readable failure, visible lifecycle.

Problem responses contain type, title, status, detail, instance, code, and hint. Deprecated resources return the RFC 9745 Deprecation header with migration guidance. When removal is planned, LegoTechApps also returns a Sunset header at least six months before that date.

{
  "type": "https://legotechapps.com/developers/#errors",
  "title": "API Route Not Found",
  "status": 404,
  "detail": "The requested public API route does not exist.",
  "instance": "/api/v1/missing",
  "code": "API_ROUTE_NOT_FOUND",
  "hint": "Read /openapi.json for available endpoints."
}

Sandbox and CLI

Start with a harmless discovery call.

The public v1 index is safe for connection checks. New accounts include trial access for evaluating product workflows, while every business remains isolated. An official npm, PyPI, or Homebrew CLI is not published yet. Until it is, use curl, an OpenAPI-generated client, or an MCP host such as Claude, ChatGPT, Cursor, or VS Code.

Create or manage a key Ask developer support