Decide routing
Changed onEvaluate the existing hybrid routing pipeline using the flat request contract. Existing rule evaluation, SR feature gates, A/B experiments and fallback behavior apply.
Request
- Base URLhttp://localhost:8080
- URLhttp://localhost:8080/decide
- Auth
- HTTP bearer
- or API key in header x-api-key
Request body
Response
Routing decision. Connector order and account IDs are preserved from hybrid routing. An account ID can be null when a legacy rule identifies only a gateway.
Example response
{
"debit_routing": {
"co_badged_card_networks_info": [
{
"network": "NYCE",
"saving_percentage": 1.2
}
],
"issuer_country": "US",
"card_type": "Debit"
}
}Changes
- breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - info
added the new optional request property
- info
the request property
///became nullable - info
the request property
///became nullable - info
the request property
///became optional - info
the request property
///became optional - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- breaking
- info
endpoint added
- info