# Deeply integrating Discourse into website **URL:** https://meta.discourse.org/t/deeply-integrating-discourse-into-website/44214 **Category:** Development **Created:** [13 mei 2016 om 20:12 UTC](https://meta.discourse.org/t/deeply-integrating-discourse-into-website/44214 "2016-05-13T20:12:31Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![joebuhlig](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joebuhlig/32/193054_2.png) [@joebuhlig](https://meta.discourse.org/u/joebuhlig) #### Post date: [13 mei 2016 om 20:35 UTC](https://meta.discourse.org/t/deeply-integrating-discourse-into-website/44214/2 "2016-05-13T20:35:24Z")
It really depends on what you’re trying to do. If you’re trying to pull pieces of your discourse instance into an existing website, then take a look at this: > [@Discourse REST API Documentation](https://meta.discourse.org/t/discourse-api-documentation/22706): > > Discourse API Please view the Discourse API Documentation site for detailed info: [https://docs.discourse.org](https://docs.discourse.org)information_source Authentication API requests must use HTTP header based authentication. Pass your Api-Key and Api-Username as HTTP headers. Authentication via query parameters or request body is not supported (this was removed in April 2020). Please see the example cURL request below. The only API endpoints that continue to support credentials in query parameters are requests to… If you’re trying to go the other way, I would challenge you to ask if this is really necessary. By creating links on discourse that go to your site and links on the site that go back to discourse, you’re effectively doing the same thing. This is exactly what I do and I have people ask how I managed to incorporate something so dynamic and database driven into my static site. 😄 I don’t. One is on a subdomain with heavy linking back and forth. --- _[View the full topic](https://meta.discourse.org/t/deeply-integrating-discourse-into-website/44214)._