Skip to end of banner
Go to start of banner

Validation API (and Inspection API)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

We’ll not provide separate examples for Inspection API since the two endpoints are essentially the same as their counterparts in Validation API.

Validate 1 - online validation

The response is shown for a valid validation of a ticket.
Endpoint: POST /api/v2/validation/74f5a450-f57a-416f-9f1d-54f371dea08c?mtb=v2F2Q…

 Request
 Response

Validate 2 - offline batch validation

Endpoint: POST /api/v2/validation

 Request

Retrieve all tickle macros

Endpoint: GET /api/v2/ticklemacros

 Response

Retrieve tickle macros by serial

Endpoint: GET /api/v2/ticklemacros/1

 Response

Retrieve blacklist

Endpoint: GET /api/v2/blacklist?blacklistEntryId=0

 Response

Fraudcheck

The fraudcheck call results in a velocity calculated as follows:

  • The caller provides a reference to a MTB, a time and geographical position

  • The callee looks up the time and geographical position of the last ticket event for the given MTB

  • The callee returns the calculated velocity given the time/geopos

The response must only be given once per validation event and client. Velocity less than 1 km/h or distances less than 1 km shall render 0 km/h.

The resulting velocity is used to determine possible fraud. If the velocity is higher than any available mode of transportation, the ticket has most likely been copied and presented at different locations.

Endpoint: GET /api/v2/fraudcheck

 Request
 Response
  • No labels