RevenueBase organizes B2B data around three core entities — Person, Organization, and Contact — each with its own identifier and scope. Understanding how they relate to each other is the foundation for using the API effectively, whether you’re enriching records, running outbound campaigns, or joining datasets.Documentation Index
Fetch the complete documentation index at: https://docs.revenuebase.ai/llms.txt
Use this file to discover all available pages before exploring further.
Developer rule of thumb
- Use Person when you care about who someone is — deduplication, career tracking, identity resolution.
- Use Contact when you care about where they work and in what role — outbound campaigns, enrichment, work email lookup.
- A person can have many contacts. A contact belongs to exactly one person and one organization.
Person
Person is a real human being. There is exactly one Person record per human, identified byRBID_PER. It holds identity-level data — name, personal email, LinkedIn URL.Organization
Organization is a company. One record per company, identified byRBID_ORG. It holds firmographic data — headcount, revenue, industry, location.Contact
Contact is the join. It represents a specific Person at a specific Organization — Jane at Acme Corp is one Contact, Jane at Stripe is another. Each Contact gets its own unique identifier,RBID_PAO, but the same RBID_PER threads through both. If a person holds multiple current positions, they appear in multiple rows — one per organization.