Skip to content

Improve clarity and guidance on integrating webhooks with external listing services (e.g., Zillow, Redfin , Zumper , Rent.com , apartments.com , facebook marketplace #37520

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

Closed
1 task done
viviarentals opened this issue Apr 13, 2025 · 4 comments
Labels
content This issue or pull request belongs to the Docs Content team

Comments

@viviarentals
Copy link

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/webhooks-and-events/webhooks/about-webhooks

The documentation could benefit from a dedicated section on how to configure webhook endpoints for integration with third-party listing and payment platforms like Zillow, Redfin, Zumper, and Stripe.
It should also provide examples of real-world usage in React applications or Node.js backends, including common security practices (e.g., validating signature headers or using AWS KMS for encryption

What part(s) of the article would you like to see updated?

Many developers are building listing/invoicing apps that depend on third-party data and webhook notifications. Adding guidance would help streamline integration, improve security, and reduce confusion.

More developers can build compliant and secure webhook endpoints, reduce implementation time, and adopt best practices from GitHub and the wider ecosystem.

Additional information

We’re building a property listing and invoice dashboard that connects with Zillow via HasData, and uses Stripe for invoicing with webhook support for platforms like Redfin, Zumper, and Facebook Marketplace.
More example snippets and webhook troubleshooting tips would help development teams rapidly implement integrations.

@viviarentals viviarentals added the content This issue or pull request belongs to the Docs Content team label Apr 13, 2025
Copy link

welcome bot commented Apr 13, 2025

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Apr 13, 2025
@usman000777

This comment has been minimized.

@Sharra-writes
Copy link
Contributor

Thanks for opening an issue! I'll get this triaged for review.

@Sharra-writes Sharra-writes removed the triage Do not begin working on this issue until triaged by the team label Apr 14, 2025
@Sharra-writes
Copy link
Contributor

Sharra-writes commented Apr 15, 2025

Thank you for opening an issue. Per our “About contributing to GitHub Docs” article -

We only document GitHub products, features, tools, and extensions. We may mention or link to third-party tools to demonstrate how a feature works, but we do not accept pull requests to document third-party tools or integrations unless they were codeveloped with GitHub.

For this reason, we will be closing this issue. If you would like to update our docs with content outside of third-party tools or integrations, feel free to open another PR or issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

No branches or pull requests

4 participants
@usman000777 @Sharra-writes @viviarentals and others