Impressions
Get Impression
Retrieve detailed information about a specific QR code scan
GET
Retrieve detailed information about a specific QR code scan (impression) by its unique ID. Use this endpoint to fetch complete scan details including timestamp, device information, and associated poster.
Overview
The Get Impression endpoint returns comprehensive information about a single QR code scan. This is useful for:- Viewing detailed scan information
- Linking impressions to referrals
- Debugging scan issues
- Building impression detail pages
- Tracking individual user journeys
Authentication
This endpoint requires authentication using a Bearer token in the Authorization header:Path Parameters
The unique identifier of the impression you want to retrieve. This ID is returned when a QR code is scanned and is used when creating referrals.Example:
imp_123abcRequest Example
Response
The API returns a detailed impression object:Unique identifier for the impression. Use this ID when creating a referral.
ID of the poster whose QR code was scanned.
ID of the program this impression belongs to.
ID of the student ambassador who placed the poster.
ISO 8601 timestamp of when the QR code was scanned.
User agent string of the device that scanned the QR code. Useful for identifying device type and browser.
IP address of the device that scanned the QR code (if available).
Additional metadata about the scan, such as device type, location, or custom fields.
Response Example
Error Responses
Unauthorized - Invalid or missing API key
Not Found - The impression with the specified ID does not exist
Use Cases
Creating a Referral from an Impression
When a user signs up after scanning a QR code, use the impression ID to create a referral:Viewing Impression Details
Fetch impression information to display in a detail view:Building Impression Detail Component
Create a React component to display impression details:Best Practices
- Link impressions to referrals - Always use the impression ID when creating referrals
- Cache impression data - Impression information doesn’t change after creation
- Handle 404 errors - Always check if the impression exists
- Track device information - Use user_agent and metadata to analyze device types
- Monitor scan timing - Use scanned_at to analyze peak scan times