These docs are for v3.2. Click to read the latest docs for v3.3.

API Authentication

Authentication as a merchant.

⚠️

API Access

Currently you must request API access here.

Server to Server

This recipe is an example of how server to server authentication, below are specific examples of authentication for particular roles.

🔒 Server Authentication

Learn how to authenticate server-to-server connections with AuthVia.

View Tutorial →

As a Merchant / Account

Authentication as a merchant is important when you want to engage with merchants directly. This will be the most common use case as this is the type of authentication needed in order to create a New Conversation Link with a New Customer.

See:

🔒 Creating Merchant authentication token

Learn how to create authentication tokens for merchant accounts.

View Tutorial →

As a Partner

When you need to create and listen to the data of multiple different merchant / accounts, you will need tenancy. This is useful if your system has direct relationships with businesses (B2B) and are offering Authvia products to your Merchant's. It may also be useful as an enterprise merchant and want to isolate different parts of your business from one another.

See:

🚆 Creating Merchant authentication token with Partner Credentials

Learn how to create merchant authentication tokens using partner credentials for multi-tenancy scenarios.

View Tutorial →

Want a recipe in your language?

Send an email to [email protected] and let us know what example, and what language. You can also utilize the built in API request builder of our references, which allows not only different languages, but different libraries within each language.


What’s Next