Article sections

    About DSU

    Direct Scan to URL (DSU) enables the codeREADr mobile apps to post scans directly to your server. Likewise, it enables your server to post the scan response directly back to the app. No scan or response data is posted to codeREADr’s server.

    This type of service has the benefits of Postback URL with data security. Also, it enables the use of the codeREADr apps with local area networks. This is useful when you have firewall restrictions or unstable Internet connectivity.

    Please look here for developer instructions and here for helpful hints.

    Option 1: Receiving server responds to the scan

    After selecting “Scan to Third Party Server” check the option to “Skip our server and go directly to yours” when creating the service.  Then the scan is posted directly from the mobile app to your local or cloud server and your server responds directly to the app.

    DSU Service

    Option 2: Offline record scans or validate scans

    Instead of creating a “Scan to Third Party Server” service you can alternatively create a standard “on-device” record or validate scans service type with or without an on-device database. You would use the DSU method but the scan response (valid, invalid, response text) would be seen by the user before the receiving server receives the post.

    So why is this valuable? One of the main benefits of using this method is an “instant” response because there’s no LAN or Internet latency delays. Also, the app can even work offline. However, once each scan hits the receiving server it must still respond to clear the record from the device.

    dsu advanced setting
    in Developer APIs