Skip to main content
POST
Resolve a sandbox scenario

Authorizations

X-Access-Client-Id
string
header
required

Client ID

X-Access-Secret
string
header
required

Client Access Key

Body

application/json

The input a user would supply, to be resolved against your scenarios.

data_source
enum<string>

Data source to resolve against. Inferred from the supplied fields when omitted, the same way a write infers it.

Available options:
payroll,
docs,
financial_accounts,
education,
credit,
insurance
Example:

"payroll"

product
enum<string>

Product of the task being simulated. Scenarios pinned to other products are skipped.

Available options:
income,
employment,
deposit_switch,
pll,
insurance,
transactions,
assets,
admin,
credit,
education
Example:

"income"

username
string

The login the user would type.

Maximum string length: 255
Example:

"acme.salaried"

password
string

The password the user would type.

Maximum string length: 255
Example:

"s4ndb0x"

provider_id
string

Provider the connection would go through.

Maximum string length: 64
Example:

"adp"

company_domain
string

Company the connection would be made for.

Maximum string length: 128
Example:

"acme.com"

is_refresh
boolean | null

Whether the task would be a data refresh.

Example:

false

filenames
string[]

Filenames the user would upload. Document upload only.

Maximum string length: 255
Example:
ssn_last4
string

Last four SSN digits. Education and credit only.

Maximum string length: 4
date_of_birth
string<date>

Date of birth. Education only.

phone
string

Phone number, normalized to E.164 before matching. Credit only.

Maximum string length: 32

Response

The scenario that would answer the supplied input, and why it won.

scenario
object

A client-authored sandbox case - what it matches on, how it behaves, and the data it returns.

matched_on
string[]

Matcher fields the winning scenario actually constrained.

Example:
tier
enum<string>

Where the winning scenario came from.

Available options:
client
Example:

"client"