canonical: https://jentic.com/apis/swaggerhub.denefits/alternate-emails-doctor-apis

# Denefits Alternate Emails Doctor APIs

swaggerhub.denefits/alternateemails version 1.0.0-oas3. The API exposes 6 endpoints.

## For AI agents

Programmatically list of alternate emails, add an alternate email. Covers 6 operations.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- List of alternate emails
- Add an alternate email
- Edit an alternate email
- Delete alternate email
- Resend verification email
- Verify an email

## Use cases

### Communications Operations

Use the Alternate Emails Doctor APIs to perform communications operations programmatically. The API provides 6 endpoints covering core functionality including list of alternate emails, add an alternate email, edit an alternate email.

Example prompt: Call POST /alternate_emails_list to list of alternate emails

### Automated alternateEmail Management

Automate alternateemail operations by combining multiple Alternate Emails Doctor APIs endpoints. Agents can add an alternate email and then edit an alternate email in a single workflow.

Example prompt: Call POST /add_alternate_email to add an alternate email, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Alternate Emails Doctor APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'list of alternate emails', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /alternate_emails_list | List of alternate emails |
| POST | /add_alternate_email | Add an alternate email |
| POST | /edit_alternate_email | Edit an alternate email |
| POST | /delete_alternate_email | Delete alternate email |
| POST | /resend_verification_email | Resend verification email |
| POST | /verify_email | Verify an email |

## Key resources

- **alternateEmail** — All APIs of Alternate Emails

## Why Jentic

- **Setup:** Wiring the Alternate Emails Doctor APIs by hand means pointing at the api.denefits.com:8003 host, shaping the list, add, edit, and verification calls, and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the Alternate Emails Doctor APIs from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** This API carries its targets in the request body rather than the URL path, so scope by operation: limit the agent to the operations it needs, such as listing alternate emails and resending a verification email, and leave out deleting an alternate email unless you add it.
- **Credential handling:** This API needs no credentials, so there is nothing for the agent to hold. If a call ever required a secret, your own Jentic One instance would store it once, encrypted, and inject it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list a doctor's alternate emails' or 'resend a verification email', and Jentic returns the matching Alternate Emails Doctor APIs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Alternate Emails Doctor APIs use?

The Alternate Emails Doctor APIs uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list of alternate emails with the Alternate Emails Doctor APIs?

Yes. Use the POST /alternate_emails_list endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Alternate Emails Doctor APIs?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list of alternate emails through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list of alternate emails'. Jentic returns the matching Alternate Emails Doctor APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Alternate Emails Doctor APIs have?

The Alternate Emails Doctor APIs exposes 6 endpoints covering alternateemail operations.

### Can I limit what my agent is allowed to do with the Alternate Emails Doctor API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations and credentials the agent may use. Since the API carries its targets in the request body rather than the URL path, scope by operation: allow only what the agent needs, such as listing alternate emails, adding an alternate email, and resending a verification email. Leave out destructive operations like deleting an alternate email unless you explicitly grant them.