Create Journey Application Batch
Changed onCreate a batch of journey applications by passing in a list of entities, grouped into different applications by the multi_entity_application_batch_key that can be optionally supplied for each entity
Request
- Base URLhttps://sandbox.alloy.co/v1
- Auth
- OAuth 2Client credentialsToken URL/oauth/bearer
- or HTTP basic
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Identifier of the journey
Headers
Evaluation header
Evaluation header
Specifies the journey version to create an application from. This includes drafts and inactive versions. If not supplied, the active journey version will be used.
Request body
Example request
{
"entities": [
{
"external_entity_id": "my_system_entity_id_123",
"data": {
"name_first": "John",
"name_middle": "Franklin",
"name_last": "Doe",
"birth_date": "1990-01-25",
"email_address": "john@alloy.com",
"gender": "male",
"ip_address_v4": "42.206.213.70",
"addresses": [
{
"type": "primary",
"line_1": "41 E. 11th",
"line_2": "2nd floor",
"city": "New York",
"state": "NY",
"country_code": "US"
}
],
"meta": {
"user_type": "vip"
}
},
"entity_type": "person",
"branch_name": "my_person_branch_name",
"entity_token": "P-1GoQALm40nPQSp7UVTJS",
"auto_decision_node_outcomes": {
"Manual Review": "approved",
"Authy": "approved",
"23489243289": "denied"
}
}
]
}Response
Success
Changes
- breaking
added to the
/request propertyallOflist - warning
removed from the
/request propertyallOflist - info
added the new optional
headerrequest parameteralloy-journey-version - info
added the media type
application/jsonfor the response with the status - info
added the media type
application/jsonfor the response with the status - info
added the media type
application/jsonfor the response with the status - info
added the media type
application/jsonfor the response with the status - info
added the media type
application/jsonfor the response with the status
- breaking