EN
Business email
Checking sign-inAccount
Connect API

Mailcore Email API

Keep your product's service messages under control

Receipts, sign-in codes, order updates, and notifications are sent from your company domain. One API shows whether a message was accepted, delivered, or needs attention.

Connect Email API See how it works
  • Your domain
  • Clear statuses
  • Launch assistance

What your business gains

Make email a reliable part of your product

Your team sees the journey of every important message, sends from its own domain, and avoids building separate email infrastructure.

From product event to message

Customers receive messages when they expect them

Payment, registration, or an order update triggers the message automatically. A retry with the same Idempotency-Key returns the same result.

Your brand as the sender

orders@notify.company.uz

The message looks like part of your service, not a third-party campaign.

Delivery without guesswork

queued → delivered

Statuses are available through the API and webhooks, so support can understand what happened faster.

Use cases

Messages that help customers complete an action

Mailcore is designed for messages triggered by a user action or an event in your product.

Orders and receipts

Confirmation of payment, refund, fulfillment, and order delivery.

Order #8421 paidorders@notify.company.uz

Sign-in and security

One-time codes, account recovery, and important account changes.

Your sign-in code is 184 520security@notify.company.uz

Appointments and bookings

Time confirmation, reminders, and rescheduling.

Your booking is confirmedbooking@notify.company.uz

Product events

A completed report, new comment, or status change.

Your report is readyupdates@notify.company.uz

Only expected service messages. Cold email, purchased lists, and bulk promotional outreach are not permitted.

Delivery tracking

See what happened to every important message

A message receives an ID as soon as it enters the queue. Check its status through the API or receive an event by webhook.

  • 01Support responds with facts
  • 02Your product responds to delays and failures
  • 03Your team sees complaints and protects domain reputation
Status exampleinterface
Order #8421 paidcustomer@example.com · eml_84… delivered
Your sign-in code is 184 520user@example.com · eml_85… accepted
Your booking is confirmedguest@example.com · eml_86… queued

Important: an “accepted” status means the email provider accepted the message; final delivery is confirmed by a separate event.

For developers

One request puts the message in the queue

Developers integrate a clear HTTP contract. The key stays on the server, safe retries do not duplicate a message, and the result returns immediately.

  • The sender is tied to a verified domain
  • Idempotency-Key prevents accidental duplicates
  • Statuses are available through the API and webhooks
Request access
cURLPOST /emails
curl https://mailcore.uz/api/email/v1/emails \
  -H "Authorization: Bearer $MAILCORE_API_KEY" \
  -H "Idempotency-Key: order-8421-completed" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Shop <orders@notify.company.uz>",
    "to": "customer@example.com",
    "subject": "Order #8421 completed",
    "text": "Your order has been completed."
  }'
202 · {"id":"eml_84…","status":"queued"}

Setup

Connect Email API in four clear steps

We verify your domain and use case, agree the limits, and issue a production API key.

  1. 01

    Describe your use case

    Which event triggers the message, who receives it, and what volume do you expect?

  2. 02

    Verify your domain

    Add one verification DNS record. Your website and current incoming email remain unchanged.

  3. 03

    Submit the request for review

    The Mailcore team verifies the sender and sets safe production limits.

  4. 04

    Get production access

    We agree the terms, issue an API key, and help you launch the first use case.

Your current email environment stays in place

Email API does not require moving your website or business email

Outgoing service messages normally use a separate subdomain, for example notify.company.uz.

Two products, one domain

Do your employees need mailboxes too?

Email API sends messages from your application. Business email receives incoming mail and gives your team personal and shared mailboxes. Connect them together or separately.

Explore business email

Setup

Launch your first use case with us

Create an account and describe your product and expected volume. We verify the domain, agree the limits, and prepare production access.

Request
no payment
Domain
verified in the request
Access
after domain verification
Connect Email API

Sending terms are confirmed before the production API key is activated.

Before setup

Frequently asked questions

A quick guide to domains, mailboxes, and sending rules.

Can I use only Email API without mailboxes?

Yes. Email API and business mailboxes are separate products. Employee mailboxes can be added later.

Will the API change MX or affect my website?

No. Outgoing service messages do not require MX. Your website and current incoming email remain in place.

Can I send from the main domain?

The design depends on the domain, but a separate subdomain is usually better for product email, for example notify.company.uz. This makes traffic separation and reputation management easier.

Is the service suitable for marketing campaigns?

No. Cold email, purchased lists, and bulk promotional outreach are prohibited. Email API is for messages the recipient expects.

When will I receive an API key?

After reviewing the domain and use case, we agree the limits and activate a production API key.