Reftab setup

ConfigView reads your Reftab asset register through Reftab’s REST API, using an API key pair (a public key and a secret key) that you generate in Reftab. Every request is signed with the secret key; the secret itself is never sent. You will end up with 2 secrets in ConfigView (REFTAB_PUBLIC_KEY, REFTAB_SECRET_KEY) when setup is complete.

Scope of this integration today. ConfigView ingests Reftab’s asset register and who holds what: assets (with serial numbers), accessories, licences and the applications they belong to, loans (check-outs), borrowers and Reftab users, requests, reservations, maintenance and verifications. ConfigView only reads. It never checks items in or out or edits records.

Step 1: Open the Reftab page in ConfigView

Open ConfigView in a second browser tab and leave it open: https://{companyname}.configview.com/admin/integrations/reftab Reftab shows the secret key once, when you create the pair, so paste it straight into ConfigView instead of keeping it in a notes file.

Step 2: Create an API key pair in Reftab

Sign in to Reftab as the user whose access ConfigView should have. Use a shared service account with an Admin role (for example integrations@), not a person’s own login. See Which user owns the key below
Open Settings and find the API section
Create a new API key. Reftab shows a public key and a secret key
Switch to the ConfigView tab and paste each one into its row under Credentials, clicking the save icon on each:

Reftab shows	Paste into ConfigView as
Public key	`REFTAB_PUBLIC_KEY`
Secret key	`REFTAB_SECRET_KEY`

Which user owns the key

A Reftab API key acts as the user who created it and sees only what that user’s role can see. If the user can’t view licences, or only some locations, ConfigView can’t either, and the gaps don’t look like errors. They show up as fewer rows. An Admin role sees everything. Reftab ties the key to that user. If the user is disabled or deleted, collection stops, so a service account that won’t leave is the safer owner. You can revoke a key from the same Settings page at any time.

Step 3: Connect and verify

Back on https://{companyname}.configview.com/admin/integrations/reftab, confirm both credentials show as saved
Click Connect. ConfigView creates its tables and schedules every collector at your default run time. Stop any you don’t want under Collectors:

Script	Notes
Assets	Every asset with category, location, status, serial number, current borrower and due date.
Accessories	Accessories and consumables: quantity, available, in use, reorder minimum, vendor.
Asset Categories	Categories, asset counts and the custom fields defined on each.
Locations	Every location and sub-location, flattened to one row each with its parent and depth.
Licenses	Licences, active and cancelled: seats bought and used, cost, expiry and cancellation dates.
Applications	SaaS applications tracked in Reftab, with vendor, owners, status, cost and roles.
Loans	Every check-out, open and returned, of an asset, licence, accessory or kit.
Borrowers	Everyone who can be lent equipment: borrowers and Reftab users in one list.
Users	Reftab user accounts, enabled and disabled, with role.
Requests	Asset and accessory requests in every state, with approval history.
Reservations	Reservations: upcoming, fulfilled and cancelled.
Asset Maintenance	Open and completed maintenance jobs per asset.
Verifications	Verifications sent to borrowers to confirm they still have an item, and their answers.

Click Verify now. The health check signs one request to confirm the key pair, then reads one record from each kind of data above.

If a check fails:

API key signature fails with 401. The two keys aren’t a matching pair, one was pasted with a stray character, or the key has been revoked. Create a new pair and paste both again.
A Read: check fails with 401/403. The key’s user has a role that can’t view that kind of record. Raise the role (Admin sees everything), or stop that collector if you don’t want it collected.
Health check passes but a table is empty. Re-run that script and check the run log. Requests, Reservations, Asset Maintenance and Verifications are legitimately empty if your team doesn’t use those Reftab features.

Data Tables

Once the scripts run, these tables are created in your database. Each includes a run_at column for historical tracking, and a raw column holding the full record exactly as Reftab returned it, including fields not broken out into columns.

Table	Source	Key Columns
`reftab_assets`	`GET /api/assets`	aid, title, category_id, category_name, location_id, location_name, status_id, status_name, status_loanable, serial_number, loan_id, loanee_email, loanee_name, checked_out_at, due_at, last_scanned_at, created_at, loan_period_hours, notes, details, depreciation
`reftab_accessories`	`GET /api/accessories`	accid, title, type, location_id, location_name, vendor, barcode, order_number, quantity, available, used, min_quantity, purchase_date, portal_visible, notes, details
`reftab_categories`	`GET /api/categories`	cid, name, asset_count, fields
`reftab_locations`	`GET /api/locations` (tree flattened)	clid, name, parent_id, depth, address, email, main_contact, can_have_assets, asset_count, license_count, expired_license_count, accessory_count, low_accessory_count, notes
`reftab_licenses`	`GET /api/licenses?status=all`	licid, title, application_id, vendor, licensee, seats, used, min_seats, cost, location_id, location_name, order_number, purchased_at, expires_at, cancelled_at, terminated_at, notification_email, notes, details
`reftab_applications`	`GET /api/applications`	application_id, name, vendor_name, vendor_website, category, status, website, cost, owner_uids, owners, roles, license_count, compliances, created_source, created_at, updated_at, description
`reftab_loans`	`GET /api/loans` (once per status: out, in)	lid, loan_group_id, status, item_type, aid, licid, accid, kid, title, category_name, location_id, location_name, loanee_id, loanee_user_id, loanee_email, loanee_name, loaner_email, returner_email, in_at, out_at, due_at, application_roles, notes, details
`reftab_loanees`	`GET /api/loanees`	person_key, record_type, lnid, uid, name, email, title, employee_id, disabled, details
`reftab_users`	`GET /api/subusers` (disabled, then all)	uid, name, email, role, activated, disabled, role_lock, details
`reftab_requests`	`GET /api/requests` (once per status)	rqid, status, requestor_email, requestor_name, email, uid, lnid, location_id, location_name, assigned_to, start_at, end_at, reason, notes, items, asset_ids, history, current_approvers, details
`reftab_reservations`	`GET /api/reservations` (once per status)	resid, status, item_type, aid, licid, accid, kid, title, location_id, location_name, loanee_id, loanee_user_id, loanee_email, loanee_name, reserved_by_email, start_at, end_at, notes
`reftab_asset_maintenance`	`GET /api/assetmaintenance` (open, then completed)	amid, mnid, maintenance_name, aid, asset_title, completed, assigned_uid, creator_uid, assigned, start_at, end_at, due_at, tasks
`reftab_verifications`	`GET /api/verifications`	vid, lid, status, loanee_id, loanee_user_id, creator_uid, created_at, due_at, submitted_at, asset, accessory, kit, response, notes

Things worth knowing

serial_number is read from your custom fields. Reftab has no built-in serial field. Each asset category defines its own, so ConfigView takes the first field whose name contains “serial” (or is “S/N”). If your categories call it something else, it stays in details and serial_number is empty. The serial is what lets ConfigView match a Reftab asset to the same machine in Kandji, Intune or CrowdStrike. Loans and reservations cover every state, not just current ones. Reftab’s lists filter by status, so ConfigView asks for each status in turn. To find who has what right now, filter reftab_loans on status = 'out', or read loanee_email on reftab_assets, which only shows the current borrower. Borrowers aren’t necessarily Reftab users. Reftab can lend equipment to people who never sign in. reftab_loanees lists both kinds together. record_type says which, and person_key keeps their two id spaces apart. reftab_users is the login accounts only. Disabled users are included and flagged. reftab_users.disabled = 1 marks accounts Reftab returned as disabled. Filter it out for current users. Thumbnails and image links aren’t stored. Reftab’s image URLs expire after 15 minutes, so they’d be dead links by the time anyone read them.

Platform

Integrations

Step 1: Open the Reftab page in ConfigView

Step 2: Create an API key pair in Reftab

Which user owns the key

Step 3: Connect and verify

Data Tables

Things worth knowing

​Step 1: Open the Reftab page in ConfigView

​Step 2: Create an API key pair in Reftab

​Which user owns the key

​Step 3: Connect and verify

​Data Tables

​Things worth knowing

Step 1: Open the Reftab page in ConfigView

Step 2: Create an API key pair in Reftab

Which user owns the key

Step 3: Connect and verify

Data Tables

Things worth knowing