Best practices & FAQ
Best practices
Section titled “Best practices”- Keep tokens server-side and request only the scopes you need.
- Store
printer_idandrfid_label_template_idas configuration, not in code, so printers can be swapped without a release. - Group print requests by product and size so every asset in a request shares the same
classification_ids. - Record every EPC returned by the create and print routes. It is your key for matching later movement events.
- Cache zones and classifications and refresh them on a schedule.
- Webhooks: verify every signature, return
200immediately, process in the background, deduplicate onepc_hexplustimestamp, and backfill fromGET /mqtt-change-messages/. - Test with Send test webhook on the Automation Recipes page before pointing a recipe at production.
- Parse
priceas a string or number, and treat missing keys in stock alerts asnull.
Why did fewer assets come back than I sent?
Section titled “Why did fewer assets come back than I sent?”Assets whose epc_hex already exists are not created and are left out of the response. Compare the EPCs you sent with the EPCs returned.
Why didn’t I get a webhook when an item moved?
Section titled “Why didn’t I get a webhook when an item moved?”Check that the automation recipe is active and covers the zones the item moved between, and that your endpoint returned exactly 200. Use Send test webhook to confirm your endpoint is reachable.
Can we get a webhook for other kinds of movement?
Section titled “Can we get a webhook for other kinds of movement?”Yes. Build another automation recipe for that movement and give it its own URL path (see How automation recipes work).
Our endpoint was down for a few minutes. How do we catch up?
Section titled “Our endpoint was down for a few minutes. How do we catch up?”Messages are not retried. Call GET /third-party-access/mqtt-change-messages/ and apply any movements newer than the last one you processed.
How do I get my printer and template IDs?
Section titled “How do I get my printer and template IDs?”From your VastVision contact or the web app (see Onboarding).
Who on our team needs a VastVision account?
Section titled “Who on our team needs a VastVision account?”At least one administrator, to generate tokens, build automation recipes, and look up IDs. We recommend two.
We lost the webhook signing secret.
Section titled “We lost the webhook signing secret.”It is shown only once. Set up the recipe’s webhook action again in the web app (or ask VastVision to), then update your receiver with the new secret.
Our token may have leaked.
Section titled “Our token may have leaked.”Contact VastVision immediately to revoke and reissue it.