# Sna4an LinkedIn BlitzAPI

> Sna4an LinkedIn BlitzAPI is a paid API for AI agents from sna4an-linkedin.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Proxies LinkedIn data enrichment and job listings queries through a RapidAPI-backed sub-endpoint path with parameterized lookups

## Facts

- Endpoint: POST https://sna4an-linkedin.vercel.app/api/linkedin-blitzapi
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sna4an-linkedin-blitzapi-7bb89d08
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WcXk8rBO5FhXuJinPQ51J

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability sna4an-linkedin-blitzapi-7bb89d08 -d '<json body>'
```

Example prompt: Can you pull LinkedIn job listings for 'software engineer' roles at Google using the job-search sub-endpoint path, and also enrich John Smith's LinkedIn profile at linkedin.com/in/johnsmith?

## When to prefer this

Choose this endpoint when you need LinkedIn-specific professional data — profiles, job listings, or company info — via a flexible sub-endpoint routing pattern that mirrors RapidAPI LinkedIn APIs, especially when paying per-call via x402 protocol is acceptable and you need programmatic access without a direct LinkedIn API agreement.

## Known failure modes

- Invalid or unsupported RapidAPI sub-endpoint path returns error or empty object
- Missing required query parameters causes malformed upstream request
- LinkedIn data not found for the given identifier returns empty result
- Rate limiting or upstream RapidAPI quota exceeded returns 429 or error
- Payment not processed (402) if x402 payment header is missing or invalid
- Profile or job listing has been removed from LinkedIn, returning null data

## How this service works

LinkedIn data enrichment and job listings APIs

## Output

A JSON object containing LinkedIn data matching the requested sub-endpoint — could include profile fields (name, title, company, location, experience), job listing arrays (title, company, location, date posted), or company metadata depending on the path and params supplied.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "path": {
   "type": "string",
   "description": "RapidAPI sub-endpoint path"
  },
  "params": {
   "type": "object",
   "description": "Query parameters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sna4an-linkedin-blitzapi-7bb89d08/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sna4an-linkedin.vercel.app](https://www.zero.xyz/host/sna4an-linkedin.vercel.app/llms.txt)