Connect what you already have
Most equipment already sends messages: a payment terminal to its host, a charger to its management system, a meter or an industrial controller to a broker, a hospital system to its integration engine. A mapping tells wede which field of those messages fills each field of a wede operation. The messages are then sent to wede as they are, and each one becomes an operation exactly like any other: the same checks, the same protection against duplicates, the same Devices and Reconciliation. There is no code to write on your side, and nothing changes on the equipment.Only what you map enters wede
A mapping lists the fields wede keeps. Everything else in each message is ignored and never stored. The sample messages you use to try a mapping are never stored either. Your organisation stays in control of what wede holds, field by field.What a mapping says
For JSON, a field is a path with dots (
data.amount, items.0.qty); messages can arrive one at a time, as a list, or inside a list at a path you set. For CSV, a field is a column name, with a header line and the separator you choose.
wede never guesses. A required field without a value, a value that is not in its table, or a time or a number that cannot be read refuses that message with the field and the reason; the other messages go on.
Versions
A mapping has a code and versions. A version never changes once saved: a change is a new version. One version is in use at a time, and the others are kept. An archived version stops being used and is kept for audit. Nothing is deleted.Sending messages
In the dashboard, Mappings shows the address of each mapping in use. Your systems, or the broker that receives the messages of your devices, send them there with your API key, up to 500 messages per request, handled in order:Content-Type: text/csv. The answer lists every message as accepted, duplicate or rejected, with the field and the reason. Each message counts toward the same limit per minute as POST /v1/events.
Try before you use it
In the dashboard, paste a few real messages and press Try on sample: each message shows the operation it would become, or why it would be refused, before anything is saved. The same check is available from your systems withPOST /v1/mappings/preview.
Mappings are managed by the people of your organisation who manage its integration. wede staff never see or manage them.