What we do
Tools
Industries
Department
How we workLet's talk →
Home/Filevine
Filevine API v2

The Filevine API: Personal Access Tokens, Org Headers and Your First Project Call

Your Filevine admin gave you a Personal Access Token, and your first request came back 401. That's expected. Filevine's v2 gateway doesn't take the PAT itself: it takes a short-lived bearer token you get by exchanging the PAT, plus your org and user IDs as headers on every call.

Where Filevine stops

A case moves forward in Filevine, and nobody outside the firm finds out until someone tells them.

Stuck on Filevine? Let's solve it →

From a Filevine PAT to a request that works

  1. 1

    Get the PAT and client credentials

    Only an Account Admin can create a Personal Access Token in Filevine, and it's shown once, so store it like a password. You also need the client ID and secret issued with your org's API credentials.

    Watch for: the token acts as the user who created it. Make it under a dedicated integration user rather than a staff member who might leave.

  2. 2

    Exchange the PAT for a bearer token

    POST form-encoded to /connect/token on the identity host with grant_type=personal_access_token, token set to the PAT, your client_id and client_secret, and the scopes Filevine lists for the gateway: fv.api.gateway.access, tenant, filevine.v2.api.*, openid, email and fv.auth.tenant.read.

    Watch for: Canadian orgs use identity.filevine.ca and the .ca gateway together. Keep the region in your config, not hard-coded.

  3. 3

    Look up your user and org IDs

    POST to /fv-app/v2/utils/GetUserOrgsWithToken on the gateway with the bearer token. The response holds the user ID and org ID the gateway expects on every later call.

  4. 4

    Send the three headers

    Each request carries Authorization: Bearer, x-fv-orgid and x-fv-userid. A sensible first call is listing projects, since a project is the case record everything else in Filevine hangs from.

  5. 5

    Renew before it runs out

    The bearer token doesn't last long. Read expires_in from the exchange response and fetch a new one ahead of time, rather than finding out from a 401 halfway through a batch.

What breaks a Filevine integration in week two

Built on one paralegal's PAT

How you'll know: The sync stops the day that person is deactivated or their permissions change.

Fix: Run integrations under a dedicated API user with only the access the job needs, and write down who can reissue its token.

429s during a backfill

How you'll know: A bulk load of projects or notes fails partway with too many requests.

Fix: Filevine returns 429 when you send too many calls in a minute. Pace the job, back off and retry, and pull what changed since the last run rather than every project every night.

Polling every project for phase changes

How you'll know: A scheduled job reads the whole caseload just to spot the few that moved.

Fix: Filevine can post events to your URL through webhook subscriptions, which an admin manages in Filevine. Subscribe to the events you need, verify each delivery, and keep a light nightly check only to catch anything missed.

Fields mapped by their labels

How you'll know: Someone renames a section field and the integration quietly writes nowhere.

Fix: Filevine projects are built from your firm's own project types, sections and fields. Map them by ID, and re-test the mapping whenever an admin edits a project type.

Updates to referring doctors, without the phone calls

High-volume personal injury firm: Filevine for case management, a separate intake call center, and referring physicians who expect regular updates

Before

Each time a case reached a new stage in Filevine, a case manager had to remember to call the referring doctor's office and the client separately, on top of everything else that day.

After

The stage change now sends the update: an email to the referring office and a text to the client, each filled from the project.

Case managers save their phone time for the cases that need a real conversation.

A ready-made Filevine integration or a build of your own?

Existing integration

When the tool is already connected

  • Filevine lists native integrations for common tools alongside its API.
  • Switch it on and map the fields, and the tool's vendor keeps it current.
  • Works best when your workflow matches the one the integration was designed around.
Built on the API

When the workflow is your firm's own

  • Referring-party updates, a non-standard billing sync, an intake source nobody else connects.
  • Someone owns the token exchange, the headers, the webhook subscriptions and the monitoring.
  • n-frames builds and runs these for firms that don't want that job in-house.

Look for an existing integration first. Build on the API when the step is specific to how your firm works a case.

Questions people ask

What is Filevine?

Filevine is cloud case management software organized around projects: each case's stages, documents, tasks and people. It's built for litigation and personal injury firms in particular, and has a mobile app for staff working away from the office.

How much does Filevine cost?

There's no published Filevine price list. Cost depends on firm size and the modules you need, so current numbers come from a quote. Ask about API access in the same conversation, so you know what your plan includes before anyone writes code.

Is Filevine good?

It's widely used in personal injury and litigation, known for organizing a case around stages and tasks rather than a flat document list. Whether it suits you depends on your practice area and how your team works a case day to day.

Is there a Filevine mobile app?

Yes. Staff can review case details, documents and tasks from a phone, and it's a real extension of the platform rather than a stripped-down viewer.

Where do I log into Filevine?

Through Filevine's web app, or through the mobile app once your firm's account is set up. The API doesn't use that sign-in. It authenticates through the identity host with your PAT and client credentials.

Does Filevine have real integrations, or just an API?

Both. Filevine has a marketplace of native integrations for common tools, plus the v2 API. Firm-specific work, such as a non-standard billing sync or updates to referring parties, goes through the API, which is where n-frames does the building and upkeep.

Why does my Filevine API call return 401 when the PAT is valid?

Usually because the PAT was sent as the bearer token. Exchange it at the identity host first, then send the resulting token with the x-fv-orgid and x-fv-userid headers. A token from the US identity host also won't help a Canadian org on the .ca gateway.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.