Paydro + GitHub Copilot

Paydro gives you a straightforward starting point for adding ticket sales to your project. Pick what you want to build and include the matching guide in your task for Copilot. It contains the setup steps, examples and access requirements, so you have less to explain from scratch. A public ticket-shop embed needs no API credentials; more detailed guides cover event listings, registration data and connections to your other tools.

Try asking

Create a shop: “Create a draft ticket shop for our workshop with 50 tickets at €25 each.”
Check ticket inventory: “How many tickets are still available for our workshop? Break it down by ticket type.”

These tasks use your authorized organizer access.

Put the context beside your code

Include the prompt below in your task for Copilot. Keep the Paydro documentation links in .github/copilot-instructions.md for repository-wide custom instructions, and describe how your project builds and tests.

Ask Copilot to make a focused change, run the checks and explain the result in the pull request. Review the diff and test the registration flow before release.

Explore Copilot on GitHub.

Start with this prompt

Add a Paydro ticket shop to this website. Read https://developer.paydro.com/llm/summary.md and follow the “Sell tickets on my website” guide. Inspect the project, ask me for any information the guide requires, and integrate the shop with the existing layout and design. Briefly explain your approach, implement it, and verify the result on desktop and mobile. Tell me what you changed and what you checked.

Create a reusable Paydro skill

Working with Paydro regularly? Create a skill so your agent knows where to find current guidance. Use its skill creator if available, or ask it to create the skill using its supported format. Skill support and automatic activation depend on your agent and setup.

Create a reusable paydro skill for Paydro integration and workflow questions. Configure it to activate for relevant Paydro requests where supported. When invoked, read https://paydro.com/llms.txt, follow the guides relevant to the user’s goal, and ask for missing required information. Support both answering questions and implementing requested integrations. Keep the skill concise, link to current documentation, and validate it using your agent’s supported skill format.

Files your agent can read

Start with the summary, choose the guide for your goal and fetch only the reference material needed for the task. These files are public and readable without signing in.

More than a ticket-shop embed

Show your events, match your branding or connect your other tools. Each guide explains the supported approach and what needs organizer access.

For organizer API work, use your organization's HTTPS origin and keep authorized credentials server-side. The developer host serves documentation. Ask your agent to check the documented responses and verify the requested result.