Ressurser

API-dokumentasjon, kildekode og megler-frontender for hele M360 → CRM-pipelinen. Alle lenker åpnes i ny fane.

Pipeline-lag

M360 FEUI
React frontend
Auth: Cookie / m360Token
marketer-frontend
M360 APIGraphQL
POST /api/graphql
Auth: Bearer JWT
GraphiQL explorer (login) GraphQL schema (source)
CRM GatewayAMQP
amqp://:5672 · RabbitMQ
Auth: Bearer
crm_gateway adapters
Vitec APIREST
/{installationId}/Estates/{id}
Auth: HTTP Basic
Vitec Megler Hub Swagger OpenAPI spec (local)
Core / WebtopREST
/flow/api/... · OAuth2
Auth: OAuth2 Bearer
Visma RES Core docs Scalar API explorer
Broker FEUI
Vitec Next FE / Webtop Broker Web
Auth: Broker login
Vitec Next (broker login) Webtop Broker Web

Vitec — broker side

Vitec Megler Hub (production)

Broker-side hub UI for Vitec Next

https://hub.megler.vitec.net
Vitec Megler Hub Swagger

Live OpenAPI 3.0 explorer (135 endpoints)

https://hub.megler.vitec.net/swagger/index.html
Vitec OpenAPI spec (local)

Bundled OpenAPI JSON — open with any Swagger viewer

/specs/vitec-megler-hub.json
Vitec Next QA bidding

QA environment for bidding flows

https://bud.qa.vitecnext.no

Webtop / Visma RES — broker side

Visma RES Core docs

Conceptual guide: Cases, Activities, Webhooks, Integrations

https://visma-real-estate-solutions.github.io/core-documentation/
Webtop Scalar API explorer (sandbox)

Interactive API browser — Cases, Bids, Properties, Projects, Roles, etc.

https://sb.webtopsolutions.com/flow/scalar/
Webtop Swagger (integration)

Live Swagger UI on the integration environment

https://integration.webtopsolutions.com/flow
Webtop Core/Cases OpenAPI spec (local)

Bundled OpenAPI JSON — 561 paths, 684 schemas

/specs/webtop-core-api-cases.json
Webtop Broker Web

Broker-side login UI

https://broker.webtopsolutions.com

M360 internal

M360 GraphiQL explorer

Login required. Live GraphQL schema + query playground.

https://admin.m360.marketer.tech/graphiql/
marketer-frontend

M360 React FE source — search for fieldName usages

https://github.com/marketertechnologies/marketer-frontend
marketer (backend)

Rails monorepo — graphql/, services/crm_gateway/, lib/api/{vitec,webtop}/

https://github.com/marketertechnologies/marketer
m360-field-mapping (this app)

Source for this visualizer

https://github.com/marketertechnologies/m360-field-mapping

CRM Gateway — adapters & dictionaries

crm_gateway/adapters/

Per-section, per-broker mapping representers

https://github.com/marketertechnologies/marketer/tree/master/app/services/crm_gateway/adapters
unit · Vitec adapter

adapters/vitec/stages_unit.rb

https://github.com/marketertechnologies/marketer/blob/master/app/services/crm_gateway/adapters/vitec/stages_unit.rb
unit · Webtop adapter

adapters/webtop/stages_unit.rb

https://github.com/marketertechnologies/marketer/blob/master/app/services/crm_gateway/adapters/webtop/stages_unit.rb
project · Vitec adapter

adapters/vitec/project.rb

https://github.com/marketertechnologies/marketer/blob/master/app/services/crm_gateway/adapters/vitec/project.rb
project · Webtop adapter

adapters/webtop/project.rb

https://github.com/marketertechnologies/marketer/blob/master/app/services/crm_gateway/adapters/webtop/project.rb
parking · Vitec adapter

adapters/vitec/parking_units.rb

https://github.com/marketertechnologies/marketer/blob/master/app/services/crm_gateway/adapters/vitec/parking_units.rb
parking · Webtop adapter

adapters/webtop/parking_units.rb

https://github.com/marketertechnologies/marketer/blob/master/app/services/crm_gateway/adapters/webtop/parking_units.rb
Vitec dictionary (enums)

HOUSING_TYPE, OWNERSHIP_TYPE, STATUS, FACILITIES_MAPPER...

https://github.com/marketertechnologies/marketer/blob/master/app/services/crm_gateway/adapters/vitec/dictionary.rb
Webtop dictionary (enums)

STATUS_TYPE, PROPERTY_TYPE, OWNERSHIP_TYPE, FACILITIES_MAPPER...

https://github.com/marketertechnologies/marketer/blob/master/app/services/crm_gateway/adapters/webtop/dictionary.rb

Hvordan dataflyten fungerer

  1. M360 FE — broker-team enters data in the React UI.
  2. M360 API — GraphQL persists to the Rails backend. Schema is browseable via GraphiQL.
  3. CRM Gateway — a RabbitMQ queue picks up changes; representer Ruby code in crm_gateway/adapters/{vitec,webtop}/ normalizes M360 fields into the broker shape.
  4. Vitec API — REST calls (HTTP Basic Auth) to /{installationId}/Estates/{estateId}.
  5. Core API — REST calls (OAuth2) to /flow/api/....
  6. Broker FE — the broker logs into Vitec Next or Webtop Broker Web and sees the data appear.