canonical: https://jentic.com/apis/prefinery.com/prefinery # Prefinery API Jentic publishes the only available OpenAPI specification for Prefinery API, keeping it validated and agent-ready. The Prefinery API manages beta testing and waitlist programs including user registration, referral tracking, points-based rewards, checkins, and email suppression lists. It provides 22 endpoints for managing testers (waitlist users), projects (betas), friend invitations, reward configurations, and engagement tracking with API key authentication. ## For AI agents Manage beta waitlists, referral programs, and reward systems including user registration, points tracking, friend invitations, and suppression lists. ## Scope Does not handle email delivery, feature flagging, or payment processing -- use for waitlist registration, referral tracking, and reward management only. ## Capabilities - Register and manage waitlist users with referral code tracking - Track user engagement through checkin events and point accrual - Configure and trigger rewards based on referral milestones - Manage friend invitation workflows for viral referral loops - Suppress email communications for opted-out users - Organize multiple beta projects with independent user pools - Monitor waitlist growth and referral conversion metrics ## Use cases ### Viral Waitlist Management Manage product launch waitlists with built-in referral tracking. Prefinery assigns each user a unique referral code upon registration, tracks friend invitations, and awards points when referred users join. This creates viral growth loops where existing waitlist members are incentivized to invite others. Example prompt: Create a new tester via POST /testers with their email, then create a friend invitation via POST /friend_invitations linking to the new user's referral code ### Referral Reward Automation Automate reward delivery when waitlist users reach referral milestones. Configure rewards with the API, then trigger them programmatically when users accumulate enough points or complete specific actions. Points can be awarded for checkins, referrals, or custom engagement events. Example prompt: Create points for user via POST /points, check if threshold is met by reviewing current points via GET /points, then trigger reward via POST `/rewards/{id}/trigger` for the qualifying user ### Beta Program User Engagement Tracking Track user engagement throughout a beta program by recording checkin events when users perform key actions. Checkins provide a history of user activity that feeds into the points system and helps identify the most active beta testers for early access or feedback opportunities. Example prompt: Record a checkin for user 789 via POST `/testers/789/checkin`, then list their checkin history via GET `/testers/789/checkins` to verify engagement frequency ### AI Agent Waitlist Operations via Jentic Enable AI agents to manage waitlist operations through Jentic by searching for Prefinery operations, loading schemas, and executing calls. Agents can register users, track referrals, award points, and trigger rewards without managing API keys directly. Example prompt: Search Jentic for 'add user to waitlist', load the Prefinery tester creation schema, and execute POST /testers with the user email to register them on the waitlist ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/testers` | List all waitlist users | | POST | `/testers` | Register a new waitlist user | | GET | `/testers/{id}` | Get user details and referral code | | POST | `/testers/{id}/checkin` | Record a user checkin event | | POST | `/friend_invitations` | Create a referral invitation | | POST | `/rewards/{id}/trigger` | Trigger a reward for a user | | GET | `/betas` | List beta projects | | POST | `/points` | Award points to a user | ## Key resources - **Testers** — Waitlist users with referral codes and engagement history - **Betas** — Projects representing individual beta or waitlist programs - **Rewards** — Configurable rewards triggered at referral milestones - **Points** — Point accrual system for tracking user engagement - **Checkins** — User activity events for engagement tracking - **Suppressions** — Email suppression list for opted-out users ## Why Jentic - **Setup:** Wiring the Prefinery API by hand means putting your API key in the Authorization header against api.prefinery.com/api/v2 and coordinating tester, referral, and reward calls yourself. Through Jentic you install once, import the Prefinery API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Prefinery takes the new tester's details in the request body, so scoping is by operation: you limit the agent to the operations it needs, such as adding a tester or reading the tester list. Because you pick that set, triggering a reward or awarding points is included only if you add it. - **Credential handling:** Your Prefinery API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'add a user to the waitlist with referral tracking' or 'trigger a reward', and Jentic returns the matching Prefinery operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **LaunchDarkly API** — Feature flag management for controlling beta access based on waitlist position - **Mailchimp API** — Email marketing for communicating with waitlist users about launch updates - **Kickbox API** — Email verification to validate waitlist signups before registration ## FAQ ### Why is there no official OpenAPI spec for Prefinery API? Prefinery does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Prefinery API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Prefinery API use? The Prefinery API uses API key authentication passed in the Authorization header. You receive an API key when you create a Prefinery account. Through Jentic, this key is stored encrypted in the credential vault and agents receive scoped access without handling the raw key. ### Can I track referrals and award points with the Prefinery API? Yes. Each tester registered via POST /testers receives a unique referral_code. When referred users join, Prefinery tracks the chain. Use POST /points to award points manually, and POST `/rewards/{id}/trigger` to deliver rewards when users reach milestones. ### What are the rate limits for the Prefinery API? Prefinery applies rate limits based on your subscription plan. The API returns HTTP 429 responses when limits are exceeded. Check your Prefinery dashboard for plan-specific rate limit details. ### How do I add a user to the waitlist through Jentic? Install the Jentic SDK with pip install jentic, then search for 'add user to waitlist'. Jentic returns the Prefinery POST /testers operation with its schema. Provide the email address in the request body to register the user and receive their referral code in the response. ### Can I manage multiple waitlists with the Prefinery API? Yes. The /betas endpoints let you manage multiple beta projects, each representing an independent waitlist or program. Use GET /betas to list all projects and GET `/betas/{id}` to retrieve details for a specific program. ### Can I limit what my agent is allowed to do with the Prefinery API? Yes. Because Jentic One is self-hosted, you decide which Prefinery operations your agent may call, so you can allow it to add a tester with POST /testers or read the waitlist with GET /testers while excluding everything else. Higher-impact operations like awarding points with POST /points or triggering a reward with POST `/rewards/{id}/trigger` are only available to the agent if you include them in that set. Your own rules and the encrypted API key stay with your instance, and the agent operates strictly within the operations you grant.