Operational controls and external handoffs
Learn when operational work belongs to third-party links, scheduling, logs, custom roles, DAM shareable links, or public share-token reads.
Start here when the job is not to change the main catalog model, but to coordinate work around it: external IDs, scheduled changes, audit lookups, role records, or token-backed asset sharing.
Use this page to choose the right operational surface before changing supporting records or external handoffs. Operational routes can look similar because they sit around the main catalog, media, account, or role record. The right route depends on whether the caller is recording an outside reference, scheduling future work, reading item history, maintaining merchant roles, administering a share, or reading an already-issued share token.
The short model
Operational controls sit around the record that owns the actual business state. They help another system, user role, future workflow, or external recipient interact with Enad without making every job a product, media, order, or account mutation.
Choose the surface that matches the job:
- Use Third Party Link when an external system identifier needs to be recorded and linked to a product.
- Use Scheduling when a supported item change should happen later instead of immediately.
- Use Logs when a caller needs API-exposed history for an item.
- Use Custom Roles when a trusted admin workflow changes merchant role records.
- Use DAM shareable-link operations when a trusted workflow creates, updates, deletes, or changes the resources behind a shareable link.
- Use Shareable Links when a token is already available and the caller only needs to read exposed folders or media.
Choose the right surface
| Job | Use | Why |
|---|---|---|
| Map an outside identifier to a product | Third Party Link reference | Third-party link operations own external link records and product relationships. |
| Run supported catalog or asset changes later | Scheduling reference | Scheduling operations create, list, inspect, and delete scheduled jobs instead of mutating the target immediately. |
| Inspect an item's API-exposed history | Logs reference | Logs are read-only item history lookups; they do not replace the surface that owns the mutation. |
| Manage merchant role records | Custom Roles reference | Custom role operations own role records. Merchant-user operations own user accounts. |
| Create or maintain a shareable asset link | DAM administration reference | Management DAM shareable-link operations manage the token-backed collection and its resource membership. |
| Read media through an existing share token | Shareable Links reference | Shareable Links are public read routes for folders and media after the trusted DAM workflow has created the share. |
Contract facts to keep in mind
Use these facts to choose the right reference. Use operation pages for exact fields, auth, validation, status codes, and response shapes.
- Third Party Link, Scheduling, Logs, Custom Roles, and DAM shareable-link management are trusted Management API workflows.
- Shareable Links are read-only DAM API routes for consumers that already have a share token.
- Third-party link records are app-scoped and carry a title, type, and URL. Product relationship routes attach or detach a third-party link from one product.
- Scheduling is for supported future changes, not every delayed workflow. Bulk scheduling create accepts up to 100 jobs, bulk delete accepts 1 to 100 job IDs, and mixed results need item-level handling.
- Logs are read-only item history lookups. Use the owning surface for corrections.
- Custom Roles own merchant role records, not merchant-user accounts.
- Management DAM shareable-link operations manage the token-backed collection and its resource membership.
Shareable-link boundary
Use DAM administration when a trusted user is creating the share, changing expiration or description, adding resources, removing resources, or deleting the share. Use Shareable Links when the token has already been issued and the caller only needs to read the exposed asset collection.
Events
Use Events after operational records change. The Event catalog covers custom-role events and DAM shareable-link events. No dedicated third-party-link, scheduling, or log event family is currently exposed; for those jobs, use the operation response and the broader event family for the item that changed.
Use the Event catalog for exact event type strings, schema IDs, required fields, and payload fields. Use Events latest for delivery and retry behavior.
Where to go next
- Need catalog concepts before operational routing? Read Products, variants, variant groups, prices, and stock.
- Need media and shareable asset context? Read Content, assets, and customer data.
- Need exact endpoint contracts? Use Reference, then choose the surface that owns the job.