What a child shares and owns
When RevDesk looks up a child’s caller registration, it uses the child’s own registration first, then the
parent’s. Register once on the parent and every child’s numbers are covered.
Keys and scopes
The sub-entity endpoints need an API key created in the parent workspace, with these scopes:sub_entities:readto list and read children.sub_entities:writeto create and rename them.compliance:writeas well, to changehipaa_enabled. It’s never granted by default.
/v1/caller-trust/* but can’t change it.
Endpoints
Create
slug is optional. Without it, RevDesk makes one from the name. Slugs are lowercase letters, numbers and
hyphens, up to 64 characters, and unique across RevDesk; a taken slug returns 409. The person who owns the
key becomes the child’s owner.
List
meta.cursor back as cursor for the next page. member_count and
phone_number_count show which children are live.
Get one
403.
Update
name and hipaa_enabled.
HIPAA
A child of a HIPAA-enabled parent starts HIPAA-enabled. While the parent has HIPAA on, settinghipaa_enabled: false on a child returns 403. Turning HIPAA on for a child also sets its call-recording
retention to 30 days, which you can change per number afterward. The parent’s BAA covers its children. See
HIPAA and BAA.
Own caller registration
If a child is a separate legal business with its own caller name, register it with a key scoped to that child:POST /v1/caller-trust/enterprise, then POST /v1/caller-trust/enterprise/sign-and-submit. See
Caller trust.