Hi all! I'm a developer looking to integrate <cal....
# general
c
Hi all! I'm a developer looking to integrate cal.com, but as I'm diving into the API documentation I'm getting a bit confused whether this service is correct for what we're trying to do. We have an application built via React Native, and we're attempting to bring in the ability for our users to all schedule meeting with each other, but listing availability and booking it. That seems like a slam dunk for cal.com's $189 plan, but in going through the documentation I'm getting a bit lost. The documentation reads to me like we're to take cal.com and build our features on top of it. For example, the "Users" section of the API doesn't support us creating a user, only editing existing ones. This to me means that our users would need to go and create their own accounts on our self-hosted cal.com? Is there not a way to create a "user" ourselves when they sign up for our own app? Does that make sense? Thanks in advance for any help!
p
following.
v
Two direct DB queries will do the trick, one for creating a user, one for adding an API key. Then you can simulate sign in and intercept cookies. This is a lame but working approach. Or, preferably, you can use SAML which is much cleaner, but SSO should be a part of your architecture from the start.
s
Hey Cody! SSO is a great place to start we are also working on tightening up the create user API. We are working towards having a Stripe Elements approach where every component can be embedded, but that’s a few months out. Right now, you can either build your own front-end components on your dashboard and push the data to the Cal.com platform or you can white-label the Cal.com platform and have it redirected when say a user clicks on your “bookings tab.”
@Bailey lmk if I’m missing anything
j
@Cody Sherman we're also making improvements to our API. For example, creating an admin API key for your self-hosted instance will allow you to create users and control their data directly. This will by pass the hack that @Vladimir Spirin mentioned.
v
@Joe Au-Yeung do you have ETA for this? User creation through API is a must for us, now it’s extremely hacky, I agree.:)
s
@Vladimir Spirin roughly a week~, 2 weeks max!