# Parkstack

> Parkstack runs websites, online ticket sales, entry scanning and a box office for visitor attractions: theme parks, zoos, farms and museums. Parks edit everything in the Parkstack console. A park with a website built elsewhere reads its details and sells its tickets through the Parkstack API.

## Parkstack API

- [Developer guide](https://parkstack.net/developers): what the API is for, a quick start and the rules a site must follow
- [Reference](https://parkstack.net/developers/reference): every address, field and error, with example answers
- [Guides](https://parkstack.net/developers/guides): selling tickets start to finish, phone apps, keeping a site up to date, renamed pages, and what has changed
- [OpenAPI description](https://parkstack.net/developers/openapi.json): the same reference as OpenAPI 3.1
- [Instructions for AI coding tools](https://parkstack.net/developers/instructions.md): a file to give an AI tool building a park's website
- [Starter website](https://github.com/Parkstack/attraction-site-starter): a complete park website in Next.js on the API, MIT licensed

Base address: https://api.parkstack.net/site/v1. Send the key as `Authorization: Bearer <key>`. The public demo key `pk_live_demoRiversideParkstackSiteApiKey` reads Riverside, a demonstration park whose checkout takes no payment.

## For parks

- [Product](https://parkstack.net/product): what Parkstack does
- [Pricing](https://parkstack.net/pricing)
- [Help](https://parkstack.net/help): guides for park staff