REST API · v1

The Dipitous Engine

One API call. Every hidden connection in your data. Plug in an email address or handle — get back the complete overlap graph: shared places, events, and context scores.

Request API access Browse endpoints
curl
$ curl https://dipitous.aureus.cx/api/v1/connections \
-H "Authorization: Bearer sk_live_…" \
-G --data-urlencode "[email protected]"
// Response
{
"user": {
"handle": "sarah_chen",
"name": "Sarah Chen",
"email": "[email protected]",
"city": "New York, NY"
},
"connections": [
{ "handle": "marcus", "overlap_count": 4, "top_score": 92 }
],
"total": 12
}

Built for teams that care about context

Conference & events

Submit your attendee list before the event. Surface who already has hidden history with each other. Unlock ice-breakers that actually mean something.

HR & recruiting

Find candidates who share meaningful background with your existing team — same universities, same conferences, same cities at the same time.

Sales intelligence

Before the call: does your prospect have hidden overlap with anyone on your team? The warm intro that wasn't even on LinkedIn.

Authentication

Bearer tokens.
Simple. Secure.

Every request must include your API key in the Authorization header. Tokens are generated once and stored as a one-way hash — we can't recover them, so keep yours safe.

  • ✓ Keys never expire — you deactivate them
  • ✓ Daily rate limit resets at midnight UTC
  • ✓ Per-client usage tracking in the admin panel
HTTP headers
Authorization: Bearer sk_live_a1b2c3d4e5f6…
Content-Type: application/json
Rate limit headers in response
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 994
X-RateLimit-Reset: 2026-03-14
Endpoints

Four endpoints. All the context.

GET /api/v1/connections

Resolve a member & list connections

Look up a Dipitous user by email address or handle, then return a ranked summary of their existing connections — overlap counts and top scores included.

Query parameters

  • email — optional string
  • handle — optional string

Provide exactly one identifier.

Example
GET /api/v1/[email protected]
{
"user": { "handle": "sarah_chen", ... },
"connections": [ { "handle": "marcus", "overlap_count": 4 } ],
"total": 12
}
GET /api/v1/overlaps

Pairwise overlap detail

Given two Dipitous members, return scored overlaps — shared places, date windows, categories, and narrative-ready context. Ideal before introductions or event matchmaking.

Query parameters

  • user_a — email or handle
  • user_b — email or handle
  • limit — optional, default 20
Example
GET /api/v1/overlaps?user_a=sarah_chen&user_b=marcus
{
"overlaps": [ { "place": "Madison Square Garden", "score": 92 } ],
"overlap_count": 4
}
POST /api/v1/batch/overlaps

Batch overlap matrix

Submit up to 500 identifier pairs in one request — perfect for conference attendee lists, hiring pipelines, or CRM enrichment. Returns only pairs with at least one scored overlap.

JSON body

  • pairs — array of { user_a, user_b }

Each value may be an email or handle.

Example
POST /api/v1/batch/overlaps
{ "pairs": [
{ "user_a": "sarah_chen", "user_b": "marcus" }
] }
GET /api/v1/ping

Auth & health check

Verify your API key, inspect remaining rate-limit budget, and confirm Dipitous API availability. Use this in CI or uptime monitors.

Headers

  • Authorization: Bearer sk_live_…
Example
GET /api/v1/ping
{ "status": "ok", "client": "Acme Events" }
Errors & limits

Predictable responses

Dipitous returns standard HTTP status codes with a JSON body { "error": "message" }. Integrations should retry 429 and 5xx responses with exponential backoff.

401 Unauthorized

Missing or invalid API key.

404 Not found

No Dipitous member matches the identifier you supplied.

422 Unprocessable

Malformed JSON or missing required query parameters.

429 Rate limited

Daily quota exceeded — inspect X-RateLimit-* headers.

Default quotas
Standard API key 1,000 requests / day
Batch endpoint max pairs 500 per request
Overlap detail default limit 20 rows

Need higher limits for a live event or enterprise deployment? Request API access — Merezi reviews every integration.

Ready to integrate?

Request your API key. We review every integration to ensure user data is handled responsibly. Typical turnaround is 24–48 hours.

Request API access [email protected]