API?

+1 For a public API! At this time, HB doesn’t allow us access to their API which is a huge bummer.

Pretty wild they don’t have one… (I mean they do since they support Zapier… why not make it public?)

Do we know if it’s planned?

I agree. Super inconvenient. 

Digging in with the curiosity question here; what would you envision using the API for? An integration, automation, etc? As much detail as you can share will help me with relaying feedback to the team! 

Here’s a few:

• Integrations with our website, such as custom triggers (like revisiting our website could trigger an email send from a previously lost prospect)
• Integrations with other marketing software (for instance, I could trigger different actions based on a user’s engagement with my MailChimp monthly newsletter)
• Integrations with social media platforms (I could trigger different automations based on a users engagements with my posts)

TBH the list could go on forever. The Zapier integration list is too limited to allow any of this, and many platforms don’t have a Zapier counterpart or a limited counterpart, which doesn’t allow these things to be possible.

Anything. We dislike Zapier and it’s a bit ridiculous we’re forced to use a third-party PAID application to do anything remotely modern involving automations in HoneyBook.

I fully understand not everyone is a developer, and by leveraging Zapier’s SDK they can be lazy and get that kind of functionality in quick and dirty. And many people will already use Zapier or just cave in and bite the financial bullet.

Though there are blokes like me who are developers and/or have a development team behind them who can code things. Thus, why should I pay for Zapier when I already have in-house and on-premise automation tools (that provide me with FAR greater control and data privacy and integration than Zapier could ever do) that do anything and everything I want for the low-low cost of: my employees short bit of time (or mine on the weekend when I’m bored).

I would like to use an API <IN> for:

• Integration with other forms and tools I have
• Data sync between my data warehouse for centralized contact management
• Adding sales event log into HoneyBook from outside tool
• Allow for easier control from a centralized platform that does my marketing and thus the leads end up into HB (but presently I have no way of getting their sales activity into HB)

For data OUT I would do things such as:

• For each payment (invoice paid in full or not), send data to data warehouse for analytics and reporting
• For each trigger event for a customer/client in HB, send data to my CRM for detailed centralized cotnact logging
• Add contact to email automation in a third-party app that has far more email / automation features (such as advanced branching, tagging, etc ...)

And so forth.

Zapier should not be required for any of that.

Though, to state again: I do understand why they did it. I disagree with their decision and lack of communications about a roadmap or options about this topic.

New member here!

I’m an independent consultant in software engineering and accessibility. One of the first things I looked for was an API or webhooks I could use to customize automations, projects, etc.

I’ll outline two problems that currently prevent me from renewing next year:

• I can’t make my own forms and then use a POST request to submit the data to HB.
  • Embedded forms take a really long time to load.
  • There are accessibility issues with HB forms, and I don’t want to be forced to wait for the team to fix those. (No judgement! Y’all have a lot to do.)
  • I can’t get the forms to match my branding on a form field, form, or layout level.
• I need a lot more from automations. I want to use smart files as interactive guides, and lead forms for people to sign up for them.
  • As far as I can tell I can’t automatically set the project type, project name, header image, etc.
  • I have to manually update those things, and I worry that brand new leads will find “FirstName LastName’s Project” + UI language that mentions “client” to be grifter-y? (That doesn’t feel like the right word, but close.)

Zapier can’t help me with this, and I don’t want to pay for another tool when I know I can use my current skillset to solve these problems if I have access to an API/webhooks.

Another potential API / webhook usage:

Data archiving.

We run an on-prem document management, archival, and retreival system with automated tagging and sorting … Presently, we do not have a way to auto-archive and store (and tag) signed contracts from HB into our local secured storage.

Would be nice :)

I’ll jump in with some additional use cases.  While we don't have in-house developer, Zapier does help us bridge the gaps for relatively simple automations.  Some use cases we would see a benefit are:

- Connecting our external project management system in Air table to the Honeybook project management functions.  As we update progress in our project management system, we would like to automatically push notes to Honeybook so the client can see it instantly. 

- We would also be interested in seeing what we could do with access to the tasks function in Honeybook.  Being able to generate or complete a task in Honeybook via an external system would be helpful.

I also want a public API so I can create a custom hosting panel with invoices and payments. Clients hate having to manage multiple logins. I want to create my own portal that allows the user’s full access to all their payments, upcoming invoices, and current subscriptions. I would embed a HB payment form for them to pay directly within the portal. It would be great too that if I could have my offered services then create invoices in HB and have a fully managed and automated system without the user needing to create a HB account. 

​@Aaron Beach - I would highly suggest submitting this as a feature request under the ideas section of the community or upvoting a thread if one has already been created. :) 

Open public API and webhooks please!

+1, but I feel so strongly about this that I’m going to give it a whopping +100000 for API and webhooks. At the very least, make it a bit easier to use Zapier’s webhooks and allow us to paste the catch hook URL directly into Honeybook. As it stands, Zapier is forced on us to do anything remotely close to what I need, but it’s extremely limited. If you’re going to mandate paying for a third-party solution, at least make it work for more than a limited and disparate scope. There needs to be comprehensive coverage, data coverage. I’m shocked that my options are to create a separate Zap for each and every individual trigger and can’t simply paste Zapier’s catch hook into Honeybook. 2. If I can deal with creating disparate Zaps, then another one so they can post to my catch hook, the event stream needs to pull actual useful data coverage. I’ve added a code step for schema normalization, etc., which is great, but it doesn’t help me much if I can only post about 5 separate Zaps with limited scope. I need the data, not just a shred of a datum. DATA!!!! NOT DATUM!!!! WHERE IS THE DATA!!!! 3. It should never be this inaccessible (to beginners and developers alike) to get some semblance of the complete, cohesive data stream. I need the full picture FIRST. Only after I can pull ALL data (with ease) would I filter the scope I need. This feels so crazy to me. +1, but I feel so strongly about this that I’m going to give it a whopping +100000 for API and webhooks. At the very least, make it a bit easier to use Zapier’s webhooks and allow us to paste the catch hook URL directly into Honeybook. As it stands, Zapier is forced on us to do anything remotely close to what I need, but it’s extremely limited. If you’re going to mandate paying for a third-party solution, at least make it work for more than a limited and disparate scope. There needs to be comprehensive coverage, data coverage. I’m shocked that my options are to create a separate Zap for each and every individual trigger and can’t simply paste Zapier’s catch hook into Honeybook. 2. If I can deal with creating disparate Zaps, then another one so they can post to my catch hook, the event stream needs to pull actual useful data coverage. I’ve added a code step for schema normalization, etc., which is great, but it doesn’t help me much if I can only post about 5 separate Zaps with limited scope. I need the data, not just a shred of a datum. DATA!!!! NOT DATUM!!!! WHERE IS THE DATA!!!! 3. It should never be this inaccessible (to beginners and the developers alike) to get some semblance of the complete, cohesive data stream. I need the full picture FIRST. Only after I can pull ALL data (with ease) would I filter the scope I need. This feels so crazy to me.