canonical: https://jentic.com/apis/paypi.dev/paypi # Paypi EmailVerify EmailVerify by PayPI is an OTP email verification service that sends one-time codes to email addresses and validates them. The API handles email delivery infrastructure and code lifecycle management, providing a simple 2-endpoint interface for sending verification codes and checking their validity. It eliminates the need for developers to set up email systems or track verification states. ## For AI agents Send OTP verification codes to email addresses and validate them for user authentication flows without managing email infrastructure. ## Scope Does not handle SMS verification, push notifications, or email delivery beyond OTP codes - use for email-based one-time code verification only. ## Capabilities - Send one-time verification codes to any email address with managed delivery - Validate submitted codes against issued OTPs with expiry enforcement - Offload email delivery infrastructure to a managed service - Track verification code lifecycle from issuance through validation or expiry - Integrate email-based two-factor authentication into signup or login flows ## Use cases ### User Registration Email Verification Verify new user email addresses during account registration by sending a one-time code and validating it when the user submits. EmailVerify handles the email delivery and code management, so developers do not need to configure SMTP servers or implement code expiry logic. The API confirms verification in a single response. Example prompt: Send a verification code to user@example.com via POST /sendCode and then validate the submitted code using POST /checkCode ### Two-Factor Authentication via Email Add email-based second factor to login flows by issuing a one-time code when a user attempts to sign in. The code is sent to their registered email and must be submitted back for validation before the session is granted. EmailVerify manages delivery and expiry automatically. Example prompt: Issue an OTP to the user's registered email via POST /sendCode and validate their response with POST /checkCode before granting session access ### AI Agent Email Verification Orchestration AI agents use EmailVerify through Jentic to verify email addresses as part of automated onboarding or identity confirmation workflows. Jentic handles credential management and operation discovery so agents can trigger email verification without configuring email infrastructure. Example prompt: Search Jentic for 'send email verification code', load the sendCode operation schema, and execute to send an OTP to a target email address ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/sendCode` | Send a verification code to an email address | | POST | `/checkCode` | Validate a submitted verification code | ## Key resources - **Verification Codes** — Send OTP codes to email addresses and check submitted codes for validity ## Why Jentic - **Setup:** Wiring EmailVerify by hand means learning its bearer token auth and coding the two-step send-then-check flow against its OTP endpoints yourself. Through Jentic you install once, import EmailVerify from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** EmailVerify takes the email and code in the request body rather than the URL path, so limit the agent to the operations it needs, such as sending a code or checking a code. You choose which of those two operations it may call, and it can call nothing else. - **Credential handling:** Your EmailVerify bearer token 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 'verify an email address with a one-time code' or 'check a submitted OTP', and Jentic returns the matching EmailVerify operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Twilio Verify** — Multi-channel verification supporting SMS, email, and push in addition to email OTP - **SendGrid Email Validation** — Email address validation (syntax and deliverability) before sending OTP - **Mailgun** — Full email delivery platform for transactional and marketing email ## FAQ ### What authentication does the EmailVerify API use? EmailVerify uses Bearer token authentication. Include your API token in the Authorization header as 'Bearer {token}' with each request to POST /sendCode and POST /checkCode. Through Jentic, tokens are stored encrypted in your Jentic One instance and agents receive scoped access without handling raw credentials. ### Can I use EmailVerify for two-factor authentication? Yes. Call POST /sendCode with the user's email address to issue a one-time code, then validate the code they submit via POST /checkCode. The API handles code generation, email delivery, and expiry enforcement, making it suitable for 2FA login flows. ### What are the rate limits for the EmailVerify API? The EmailVerify specification does not document explicit rate limits. The service is designed for transactional verification flows (one code per user action) rather than bulk email sending. Contact PayPI for volume-specific limits. ### How do I verify an email address through Jentic? Use Jentic to search for the operation 'send email verification code', load the schema for POST /sendCode, and execute with the target email address. Then search for 'check email verification code', load POST /checkCode, and submit the code the user provides. Jentic handles authentication for both calls. ### Does EmailVerify handle the email delivery infrastructure? Yes. EmailVerify sends the verification emails directly - you do not need to configure SMTP servers, email templates, or delivery tracking. The API manages the full lifecycle from code generation through email delivery and validation. ### Can I limit what my agent is allowed to do with the EmailVerify API? Yes. Because you run Jentic One yourself, your own rules decide which EmailVerify operations and credentials the agent may use. EmailVerify exposes just two operations, sending a code via POST /sendCode and validating one via POST /checkCode, and you choose which of those the agent is permitted to call. Since the email address and code travel in the request body rather than the URL path, the agent can only reach the operations you have allowed and nothing else.