paydro / agents / claude-code
Claude Code

View Markdown

Loading documentation…

Paydro + Claude Code

Open your project in your coding agent and paste the prompt for your task.

Add a ticket shop to my website

Use this if you can edit your website. Have your public shop link ready, or ask the agent to help you find or create one. You can embed an existing shop without organizer credentials.

Add a Paydro ticket shop to this website. Read https://developer.paydro.com/llm/sell-tickets.md. Ask me for any missing details, fit the shop into the existing layout, and check that visitors can open the correct shop on desktop and mobile. Show me what you verified.

Connect my app to the Paydro API

You need a server project, organizer access to a test event, your organization's Paydro origin, and the event UUID from its organizer URL.

Connect this project to Paydro and read one test event. Follow https://developer.paydro.com/en-us/docs/getting-started.md. Show me how to set the organizer origin, event UUID, and credentials in the server environment. Keep the password out of chat and logs. Use the project's HTTP client to make a read-only request. Check for HTTP 200 and JSON with the requested Event.id, then report the event name. If access is missing, tell me what to configure.

Give Claude the right context

Start a Claude Code session in your website project and paste your chosen prompt. For repeat work, add the Paydro documentation links to your project's CLAUDE.md so the integration context stays with your code.

Use Claude's plan to review the approach, then let it implement and test the changes. Public ticket-shop embeds do not need organizer API credentials.

Explore Claude Code.

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.

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.