Renidlyrenidly
Documentation

Welcome to Renidly

2 min read

Renidly is the identity layer modern B2B teams build on. Resolve, enrich, and verify any professional identity — people, organizations, and more — through one authenticated API.

These docs cover everything you need end-to-end: authentication, the response envelope every endpoint shares, identifiers, pagination, credits and rate limits, error handling, and the production checklist we recommend before going live. They stay deliberately general — the exact fields and parameters for each endpoint live in the interactive reference behind the dashboard.

Start here

01 · Getting Started
Quickstart
Sign up, generate an API key, and send your first request in under five minutes.
02 · Getting Started
Authentication
One header, one key — how to send it on every request, across every product.
03 · Core concepts
Response envelope
The fields that wrap every response, and the identifiers you'll see in data.
04 · Core concepts
Account & credits
How credits are spent, how tiers set your rate limit, and how to read both live.

Two products, one key

Renidly exposes two complementary surfaces. They authenticate with the same key, share the same response envelope, and bill from the same credit balance — so you can mix them freely in one integration.

Structured data
Query a clean, stable dataset
Resolve and search deduplicated professional records — people, organizations, institutions — by stable opaque IDs or rich filters, in milliseconds. Best when you want consistent, queryable data at scale.
Live enrichment
Resolve fresh data on demand
Look up a record, its recent activity, or related signals in real time, fetched on request. Best when you need the freshest possible snapshot for a single subject.

Principles that hold everywhere

  • One key, one header. X-renidly-apikey on every request. See Authentication.
  • One envelope. Same response shape on success and failure — branch on success. See Response Envelope.
  • Stable, opaque identifiers. Records are keyed by permanent IDs (prsn_, org_, inst_) — prefer them over handles and slugs, which can change. See identifiers.
  • Page-based and cursor-based pagination. List endpoints page one way or the other. See Pagination.
  • You only pay for success. Failed and invalid calls never cost credits. See Rate Limits & Credits.
  • Predictable errors. Stable categories and codes, clear retry rules. See Errors & Retries.
Next →
Quickstart