Postman can build a collection of API requests and has a friendly interface for walking the API specification. This article aims to accelerate your timeline for productively exploring the API and developing an integration.
About the Management API
The OpenZiti controller provides an edge-management API for creating, reading, updating, and deleting (CRUD) OpenZiti resources, e.g., Services, Edge Router Policies, etc. The simplest way to use the edge-management API is through the ziti CLI or the console.
What about the Client API?
The edge-management API is distinct from the edge-client API. Edge SDKs use the edge-client API to authenticate and find services and routers. The OpenZiti Controller can be configured to provide both APIs on the same server port. Whether the two APIs are combined or split, their URL paths are discrete. You can learn more about both APIs in the developer references.
Generated Clients
Before you write an edge-management client, could you use the Go client (go-swagger) or Python client (openapi-generator) generated from the specification? Those might save you some typing if you can adapt them to your purpose.
Get the OpenAPI 2.0 Specification
The best place to get the specification is your running OpenZiti Controller. That way, you know the specification matches the version you are using. The controller publishes the spec in the edge-management API at the path /edge/management/v1/swagger.json. There's also a built-in API reference website at the path /edge/management/v1/docs. If you don't have a running controller, browse the latest spec and API reference on the docs site.
Import to Postman
Click the "Import" button on your Postman Workspace and provide a file path or URL to the OpenZiti edge-management API specification.
Create a Postman Environment
Create a Postman environment for this API. Here's the Postman help for reference.
Add a variable "baseUrl" and assign the current value of your management API's URL. For example, if the API is listening on local port 1280, assign https://localhost:1280/edge/management/v1.
Add another variable named "apiKey" without any value. This variable will be assigned by the "authenticate" request's test script.
Customize the Authenticate Request
Modify the "authenticate" request to store your API session token in your Postman environment. All subsequent requests will use this bearer token.
In the collection of requests that Postman generated from the spec, find the request named "authenticate" and select the POST operation named "Authenticate via a method supplied via a query string parameter."
In the "Params" tab of the request, ensure you have a query param named "method" with the value "password".
Ensure the request path of the operation is now showing {{baseUrl}}/authenticate?method=password.
In the "Tests" tab of the request, add this Javascript.
var jsonData = JSON.parse(responseBody);
pm.environment.set("apiKey", jsonData.data.token);
In the "Body" tab of the request, add JSON like this with your correct username and password for the management API.
{
"username": "admin",
"password": "Otz2q5gnYVSTkza2aJ1EUq72hGGiFvmZ"
}
Click the "Send" button.
You should have received an HTTP OK (200) response from the management API. Now you can send any other requests in the collection, and they will automatically use the token from your Postman environment.
