[Guide] Use Postman Collections with Pragma Engine

Last updated: April 16, 2026

This guide walks you through setting up Postman to interact with the Pragma Engine API. By the end you will be able to authenticate as a player, operator, or partner and start making API calls against your Pragma backend.

1. Install Postman

Download and install Postman for your platform.

2. Import the Collection and Environment

  • Open Postman and click Import (top-left).

  • Drag in (or browse to) both of the following files from pragma-engine/platform/devenv/postman: 

    • PragmaDev.postman_collection.json — contains all Pragma API requests.

    • Localhost.postman_environment.json — contains environment variables pre-configured for a local backend.

  • Click Import to confirm.

3. Collection Structure

The collection is organized into three top-level folders:

  • Public — Unauthenticated endpoints such as the authentication requests described below. Start here.

  • Game — Requests targeting the Game backend, grouped by session type: RPC - Player, RPC - Operator, and RPC - Partner.

  • Social — Requests targeting the Social backend, with the same session-type grouping: RPC - Player, RPC - Operator, and RPC - Partner.

4. Select the Environment

In the upper-right corner of the Postman window there is an environment dropdown (it may say "No Environment"). Select localhost from the dropdown. This ensures every request uses the correct host, ports, and tokens.

5. Authenticate as a Player

  • In the left sidebar, expand the collection and navigate to Public > Player - AuthenticateOrCreateV2.

  • Click Send.

  • On a successful response, the request's built-in test script automatically saves the returned tokens into your environment variables:

    • test01PragmaPlayerGameToken

    • test01PragmaPlayerSocialToken

It also populates test01PlayerId, test01PragmaSocialId, and test01PlayerNameDiscriminator from the decoded JWT. Subsequent player requests in the collection reference these variables, so you can start making authenticated player calls immediately.

6. Authenticate as an Operator

  • Navigate to Public > Operator - AuthenticateOrCreateV2.

  • Click Send.

  • The test script saves:

    • test01PragmaOperatorGameToken

    • test01PragmaOperatorSocialToken

   Operator requests in the collection use these variables for authentication.

7. Partner Endpoints

Partner tokens (test01PragmaPartnerGameToken and test01PragmaPartnerSocialToken) are already set in the environment with long-lived JWTs. No authentication step is needed — partner requests will work out of the box.