How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OKKI Go Emails API

The Emails API from OKKI Go (go.okki.ai) — 6 operations for batch and personalized cold-outreach email sending and per-mail delivery tracking.

OKKI Go Emails API is one of 7 APIs that Xiaoman (OKKI) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Emails. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 6 operations across 6 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://go.okki.ai.

6 operations 6 paths 3 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://go.okki.ai
Authentication
API Key
Resource Areas
1

Authentication & Security 1

OKKI Go Emails API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKey).

  • apiKey — Authorization: ApiKey sk-your-key-here — API keys issued at https://go.okki.ai after registration.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Emails 6
POST
/api/v1/emails/send/batch
Send batch outreach email (one template, many recipients)
sendBatchEmails body → 201402403429502
POST
/api/v1/emails/send/personalized
Send personalized outreach emails (independent bodies)
sendPersonalizedEmails body → 201402403429502
GET
/api/v1/emails/tasks
List email tasks
listEmailTasks 12 params → 200401429
GET
/api/v1/emails/tasks/{taskId}
Get email task detail (per-mail delivery status)
getEmailTask 1 param → 200404429
GET
/api/v1/emails/mails
List individual sent-mail records across tasks
listEmailMails 14 params → 200401429
GET
/api/v1/emails/mails/{mailId}
Get a single sent mail (full body and delivery state)
getEmailMail 1 param → 200404429

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are EmailTask (9 properties), EmailMail (9 properties), Problem (6 properties). Each schema is shown below with its type and property counts.

EmailMail
object
9 properties
EmailTask
object
9 properties
Problem
object
RFC 7807 Problem Details error envelope.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xiaoman-emails-api-openapi.yml Raw ↑

Other APIs Xiaoman (OKKI) publishes across the network.

OKKI Go Companies API
OKKI Go Contacts API
OKKI Go Credits API
Xiaoman (OKKI CRM) 产品 API
Xiaoman (OKKI CRM) devops相关 API
Xiaoman (OKKI CRM) s7.1 API
Where this information came from

This is an independent, third-party profile of OKKI Go Emails API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.