Use the Postman Collection

Explore the Global API and test payment flows in the Sandbox with Getnet's ready-made Postman collection.

Before you begin

Before you import the collection, make sure you have the following:

Step 1: Import the collection

Import the collection file into Postman to load the requests.

  1. In Postman, click Import.
  2. Drop or select the collection file.
The collection appears in the sidebar, under Collections. All its folders sit inside the SEP folder.
The collection variable URL_SANDBOX already holds the Sandbox base URL, https://api-sbx.globalgetnet.com, so you don't need to set it.

Step 2: Create an environment

Create a Postman environment to hold your credentials and seller details.

  1. In the sidebar, select Environments and create a new environment. Name it, for example, Getnet Sandbox.
  2. Add these variables:
    VariableValueRequired
    CLIENT_IDYour Sandbox client_id.Yes
    SECRET_IDYour Sandbox client_secret.Yes
    SELLER_IDYour seller ID.Yes
    currencyThe currency of your seller's country: ARS, BRL, CLP, MXN, or EUR.Yes
    countryYour seller's country code: AR, BR, CL, MX, ES, or PT. Card verification and subscription requests use it.No
    document_typeThe customer's document type. Antifraud and 3D Secure requests use it.No
    document_numberThe customer's document number. Antifraud and 3D Secure requests use it.No
    EMAIL_CUSTOMERThe customer's email address. Antifraud and 3D Secure requests use it.No
  3. Save the environment.
  4. Select it in the environment selector, at the top right of Postman.

Variable names are case-sensitive. Type them exactly as shown.

You don't need to create the other variables the collection uses, such as token, number_token, and payment_id. The collection's scripts create and fill them as you send requests.

Step 3: Get an access token

Every request needs an access token. Generate one before you send other requests.

  1. Open SEP > Seller authentication > Access Token Generator.
  2. Click Send.
The response returns an access_token. The collection saves it to the token variable, and every other request sends it automatically.
The token expires after about 1 hour. If a request returns 401 Unauthorized, send Access Token Generator again.

Test it

Send a test payment to confirm your setup works. You tokenize a test card, authorize a credit payment, and check its status.

  1. Open SEP > Card tokenization / Vault > Card token Generator and click Send. The collection saves the card token to number_token.
  2. Open SEP > Simple payment > Payment authorization CREDIT and click Send. A successful payment returns status set to APPROVED. The collection saves the payment_id and payment_method.
  3. Open SEP > Simple payment > Payment info and click Send to check the payment status.
The Card token Generator request uses a test card that works only in Brazil. For other countries, replace card_number in the request body with a card for your seller's country from Test cards.

Explore the collection

Each folder inside SEP covers one feature:
FolderWhat it covers
Seller authenticationAccess token.
Card tokenization / VaultCard tokens, saving cards to a customer, card verification, and listing and deleting saved cards.
Card token TSPCard tokens for network tokenization.
Simple paymentCredit and debit payments, installments, capture, cancel, and payment info.
payments with AntifraudThe same payment flows, with antifraud data.
(AR and CL)QuotesInstallment quotes and payments with quotes, for Argentina and Chile.
Combined paymentsPayments split across more than one method.
Pre-authPre-authorization, adjustment, capture, and cancel.
SubscriptionCustomers, plans, subscriptions, and charges.
3DS3D Secure card token, enrollment, validation, and payment with 3D Secure data.
BinlookupCard BIN lookup.
BoletoBoleto payments, for Brazil.
PIXPix QR code payments, for Brazil.

To see which features have limits in the Sandbox, check the feature availability table on the Sandbox page.

Next steps

After your first test payment, continue with these pages:

  • Follow the Quickstart to send the same requests from the command line.
  • Learn how tokens and headers work in Authentication.
  • Look up error codes in Errors.