Step 5 of 5

Go live

Work through the go-live checklist and switch from the sandbox to the production base URLs.

Before you switch

Production runs the same Invoice Tools API and the same authentication as the sandbox, so the integration you tested is the one you run. What changes is the base URLs and your credentials.

Your integration needs a production-equivalent access method: a JWT signed with your key, which you exchange for an authentication token and then an authorization token. Authentication describes it.

Checklist

Work through these items before you go live. Your ticks are saved in this browser, so you can come back to the list later.

0 of 9 done

The JWT is created according to Vanguard's specification and signed with your key.
Tokens are renewed before they expire.
Only the invoice id is stored; everything else is fetched.
319-2 errors are shown so invoices can be corrected and resent.
Unknown fields and enum values don't cause errors.
Direct payments are reported to Waya.
Test invoices have been checked in Insight.
Base URLs have been switched to production.
If you use webhooks, signatures and timestamps are verified.

Where each item is covered

Item	Read more
The JWT and its signature	Sign a JWT
Renewing tokens	Renewal guidance
Storing only the `id`	Response
`319-2` errors	Categories
Unknown fields and enum values	API modifications (opens in a new tab), in Swagger
Direct payments	Direct payments
Checking test invoices in Insight	Insight
Production base URLs	Base URLs
Webhook signatures and timestamps	Verify the signature

Base URLs

Production has its own addresses for the Invoice Tools API and for Vanguard:

Invoice API	`https://api.sandbox.waya.se/v4/rest`
Vanguard	`https://vanguard.sandbox.waya.se/v2.0`

Invoice API	`https://api.waya.se/v4/rest`
Vanguard	`https://auth.waya.se/vanguard/v2.0`

Vanguard has a different host in production

The production address of Vanguard is not the sandbox address without sandbox. It is auth.waya.se, under the path /vanguard/v2.0.

Each environment has its own Swagger. The developer overview lists the Swagger addresses of both.

The code samples in these docs read the base URLs from WAYA_VANGUARD_URL and WAYA_API_URL, so switching to production is a change of configuration. In the environment that runs in production, set them to:

.env

WAYA_VANGUARD_URL=https://auth.waya.se/vanguard/v2.0
WAYA_API_URL=https://api.waya.se/v4/rest

After you go live

If a request fails in production, quote the full error code to Waya, as described under Contact support.