Introduction: Sandbox

The Akoya sandbox allows you to make calls to Akoya APIs for tokens and data.

Every data request in the Data Access Network requires an ID token. To test in sandbox, you must log in as a user and complete the account selection and consent flow process to retrieve an ID token. Akoya has provided a mock data provider for your testing use.

What is sandbox?

Sandbox is a service provided by Akoya for testing Akoya endpoints. Mikomo, a mock data provider, is the only provider available using sandbox. Mikomo includes a test library with representative samples from various data providers. The data available from these users is detailed in the Catalog below.

We recommend using Postman for testing. For more information on using Postman, see: Postman collection

Requirements for sandbox:

• An app created in the Data Recipient Hub
• 5 TPS (transactions per second) rate limit
• The following parameters:

Mikomo catalog

Mikomo users are created with static, example response payloads. These payloads are representative and can be used to understand the type of data you may receive through the Data Access Network. Sandbox accounts may also be used for your integration and testing needs. For testing support, we’ve included a variety of Akoya products, provider accounts types, account statuses, transaction loads, and error states.

Note: for all test users, the username and password are the same.

All supported data elements

The mikomo_7 user includes all account categories and data elements available through the Data Access Network.
(See details below)

Products

If you need to test Akoya products with Mikomo users, this chart is a quick way to determine which user might work for you. This chart also includes additional scenario information you might need for integration/testing use.

Account types

While there are a number of account types supported by our data providers, this chart includes a selection of account types for your reference. A sample of other account types are listed by Mikomo user below.

Account details

mikomo_1

8 accounts

mikomo_2

8 accounts

mikomo_3

38 accounts

mikomo_5

3 accounts

mikomo_6

10 accounts

mikomo_7

5 accounts

Includes:

• customers
• paymentNetworks
  • account 1602364511

mikomo_9

1 account

Includes:

• customers
• paymentNetworks
  • account 47320722f1e9340a8f8ead1e38bdbc215b0866d0ad83472c6777923499a74429

mikomo_10

6 accounts

Includes:

• customers
• paymentNetworks
  • account g833202fb0866d0ad83472c429
  • account 33fbd9e5-9cc3-3d7d-15b3-70d97d87ca1d

mikomo_11

1 account

Includes:

• paymentNetworks
• customers
• statements

mikomo_2023

6 accounts

This Mikomo user was created for testing the transactions endpoint. The g833202fb0866d0ad83472c429 checking account should always return recent transactions and has several months of history for testing pagination and date filtering. All of the mikomo_2023 accounts are generic (not provider-specific) and are detailed below.

• customers
• paymentNetworks
  • account g833202fb0866d0ad83472c429
  • account 33fbd9e5-9cc3-3d7d-15b3-70d97d87ca1d

Provider data

📘

Notice

Representative test users are created with live data from each data provider and collected through the Data Access Network. However, this sample data does not include all possible responses.

To find more information on test users, refer to each data provider's documentation section in the Data Recipient Hub.

Error testing

Some errors are difficult to replicate. For instance, there is no way for you to revoke an end-user’s consent via their bank’s app or website to test the errors that would result in your app. When data is requested for these users, the result will always be an error.

To test with these Mikomo users, go through the consent flow as usual to obtain an ID token. Then, any data call will result in the errors listed below.

Note: username and password are the same.

Change log