> For the complete documentation index, see [llms.txt](https://help.horsespot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.horsespot.com/media/marketing-tools/our-social-media-links.md). # Our Social Media Links ## **Follow us social!** **Facebook**\ [**@**Horse Spot Shows](https://www.facebook.com/horsespotshows) **Instagram**\ [**@**HorseSpotShows](https://www.instagram.com/horsespotshows/)\ [@RodeoSpot ](https://www.instagram.com/rodeospot/) **TikTok**\ [**@**HorseSpotShows](https://www.tiktok.com/@horsespotshows) **Linkedin**\ [@Horse Spot](https://www.linkedin.com/company/horse-spot-shows) ## **Collaborator Invites** Love sharing your Horse Spot moments on Instagram? We do too. We review every collaborator invite that comes in, and here's what to expect depending on who's sending it. ### From Competitors We encourage every competitor to tag us on social and invite us to share their big horse show day with them. We'll reshare and celebrate the moment right alongside you. ### From Businesses & Brands For shows, rodeos, and fairs using Horse Spot, we accept collaborator invites 99% of the time. For other businesses and brands, there are a few cases where we may decline an invite: 1. Inaccurate use of the Horse Spot logo, such as the logo being cut off, stretched, or used outside of our usage guidelines and brand parameters. 2. Invites from equine brands that aren't actively partnering with us, or with the shows we support. We love shout outs from our fans and community. If you're looking to establish more of a partnership with us on social, we encourage you to email us at If your invite falls into one of these categories, don't take it personally, we're just protecting our brand consistency. Feel free to reach out if you have questions about getting your post accepted. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.horsespot.com/media/marketing-tools/our-social-media-links.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.