1. Home
  2. Docs
  3. Data Subscriber API Documentation
  4. Quick Start | Sandbox Usage

Quick Start | Sandbox Usage

Our Sandbox is a safe environment that enables you to test the features of Pentadata’s APIs. Sandbox usage is free of charge, but all accounts have to be approved by us first. You can request access at this link, or by getting in touch with us.

Exposed Data

To ease your development and testing, the sandbox environment comes with preloaded data. You can use it to link card and bank accounts and to onboard consumers, all by using the API endpoints that we provide.

The dataset available in the sandbox is very realistic, but it’s computer-generated and does not reflect any actual personal information.

You can also send data to the sandbox endpoint that is not present in the preloaded dataset. That will work just fine, but it’s likely to be less interesting (you will get empty responses most of the time).

For example, you can link any of the cards that is in the dataset Then you can test our GET /transactions endpoint on that card, which will return some data. If you add a card that’s not in the dataset, you can still use the /transactions endpoint, but it will return an empty list.

The dataset can be downloaded clicking on this link: sandbox_sample

The sandbox url is https://signal.pentadatainc.com

Pentadata Signal

On the same line, the dataset also comes with computer-generated consumer information, that you can use with our /persons endpoints. These endpoints allows you to verify the identity of an individual and onboard them in your profile, as well as to view aggregated signals about their income.

Once a consumer is onboarded, you get access to a signal of information about their spendings via our GET /spendings endpoint. This endpoint can be fully explored with the sandbox account.

Cards & Banking | Real-time & Historical transactions

Our production API gives access to any person payment transactions, from debit and credit cards as well as from bank accounts.

This is easy to test in the sandbox, so that you can develop your program to digest the data returned by our API. Once again, you should use data from the datasample, to get other than empty responses.

Categorize Merchants

Another feature that we expose in the sandbox is the Merchant Categorization. This endpoint solves that long-standing problem of understanding what category a transaction belongs to just by looking at the text string on the card statement. We expose this endpoint on POST /merchants/mcc.

Identify Merchants

And while you’re dealing with merchants after MCC, you can test our machine-learning based product Merchant Sight! This is a API endpoint that identifies the correct merchant just looking at the text string on the card statement and, in a very high number of cases, it also finds the correct location, Google Maps ID and Yelp ID. This is available on POST /merchants/sight.

Customer Identity Verification

The endpoints to verify a customer identity (/persons/authenticate and /persons/verify) returns computer-generated knowledge-base authentication questions.

These are questions in the same format that you will receive in production, but in the sandbox will be the same for all persons that you see in the sample data in the excel file above.

Note: The correct answers in the sandbox are “0001A” and “0002A”.


Our Pay product is fully testable within the sandbox. In case you forgot, this is the product that you can use to send money to your customers.

The userflow in the sandbox is exactly the same you would use in production:

  1. Use POST /pay to register a payment method for a Person.
  2. Use /pay-verify to verify the account. The correct amount in the sandbox are 0.04 and 0.07.
  3. Use /pay-send to send money!

Exposed Endpoints

To summarize, here a list of the endpoints available in the sandbox, with links to their documentation page.


How can we help?