The borrower-facing intake surface, and the integration that carries an application from it into the loan file.
The point of sale is where a borrower starts. What arrives from it is an application in the intake system's own shape, and the integration maps it into the canonical model so the verification and pricing products can run against it.
The operations below come from the adapter service that routes the origination system, the point of sale and the closing surface together — the three places a loan file crosses a system boundary, deliberately behind one contract.
{
"collection_id": "e4502ed2-8df8-4b8f-84bd-a1097e999a77",
"message": "When ready, data will be available under the following collection_id. Use this new collection_id to get the execution status."
}
Parameters
1
Parameter
Type
Example
Description
x-api-keyrequired
stringheader
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Authorization key
Request bodyapplication/json
3 fields
Field
Type
Description
transaction_idrequired
string
Transaction ID
collection_idrequired
string
Collection ID
partner_namerequired
string
—
Response 200application/json
2 fields
POS request created successfully.
Field
Type
Description
collection_id
string
Collection ID
message
string
Message
GET/pos/elements
Retrieve Elements
get-pos-elements
Retrieve Elements provides a list of the elements needed to invoke a partner product.
Parameters
1
Parameter
Type
Example
Description
x-api-keyrequired
stringheader
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Authorization key
Response 200application/json
1 fields
Elements needed for request.
Field
Type
Description
elements
object
List of elements
POST/pos/elements/complete
Validate Collection
post-pos-collection-complete
Validate Collection validates that a collection contains all of the elements needed to invoke a partner product.
Parameters
1
Parameter
Type
Example
Description
x-api-keyrequired
stringheader
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Authorization key
Request bodyapplication/json
1 fields
Field
Type
Description
collectionrequired
object
—
Response 400application/json
2 fields
Collection is invalid.
Field
Type
Description
message
string
Error message
errors
object
List of elements that are missing
Other responses
200
POST/pos/lexicon/elements
Retrieve Lexicon Elements
You can retrieve element structure by providing specific element names (XPaths).
Request bodyapplication/json
1 fields
Field
Type
Description
elements
string[]
An XPath to a valid staircase element
Other responses
200
GET/pos/status/{transaction_id}/{collection_id}
Retrieve Status
get-pos-status
Retrieve Status checks status of your request.
Possible statuses:
Create Transaction creates a transaction in Staircase.
A transaction in Staircase is an acknowledgement that you want to call a Staircase product. It's a container for everything associated with that product invocation, and is correlated with a collection related to the product (e.g. a document).
You need to create a new transaction every time you want to connect with a Staircase product. Staircase then associates everything, from a data and API execution standpoint, to that transaction.