Skip to main content
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.
Developer rule of thumbs
  1. Use Person when you care about who someone is — deduplication, career tracking, identity resolution.
  2. Use Contact when you care about where they work and in what role — outbound campaigns, enrichment, work email lookup.
  3. 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 by RBID_PER. It holds identity-level data — name, personal email, LinkedIn URL.

​
Organization

Organization is a company. One record per company, identified by RBID_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.

​
Email

A verified work email address for the contact at their current organization. Sourced from professional profiles and validated for deliverability. Use this for outbound outreach, enrichment, and CRM sync.

​
Phone

A direct dial or company phone number associated with the contact. Where available, includes mobile numbers. Use this for outbound calling, sequencing, and contact enrichment workflows.