Create a legitimate mapping
A mapping preserves an exact correlation between an external identity and an Ormuz identity that is already legitimately known. It never turns an external reference into a new access right.
The mapping preserves an exact correspondence between an external identity and a platform object that is already legitimately known.
When to create it
Create the mapping when execution already holds the target: an explicitly bound object, an object read through authorized access, an object created through a legitimate canonical path, or the target of an existing mapping for the same configuration.
What it does not allow
- searching by arbitrary platform ID;
- listing the merchant's objects;
- automatically traversing relationships;
- mutating the target;
- creating a mapping from a simple identifier supplied by a webhook.
Creation must be idempotent for the same target and reject conflicts. See External objects, drafts, and mappings.