HR & Payroll

GreytHr Data Extractor

Vern's GreytHr extractor imports a new user's hr & payroll data — employees, employee bank details, employee pf & esi details, and employee qualifications details — into your product through a single managed migration, handling GreytHr's auth, pagination, and rate limits for you. It's built for teams onboarding customers off GreytHr who want their data in your app from day one.

Start migration

Browse all extractors

GreytHr

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 GreytHr objects (11 total), including: Employee Bank Details, Employee PF & ESI Details, Employee Qualifications Details, Employee Separation Details, Employee Statutory Details, Employees, Employees Categories, Employees Personal Details, Employees Profile, Employees Work Details, and Users List.

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 hr & payroll system (7shifts, Ashby, BambooHR) 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

Basic authentication (username + password / secret). Your user connects their GreytHr account once; Vern stores the credential encrypted and signs each request.

Pagination

Vern detects and handles GreytHr'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

GreytHr 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.

Basic-auth sources transmit credentials on every call and often lack granular scopes, so have your user connect a read-only account where possible. Vern stores the credential encrypted and never logs it.

API quickstart

1. Create a migration for GreytHr
curl -X POST https://app.vern.so/api/v1/migrations \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "GreytHr → Postgres", "source": "GreytHr" }'
→ { "migration_id": "mig_..." }
2. Generate the extraction recipe (pulls live via the GreytHr 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 greythr_export.csv

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

View docs

Common questions

Can I keep a user's GreytHr data in sync after the first import? Vern supports re-running an import on demand; incremental change tracking depends on what GreytHr's API exposes for each object.

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

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