API Enhancement Request
Hi MailOptimal team, Firstly, it's great to see API support being added to the platform. We recently started exploring the API with a view to integrating MailOptimal into our wider automation and reporting workflows. One challenge we've encountered is that the current documentation feels fairly limited from a developer perspective. The API itself appears promising, but it's difficult to understand the full capabilities, supported scenarios, and best practices for implementation without spending a significant amount of time experimenting. A few improvements that would make a huge difference: 1. OpenAPI / Swagger Specification A complete OpenAPI specification would immediately improve the developer experience by allowing SDK generation, easier testing, stronger typing, and quicker onboarding for developers. 2. Official NuGet Package As a .NET developer, this would probably be my most requested feature after Swagger support. An official MailOptimal NuGet package could provide: - Strongly typed request and response models - Authentication helpers - Async-first APIs - Dependency Injection support - Built-in retry handling - Pagination helpers - XML documentation - Sample applications Instead of every customer building their own wrapper around HttpClient, developers could simply install a package and start integrating immediately. For example: services.AddMailOptimal(options => { options.ApiKey = configuration["MailOptimal:ApiKey"]; }); and var campaigns = await client.Campaigns.GetAsync(); would provide a significantly better experience than managing raw REST calls manually. 3. Webhooks Polling APIs works, but webhooks unlock far more powerful integrations. Useful events could include: - New reply received - Campaign status changes - Lead status updates - Email account connection issues - Warmup completion or failures - Deliverability alerts This would allow customers to build event-driven automations instead of repeatedly polling for changes. 4. Reporting & Analytics Endpoints Access to richer reporting data would be extremely valuable for building internal dashboards. Examples include: - Campaign performance metrics - Deliverability statistics - Warmup effectiveness - Account health - Reply classifications - Historical trends 5. Bulk Operations For agencies and larger users, support for bulk APIs would be particularly useful: - Bulk lead management - Bulk campaign updates - Bulk mailbox management - Bulk warmup configuration 6. Documentation Improvements The biggest win may simply be deeper documentation, including: - Request and response examples - Full schema definitions - Error handling guidance - Authentication examples - Pagination behaviour - Rate limiting information - Complete end-to-end integration examples From my perspective, MailOptimal has the potential to become a central component within larger sales, automation, CRM and reporting ecosystems. Stronger API tooling, richer documentation and an official SDK/NuGet package would make it much easier for technical users to integrate the platform into their existing solutions. Thanks for taking the feedback on board and for continuing to invest in the API. I'd be very interested to see the platform become more developer-friendly over time.
Jamie Page about 14 hours ago
API Enhancement Request
Hi MailOptimal team, Firstly, it's great to see API support being added to the platform. We recently started exploring the API with a view to integrating MailOptimal into our wider automation and reporting workflows. One challenge we've encountered is that the current documentation feels fairly limited from a developer perspective. The API itself appears promising, but it's difficult to understand the full capabilities, supported scenarios, and best practices for implementation without spending a significant amount of time experimenting. A few improvements that would make a huge difference: 1. OpenAPI / Swagger Specification A complete OpenAPI specification would immediately improve the developer experience by allowing SDK generation, easier testing, stronger typing, and quicker onboarding for developers. 2. Official NuGet Package As a .NET developer, this would probably be my most requested feature after Swagger support. An official MailOptimal NuGet package could provide: - Strongly typed request and response models - Authentication helpers - Async-first APIs - Dependency Injection support - Built-in retry handling - Pagination helpers - XML documentation - Sample applications Instead of every customer building their own wrapper around HttpClient, developers could simply install a package and start integrating immediately. For example: services.AddMailOptimal(options => { options.ApiKey = configuration["MailOptimal:ApiKey"]; }); and var campaigns = await client.Campaigns.GetAsync(); would provide a significantly better experience than managing raw REST calls manually. 3. Webhooks Polling APIs works, but webhooks unlock far more powerful integrations. Useful events could include: - New reply received - Campaign status changes - Lead status updates - Email account connection issues - Warmup completion or failures - Deliverability alerts This would allow customers to build event-driven automations instead of repeatedly polling for changes. 4. Reporting & Analytics Endpoints Access to richer reporting data would be extremely valuable for building internal dashboards. Examples include: - Campaign performance metrics - Deliverability statistics - Warmup effectiveness - Account health - Reply classifications - Historical trends 5. Bulk Operations For agencies and larger users, support for bulk APIs would be particularly useful: - Bulk lead management - Bulk campaign updates - Bulk mailbox management - Bulk warmup configuration 6. Documentation Improvements The biggest win may simply be deeper documentation, including: - Request and response examples - Full schema definitions - Error handling guidance - Authentication examples - Pagination behaviour - Rate limiting information - Complete end-to-end integration examples From my perspective, MailOptimal has the potential to become a central component within larger sales, automation, CRM and reporting ecosystems. Stronger API tooling, richer documentation and an official SDK/NuGet package would make it much easier for technical users to integrate the platform into their existing solutions. Thanks for taking the feedback on board and for continuing to invest in the API. I'd be very interested to see the platform become more developer-friendly over time.
Jamie Page about 14 hours ago