Skip to main content
Peerlogic API resources are connected by short UUID identifiers. Understanding these relationships makes it easier to choose endpoints and combine responses. Treat IDs as opaque, case-sensitive strings and preserve them exactly as returned.

​
Organizations and practices

An organization contains one or more practices. A practice represents a customer location and is the primary scope used when requesting operational and reporting data. Regions provide optional, potentially overlapping groupings of practices within an organization; they are not another level in the hierarchy. See Organization and practice access to discover which of these resources your account is authorized to use.

​
Calls and insights

A call represents a phone interaction associated with a practice. Call identifiers connect a call to related information such as:
  • Transcripts and transcript summaries
  • Sentiment and call-purpose analysis
  • Participants and mentioned entities
  • Outcomes and follow-up activity
Some insights are produced after the call ends, so related information may become available after the initial call record.

​
Conversations, tasks, and opportunities

Conversations represent customer communications and their messages. Tasks represent work that can be assigned or completed. Opportunities represent potential customer outcomes and follow-up activity. These resources may reference a practice, a call, or one another. Use the identifiers returned by each endpoint to follow the relationships exposed in the response.
  • Preserve Peerlogic resource IDs in your integration.
  • Use practice identifiers to scope queries whenever an endpoint supports them.
  • Treat missing related data as potentially unavailable or still processing; do not infer a result that the API did not return.
  • Consult the API Reference for the fields and relationships returned by a specific endpoint.

​
Next step

Learn how to discover your accessible organizations and practices and use their identifiers in API requests.