Reference & Lookup Data · Integration
CodeREADr
Add CodeREADr to your product for your customers, and give your AI agents governed access to it.
CodeREADr exposes one endpoint at api.codereadr.com/api/ where behaviour is selected by section and action query parameters, for example section=services&action=retrieve, and responses come back as XML rather than JSON. The api_key parameter is mandatory on every call and its absence returns HTTP 200 with an XML error code 101 in the body, so the HTTP status is not a usable success signal and the response has to be parsed before anything is trusted. The sections are services, databases, users, scans and questions, and the model is that a service defines how a scan is processed and what the device shows, while a database holds the barcode values a scan is validated against, so loading valid codes and configuring validation behaviour are two separate operations against two different sections. Scans are pulled in bulk for reporting and carry the device user, timestamp and any answers to post-scan questions, and CodeREADr can also push each scan to a postback URL as it happens, which is the better option where near real-time matters. Of the available categories Reference & Lookup Data is the closest fit, since the product exists to look a scanned value up and return a validation result. fastn holds each customer's API key, keeps scan pulls scoped to their account and absorbs parameter changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own CodeREADr account so the codes your product issues are loaded into their validation database
Push a fresh list of valid ticket or asset codes before each event and retire the previous set
Pull scan records to reconcile attendance or asset checks against what your system expected
Show a customer which of their issued codes have been scanned, when and by which device user
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to list codes issued for an event that were never scanned, with the query audited per tenant
Have an agent upload a new batch of valid codes to a named database after an approval step
Let an agent report duplicate scan attempts by device user for a fraud review
Example prompt
How many of the tickets we issued for Saturday were actually scanned at the door?
Set up CodeREADr in 4 steps
- 01Enable the CodeREADr connector from your fastn dashboard.
- 02Have each customer authorise their own CodeREADr account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the CodeREADr integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a CodeREADr integration without building it. Your customers connect their own CodeREADr account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a CodeREADr update is not your on-call problem.
- One integration serves your product and your agents. The same governed CodeREADr connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to CodeREADr, across other categories.
Salesforce
HubSpot
Notion
SnowflakeCodeREADr integration FAQ
How do I add a CodeREADr integration to my product?
Enable the CodeREADr connector in your fastn dashboard, then let each customer authenticate their own CodeREADr account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no CodeREADr client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own CodeREADr account?
Yes. Every connection is scoped to the individual customer, so each authorises their own CodeREADr account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this CodeREADr integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to list codes issued for an event that were never scanned, with the query audited per tenant
Who maintains the CodeREADr integration?
fastn does. When CodeREADr changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a CodeREADr lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should CodeREADr results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. CodeREADr is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the CodeREADr integration?
A common starting point: let a customer connect their own CodeREADr account so the codes your product issues are loaded into their validation database. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the CodeREADr integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding CodeREADr does not change your per-connector cost. You can start free with 3 connected accounts.
Add CodeREADr to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.