Integrations

Your software stays the system of record.

HOACraft is the field layer. It sends what happened on site to the management platform you already run, and takes back what it needs to plan the next drive. Letters, fines, vendor payments and committee decisions never leave your system.

POST · violation.still_open
{
  "type": "violation.still_open",
  "data": {
    "violation": {
      "id": "f-wce-3",
      "title": "Lawn not maintained (repeat)",
      "level": 2,
      "cure_by": "2026-11-27T16:00:00.000Z"
    },
    "recheck": {
      "at": "2026-11-13T16:00:00.000Z",
      "result": "still_open",
      "note": "No visible change",
      "photos": []
    }
  }
}

Three ways to connect

Start with whatever your team can run today. Switching later doesn't change anything for inspectors.

Webhooks

One signed POST to your endpoint per event, within seconds. Retried for 24 hours with the same id, so you never double-count.

Webhooks & signing →

REST API in design

Pull violations, work orders, ACC requests and drives on a schedule. Push properties, open violations and ACC applications in.

API reference →

CSV

No developers? Download open violations as a CSV from the app and import it into your system.

How data moves →

What moves in each direction

Each kind of record has a clear owner. Nothing is edited in two places.

HOACraft sends you

You send HOACraft

  • Communities and properties, with your own ids
  • Open violations with their stage and next re-check date
  • ACC applications that need a site visit, and the committee's decisions
  • Work-order status, if vendors are managed on your side

Built to be trusted by your IT team

Signed requests

Every webhook carries an HMAC-SHA256 signature with a timestamp, and the docs include a tester that runs in your browser.

Idempotent

Each event has a unique id that retries reuse. Dedupe on it and replays are harmless.

Your ids everywhere

Once properties are imported, every payload carries your account id. No address matching.

Versioned contract

Fields are only added within a version. Breaking changes ship as a new version you opt into.

Sandbox keys

With the REST API, test keys will work only against a sandbox with fictional data, separate from production.

Published, not promised

The OpenAPI spec and real sample payloads are public. Your developers can start before you sign anything.

Using a platform we don't connect to yet?

Anything that can take a webhook, call an API or import a CSV works today. Tell us which platform you run: customer demand decides which native connectors we build first.