Made by makebetter

Connect

Your systems keep their own ids.

Nothing is replaced and nothing has to be renamed. Each system keeps its records as they are, pushes them in, asks before it creates, and hears when anything changes.

  1. 01

    Connect

    Each system becomes a source with a short mapping of its fields: which column is the VAT number, which is the register number, which fields are personal. It gets its own API key, bound to that source only, shown once and stored as a hash.

    For a system we have set up before, it is one step: pick it, and the source, the mapping and the key are made together.

    # the mapping, in part (simplified)
    vatNumber       → identifier.vat
    registrationNo  → register number
                      BG: bg-eik · DE: de-hrb, de-hra
    contactEmail    → e-mail, personal
  2. 02

    Push

    Send records in batches of up to 500, as often as you like. Each batch is checked against the mapping and saved whole or not at all; a record that does not fit goes to quarantine instead of in. Sending the same batch twice changes nothing.

    Send everything in a full run and whatever you did not send is marked as gone from your system. The answer to every push carries the identity's ID.

    POST /v1/sources/{source}/records/batch
    Idempotency-Key: 6f1c…
    
    { "externalId": "C-10422",
      "name": "Brezmira OOD",
      "vatNumber": "BG204817361" }
    
    → results[0], simplified
    { "identity": "org_01a1…c4b1" }
  3. 03

    Ask

    “Do you already know this company?” Ask with a VAT number, a register number, a name and country, or an e-mail, before you create it. Numbers give sure answers, names give possible ones, and nothing is written. The answer says which systems already hold it, and whether you do.

    “Which identity is my record?” Ask with your own id, any time.

    GET /v1/identities/match?vat=204817361
    # simplified
    
    { "sure": true, "signal": "vat",
      "identity": { "id": "org_01a1…c4b1", "displayName": "Brezmira" },
      "existsIn": ["ERP", "Invoicing", "Marketplace"],
      "yourIds": [] }
    
    GET /v1/identities/by-record?sourceId=…&externalId=C-10422
  4. 04

    Hear

    Every change is written as an event in the same transaction as the change, and sent to every subscriber by webhook: in order for each subscriber, all subscribers at once. Signed to the Standard Webhooks format, so any library checks the signature.

    A webhook can follow just one system's records. Personal fields stay out unless the subscription asks for them. Addresses must be https, and private or internal addresses are refused.

    • identity.createda new company or person
    • identity.updateda name, number or contact changed
    • identity.mergedtwo identities became one
    • identity.unmergeda merge was undone
    • identity.retiredno system holds it any more
    • identity.record_linkeda record joined, by match or by a person
    • identity.relation_addedrelated companies, a person at a company
    • source_record.vanisheda record a system stopped sending
    • source.run_overduea system stopped sending at all

    A delivery that fails is tried again after

    1. 1 min
    2. 5 min
    3. 30 min
    4. 2 h
    5. 6 h
    6. 12 h
    7. 24 h
    8. then dead · redeliver by hand

Watching the systems

It notices when a system goes quiet.

Tell it how often a system should send everything, say every 26 hours. Every 15 minutes it checks, and when a system is late or its last run failed, it says so on the dashboard and sends a source.run_overdue event, so the people who look after that system hear before anyone downstream notices stale data.

A system can be paused: its pushes are refused while it can still ask. Or retired, for good. Its records stay either way.

ERPfull run every 24 hok · 3 h ago
Invoicingfull run every 26 hok · 11 h ago
Marketplacesends as it changesnot watched
Sheetfull run every 24 hoverdue · 31 h ago

Built to be called a lot

Correct when every system calls at once.

  • Retries are safe. Writes take an Idempotency-Key; a repeated batch changes nothing.
  • No lost edits. Every change carries a version; a stale one is refused, not saved over.
  • One run at a time. Only one full run per system is open at once.
  • Nothing half-written. A batch, its events and its audit entries commit together.
  • Described. An OpenAPI description and reference docs come with the API.
  • Rate-limited per key, so one busy system cannot starve the rest.

Send us two customer lists.

An export from two of your systems is enough. We show you how many are the same company, which ones it is sure of, and which it would hold for you. No project, no new system.