# Wellfound Login API

> Log in to Wellfound with your own account email and password and get back an opaque session blob that the other Wellfound operations (viewer, conversations, applications, application modal, apply, send message) take as input. Your credentials are sent only to Wellfound and are not stored; treat the returned session as a secret. The session is tied to the exit IP it was created on, so pass the same proxyUrl (or none) on every later call. Returns an error if Wellfound rejects the credentials.

Category: [Social Media APIs](https://upapi.io/apis/social-media) · Last updated 2026-11-07

## How to call it

- Endpoint: `POST https://api.upapi.io/wellfound-login.post`, key in the `X-Api-Key` header, JSON body.
- Cost: 10 weighted units per call.
- Timeout: 90 seconds.
- Cache: none; every call runs the operation.
- Try it without writing code: https://app.upapi.io/try/wellfound-login.post

```bash
curl -X POST https://api.upapi.io/wellfound-login.post \
  -H 'Content-Type: application/json' \
  -H 'x-api-key: YOUR_API_KEY' \
  -d '{ "email": "test@example.com", "password": "example", "impersonate": "chrome146" }'
```

## Request parameters

- `email` (string, required) — Wellfound account email.
- `password` (string, required) — Wellfound account password. Sent only to Wellfound, never stored.
- `proxyUrl` (string) — Exit to log in from. Omit to send directly. The session is bound to this exit, so every later call must pass the SAME value.
- `impersonate` (string) — curl_cffi browser-impersonation target.

## Response fields

- `session` (string, required) — Opaque authenticated blob. Treat it as a credential: never log it and never store it in the clear.
- `viewerId` (string) — Wellfound user id, empty when the follow-up viewer read did not answer.
- `elapsedMs` (integer)
- `operationCount` (integer, required) — Persisted queries discovered in the bundle.

## Example request and response

The example response is generated from the published output schema: it shows the shape and field names, not values from a recorded call.

```json
{
  "email": "test@example.com",
  "password": "example",
  "impersonate": "chrome146"
}
```

```json
{
  "session": "example",
  "viewerId": "",
  "elapsedMs": 0,
  "operationCount": 1
}
```

## Frequently asked questions

### How much does the Wellfound Login API cost per call?

Each call spends 10 weighted units of your plan's monthly quota. Full pricing is at https://upapi.io/pricing.

### How do I authenticate to the Wellfound Login API?

Send your key in the X-Api-Key header. A free guest key is available without creating an account.

### Are Wellfound Login API responses cached?

No — every call runs the operation live; responses are not cached.

## More Social Media APIs

- [Wellfound Pipeline Stats](https://upapi.io/apis/social-media/wellfound-pipeline-stats)
- [Wellfound Public Session](https://upapi.io/apis/social-media/wellfound-public-session)
- [Wellfound Refresh Operations](https://upapi.io/apis/social-media/wellfound-refresh-ops)
- [Wellfound Search Jobs](https://upapi.io/apis/social-media/wellfound-search-jobs)
- [Wellfound Application Modal](https://upapi.io/apis/social-media/wellfound-application-modal)
- [Wellfound Apply To Job](https://upapi.io/apis/social-media/wellfound-apply)
- [Wellfound Browse Jobs](https://upapi.io/apis/social-media/wellfound-browse-jobs)
- [Wellfound Job Detail](https://upapi.io/apis/social-media/wellfound-job-detail)