Documentation
Welcome to Renidly
1 min read
Renidly is the identity layer modern B2B teams build on. One API to resolve, enrich, and verify any professional identity — people, organizations, activities, and career opportunities — in milliseconds.
These docs cover everything you need to integrate the Renidly API end-to-end: account setup, authentication, the response envelope every endpoint shares, rate limits and billing, error handling, and the production checklist we recommend before going live.
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
How API keys work, where to find yours, and how to send it on every request.
03 · Getting Started
Your first API call
Walk through a real request and learn how to parse the response payload.
04 · Core concepts
Response envelope
The five fields that wrap every response — what they mean and how to use them.
What you can do with Renidly
Every endpoint sits in one of four product surfaces. The detailed endpoint reference lives behind the dashboard — sign in to access the full schema, parameter list, and an interactive playground for each one.
People
Resolve any professional identifier
Look up a person by stable ID or public handle and get a complete, structured profile back in milliseconds.
Organizations
Enrich any company
Resolve a company by ID, domain, or public slug — industry, size, headcount, locations, and full firmographics.
Activities
Stream professional updates
Pull posts, comments, and reactions for any person or company — useful for signals, alerts, and intent.
Opportunities
Surface live career signals
Resolve and enrich open roles by opportunity identifier — title, company, location, salary range.
Core concepts to know
- One envelope, everywhere. See Response Envelope.
- Failed validation never costs credits. See Rate Limits & Credits.
- Predictable errors with stable codes. See Errors & Retries.
- Cursor-based pagination for list endpoints. See Pagination.