PassEntryโ€™s Scans API lets you validate passes at physical locations, whether for event access, membership verification, ticket validation, or loyalty program check-ins. By default, PassEntry handles validation internally, but for businesses needing more flexibility, third-party validation allows you to define your own rules and logic.

What is Third-Party Validation?

With third-party validation, your system takes full control over how passes are validated. Instead of PassEntry checking pass validity, every scan is sent to your own endpoint, where you decide the logic.

PassEntry Internal vs. Third-Party Validation

FeaturePassEntry Default Validation ๐Ÿ“ฆThird-Party Validation ๐Ÿ”ง
Setup๐Ÿ“ฆ Out-of-the-box, no setup required๐Ÿ› ๏ธ Requires a custom validation endpoint
Validation Logic๐Ÿ”’ PassEntry validates against its own databaseโš™๏ธ Your system defines all validation rules
Scan Value Format๐Ÿ”‘ Must be pass UUID or external ID๐Ÿ“œ Can contain any data or combination of values (e.g., customerID-promoCode)
Reader Instructions๐Ÿ“ก Pre-defined reader instructions๐ŸŽจ Full control over instructions (e.g., messages, LED colors, sounds)
Scans Logging๐Ÿ“Š Yes๐Ÿ“Š Yes
Support for NFC/Barcode๐Ÿ“ก NFC & Barcode (only if barcode is configured as pass UUID)๐Ÿ“ก NFC & Barcode
Association to the pass๐Ÿ”„ Yes๐Ÿ“ก Only if passId provided by your endpoint
Current Compatibility๐Ÿ”— Works with VTAP & PassEntry Reader๐Ÿ”œ Currently only supported on PassEntry readers (VTAP support coming soon)

How to Enable Third-Party Validation

To start using third-party validation, follow these simple steps:

1. Ensure You Have a Reader Set Up

Third-party validation is currently supported only on PassEntry readers. If you havenโ€™t set up a reader yet, follow this guide to do so.

2. Update Your Reader Configuration

  1. Go to PassEntry Dashboard โ†’ Readers โ†’ Reader Configuration.
  2. Find the Validation Settings section.
  3. Change the validation type to Third-Party.
  4. Enter an HTTPS URL of your third-party validation endpoint (this is where PassEntry will send scans for validation).
  5. Include a Bearer token (this is a token that the reader will send to your endpoint to authenticate itself).

3. Apply Changes & Activate Third-Party Validation

  • Once you update the settings, the reader will log out automatically.
  • On the next login, it will use the new validation settings, sending all scans to your third-party endpoint.
  • After validation, scans will still be logged in PassEntry for tracking and reporting.

How It Works

  1. A pass is scanned using a PassEntry reader (via NFC or barcode).
  2. Instead of PassEntry validating the pass, the scan is sent to your third-party endpoint.
  3. Your system processes the validation using custom business logic.
  4. The reader receives a response from your system and displays any necessary instructions (e.g., โ€œAccess Grantedโ€ or โ€œInvalid Ticketโ€).
  5. The scan is logged in PassEntry for visibility and reporting.

Third-Party Endpoint Structure

Your custom validation endpoint must be able to receive scan data and respond with validation results.

Reader Request Format

{
    "scan": {
        "scanValue": "some-scan-value",
        "readerId": "passentry_reader_id",
        "scanType": "nfc"
    }
}
scan
object

Your Endpoint Response Format

{
    "validationResponse": {
        "status": "failed",
        "statusDetail": "Subscription expired",
        "passId": "65844fnrjkfjfkel4h4j23",
        "readerInstructions": {
            "message": "Sorry, we can't let you in"
        }
    }
}
validationResponse
object