Other

Uptick Data Extractor

Vern's Uptick extractor imports a new user's other data — invoices, products, users, and projects — into your product through a single managed migration, handling Uptick's auth, pagination, and rate limits for you. It's built for teams onboarding customers off Uptick who want their data in your app from day one.

Start migration

Browse all extractors

Uptick

SaaS API (REST)

Managed auth, retries, and throttling

Normalized JSON, CSV, and DB-ready output

Cleaned JSON, CSV, and DB-ready output

Export coverage

Know exactly what Vern pulls before you migrate.

Objects Vern extracts

Vern extracts the full set of queryable Uptick objects (49 total), including: Accreditations, Accreditationtypes, Appointments, Assets, Assettypes, Assettypevariants, Billingcards, Billingcontractlineitems, Billingcontracts, Branches, Clientgroups, Clients, Contractors, Costcentres, Creditnotelineitems, Creditnotes, Defectquotelineitems, Defectquotes, Invoicelineitems, Invoices, Products, Projects, Properties, Purchaseorderbilllineitems, Purchaseorderbills, Purchaseorderdockets, Purchaseorderlineitems, Purchaseorders, Remarkevents, Remarks, Rounds, Routines, Routineservicelevels, Routineserviceleveltypes, Routineservices, Routineservicetypes, Servicegroups, Servicequotedoandchargelineitems, Servicequotefixedlineitems, Servicequoteproductlineitems, Servicequotes, Servicetasks, Subtasks, Suppliers, Task Profitability, Taskcategories, Tasks, Tasksessions, and Users. All of these support incremental change tracking, so syncs pull only what changed.

Output schema

Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.

Where it can land

Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another other system (Aviationstack, Bluetally, Breezometer) when a user is switching tools.

Source details

Built for the source type shown above, with extractor content refreshed from the collection record.

Managed by Vern

The details you normally have to build yourself.

Authentication

OAuth 2.0 (Authorization Code flow). Your new user authorizes Uptick once during onboarding — their credentials never touch your code. Uptick access tokens are short-lived and refresh tokens roll on the provider's own schedule, so Vern manages the full token lifecycle and refresh and the import never drops midway.

Pagination

Vern detects and handles Uptick's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.

Rate limits and gotchas

Uptick enforces its own API rate limits. Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.

OAuth-based sources expire access tokens frequently and require a working refresh flow — a dropped refresh is the most common cause of a half-finished import. Vern owns the refresh loop so a new user's onboarding completes even on a long extraction.

API quickstart

1. Create a migration for Uptick
curl -X POST https://app.vern.so/api/v1/migrations \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Uptick → Postgres", "source": "Uptick" }'
→ { "migration_id": "mig_..." }
2. Generate the extraction recipe (pulls live via the Uptick API)
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "generate", "extract_via_api": true }'
3. Run the approved extraction
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "execute" }'
4. Download the normalized CSV export
curl https://app.vern.so/api/v1/migrations/$MIGRATION_ID/exports/{template} \
  -H "x-api-key: $VERN_API_KEY" -o uptick_export.csv

A cleaner way to extract without rebuilding source-specific plumbing.

View docs

Common questions

Can I keep a user's Uptick data in sync after the first import? Yes — 49 Uptick objects support incremental change tracking, so after the first full import Vern pulls only what changed on re-run.

Can I move a user from Uptick to Aviationstack? Yes — Vern normalizes the Uptick data model into typed tables that map cleanly onto Aviationstack and into your own product.

What does it cost to read the Uptick API? Uptick's own API access follows Uptick's pricing/plan; Vern is billed separately per import. Check Uptick's developer docs for their current limits.