Developers

How the TradesMen ecosystem is wired together.

TradesMen.dev isn’t just a set of connected apps that each do one thing well and integrate cleanly with the rest. This is the developer starting page — a high-level map of identity, app-to-app APIs, webhooks, realtime data arcs, and security.

Independent apps, one connected platform.

Each app in the TradesMen.dev family is built as a smart, independent webapp. In the ecosystem, every app speaks the same “language” — your identity, data, and activity flow cleanly across apps, workflows, and APIs without giving up control or security.

Use the right app at the right layer: identity and profiles, workflows and logic, operations, or data and insights.

  • Open — Built on open APIs and webhooks.

  • Secure — Your identity. Your data. Your rules.

What connects, and how.

A high-level view of the building blocks. You use them in developer ways and assemble the public architecture you ship.

One profile, everywhere.

TradesMen Network is the identity layer. Users and companies own their profile, roles, consents, and connections. One identity unlocks every app and every API — on the web, iOS, and Android. You get SSO, scoped tokens, and verified trust built in.

Documented conversations, not code silos.

The messenger, sharing, and orchestration live in the platform. Messages, events, and notes drive workflows the same way for apps and integrations.

  • Real-time messaging between users and systems

  • Event streams and action triggers

  • Audit trails and state you can trust

  • Plug into webhooks and events instead of rebuilding them

Powerful tools that happen to be ecosystem.

Photos, proof, forms, jobs, gear, docs, and more — in TradesMen Cam, Tools, and Hub. Shared across apps by design. Build automations, custom fields, and triggers without re-inventing the wheel.

Structured for the flow, not stuck in one.

Every action, job, message, and asset creates data. It’s normalized, event-based, and queryable via APIs. Use dashboards, reports, exports, or stream it to your warehouse — your data, your way.

Security by default.

From verified identity to scoped tokens, app permissions, and tenant controls — security is built into every layer. Monitor access, log everything, and keep your ecosystem safe as you scale.

Docs, events in, spin ready.

Public, versioned APIs. Predictable webhooks. Clear rate limits. SDKs and examples. Build once, connect to the entire ecosystem — or integrate just what you need.

Three doors into the ecosystem.

Build anything — from apps to automations to analytics to AI and everything in between.

  • Integrate now — Start with APIs and webhooks. Build fast with our docs. View API docs

  • Extend your apps — Use SDKs, components, and libraries to move faster. See SDKs

  • Talk to us — Have a big integration idea? We’ll connect you with the right team. Contact us

Start integrating now

Developer reference

What you can build against today.

These are the public, unauthenticated, read-only endpoints and feeds TradesMen.dev serves right now. They are snapshot-backed, cacheable with an ETag, and return JSON or XML. Authentication is not required because nothing here is private.

Public read API

Same conventions throughout: ETag plus 304, a bounded shared cache, and limit/offset where a list can grow.

  • GET /api/public/products Every published app with its current version and platform count.
  • GET /api/public/products/{slug} One app in full: platforms, releases, updates, roadmap, docs and status.
  • GET /api/public/services The shared services catalog.
  • GET /api/public/services/{slug} One service, with its capabilities and platform availability.
  • GET /api/public/releases Release history, filterable by product, service or channel.
  • GET /api/public/updates The Updates Center, filterable and paginated.
  • GET /api/public/roadmap Public roadmap items and the stage vocabulary.
  • GET /api/public/docs Documentation discovery index (metadata, not bodies).
  • GET /api/public/platforms The platform, availability-state and release-channel vocabularies.
  • GET /api/public/known-issues Public known issues.
  • GET /api/public/status Component-level operational status.
  • GET /api/public/status/summary One-line overall status summary.

Feeds

Subscribe rather than poll, if a feed reader fits your workflow.

Authenticated ingestion

First-party TradesMen systems can submit release and update information to TradesMen.dev over a signed endpoint.

  • HMAC-SHA256 request signing over the scope, timestamp, nonce and body hash.
  • Replay protection and idempotency, so a retried delivery is never duplicated.
  • Per-client scopes, an hourly rate limit, and an audited delivery log.
  • Submissions arrive as drafts for review unless a client is explicitly trusted.

Ingestion is for first-party systems and is enabled per client by an operator. Ask us if you are building one; the signing contract is published at /api/ingest/v1/health when the feature is enabled.

Developer documentation

No API or integration documentation has been published yet.

The endpoints listed on this page are live and stable; the written reference for them is still being prepared.

Ask a specific question ›

What is deliberately not here. TradesMen.dev publishes no internal hostnames, service credentials, private endpoints or production tokens. Administration and ingestion surfaces are noindex, authenticated, and documented only to the operators who need them.

TradesMen.dev is owned and operated by Pimentel Services Ltd.

Building something that should connect to the ecosystem?

Tell us what you’re building and we’ll point you in the right direction.