[To bypass our servers, please see Direct Scan to URL (DSU).]
With Postback URL services, each scan posted to codeREADr’s servers from the codeREADr app is immediately posted to an account holder’s server. The account holder’s server then posts back a response to codeREADr’s server which then posts that response back to the app. The scan record is saved on the codeREADr servers.
Benefits: You can validate scanned data on your own servers rather than CodeREADr’s server. You can direct scans to your own server rather than using our APIs. You can use this option for databases that are constantly changing when additional data processing is required before posting the response back to the app.
There are two ways to enable PostbackURL: Postback as a Service and Postback as an Advanced Setting. The main difference is that the former relies on your server for validation. While the latter can do that too, it also gives you two other options. First, you can use our servers for validation and post the resulting scan to your server, including the option to Postback a specific response to the app user. Second, you can post scan records to your server when it doesn’t require validation. Then, you can choose to return XML with each post (Full Postback) or to simply receive the scan record without requiring return XML from your server (Receiver Only).
Postback and DSU services have designated IP addresses for whitelisting, if necessary. You can find those addresses on the Account/API page.
Option 1: Post back as a Service
Option 2: Post back as an Advanced Setting
If you plan to post responses back to the app (Post back as a Service or Full Post back) or want to totally bypass codeREADr’s servers with our Direct Scan to URL service type, please click here.
Example: Ticket Validation, Full Post back
First, you create a codeREADr service configured with your validation URL (we call it a Postback URL). It acts as an adapter between our system and your system. Secondly, we will HTTP POST the scanned value (e.g. a ticket ID) to your URL. Then, the URL will validate the ticket and reply with XML specifying the ticket is Valid (status=1) or Invalid (status=0).