Onboarding & account setup

Before you write any code, a small amount of setup happens in the VastVision web app (our middleware). Most of it is done once, by VastVision and one administrator on your side.

Accounts you will need

At least one person on your team needs a user account in the VastVision web app. That account is used to generate the access token for your integration (Settings › Custom Integration), to build automation recipes and their webhooks (and view each webhook’s signing secret), and to look up the printer and label template IDs your application will use. We recommend two named administrators so access does not depend on one person.

Request your account early

Ask your VastVision contact to create your administrator account(s) at kickoff. Your developers can read this guide in the meantime, but they cannot call the API until a token has been issued from an account in your organization.

Getting started

1. VastVision creates administrator account(s) for your organization in the web app.
2. Your administrator generates an access token under Custom Integration settings and stores it in your secrets manager.
3. Your developers verify the token with GET /third-party-access/ping (see Verify your token).
4. VastVision shares the printer_id of each Zebra printer and the rfid_label_template_id of your label design. Store them as configuration in your application.
5. You stand up an HTTPS endpoint for webhooks. Your administrator (or VastVision) builds automation recipes with a webhook action on the Automation Recipes page, then uses Send test webhook to confirm your endpoint receives and verifies the message (see Webhooks). Each webhook action’s signing secret is shown once, so store it immediately.
6. Run a supervised first print with VastVision before rolling out to your users.