Using Postman

For a quick overview of the feature, here is Postman's own walkthrough:

Import the collection

In Postman, choose Collections, then Import:

Give it this URL:

https://api.wall.et/swagger.yaml

Postman verifies it as a valid OpenAPI 3.0 document:

Click import, and you should see a confirmation:

The full Wallet API now appears in your sidebar as a collection:

The folders group endpoints by feature and function. Expand any of them to see the endpoints within:

Re-import the same URL whenever you want to pick up newly shipped endpoints. The specification is generated from the running API, so it is never out of date. (https://api.wall.et/swagger.json serves the same specification as JSON if you prefer it.)

Add your API key

Most endpoints require authentication. Open a request, go to the Headers tab, and add a header named access-token with your key as the value:

Do not have a key yet? See Creating an API Key.

Set the header once at the collection level (Collection > Edit > Headers, or an access-token collection variable) and every request inherits it. That is less error-prone than pasting the key into each request, and it keeps your key out of individual request tabs when you export or share a collection.

Test your connection

A few system reference endpoints need no key, which makes them the right first call: if this works, your network path to us is good, and anything failing afterwards is about your key rather than your connection.

Send a GET to https://api.wall.et/system/countries/all:

Now try an authenticated request, for example GET /v2/dashboard/count/visitors. A 200 means your key is working. A 401 means the header name or the key value is wrong; the header must be exactly access-token.

...and voila! You are connected to the Wallet API, with every endpoint in this reference one click away in your sidebar.

We cannot wait to see what you build.

Welcome aboard.