Indirect Management
Leverage external identifiers on Weedmaps
Indirect Management simplifies how you manage menu items by allowing you to send PUT requests using your own identifiers.
With this method:
-
You no longer need to store Weedmaps’ item
id. -
You send one request per item, and Weedmaps handles:
- Creation (if the item doesn’t exist).
- Update (if the item already exists).
| Method | Description | Try It! |
|---|---|---|
| PUT | Update or create Menu Item by External ID | Upsert a Menu Item by External Identifier. |
| DELETE | Delete Menu Item by External ID | Delete a Menu Item by External Identifier. |
How Indirect Management Works
- Use PUT requests with your internal ID as the reference.
- Weedmaps creates the item if it doesn’t exist or updates it if it does.
- You receive the same response structure as Direct Management—containing all related objects (brand, product, strain, tags, etc.).
Key Differences: Indirect vs Direct Management
| Feature | Indirect Management | Direct Management |
|---|---|---|
| Identifier Source | Your external ID | Weedmaps-generated ID |
| Request Type | PUT (upsert behavior) | POST (create), PATCH (update) |
| Use Case | Simple syncing without ID storage | Full manual control |
| Recommended For | Systems that sync often or prefer stateless updates | Systems needing exact control over data relationships |
When to Use Indirect Management
Choose Indirect Management if you:
- Prefer to avoid tracking Weedmaps IDs.
- Want fewer API calls (single PUT handles create or update).
- Are managing large inventories that sync frequently.
Updated 4 days ago