Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Billing for /contacts with embedded relationships #11384

Open
au63 opened this issue Aug 15, 2024 · 2 comments
Open

Billing for /contacts with embedded relationships #11384

au63 opened this issue Aug 15, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@au63
Copy link

au63 commented Aug 15, 2024

Can anyone from reapit explain it to me regarding how the pricing work will for this endpoint?
https://platform.reapit.cloud/contacts/?pageSize=100&embed=relationships
assuming there is 1 relationship per contact,
will it be:
1 request to contact + 1 request to relationship = 2 billable calls
OR
1 request to contact + 100 requests to relationship = 101 billable calls?

@au63 au63 added needs-triage question Further information is requested labels Aug 15, 2024
@HollyJoyPhillips
Copy link
Contributor

Hi @au63, this section in the documentation may help: https://foundations-documentation.reapit.cloud/faqs#embedding

@au63
Copy link
Author

au63 commented Aug 15, 2024

Hi @au63, this section in the documentation may help: https://foundations-documentation.reapit.cloud/faqs#embedding

Thanks @HollyJoyPhillips
But the example in that page only mentions regarding embedding appointments.
Whereas I am aware that relationships are different because Reapit can only load relationships per entity (contact, company, applicant, etc.)

So, would be helpful in our decision making if we can get clarifications from the team specifically regarding embedding relationships.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants