Primitive Functions API
Deploy JavaScript handlers that run on inbound mail. Each functionis a single ESM module whose default export is an object with anasync `fetch(request, env)` method, in the shape of a Workers-stylehandler. Primitive signs each delivery and forwards the`Primitive-Signature` header to the handler; verify the raw requestbody with `PRIMITIVE_WEBHOOK_SECRET` before trusting the parsed event.The `event` field is `email.received` for normal inbound mail, or amachine-mail type (`email.bounced`, `email.tls_report`,`email.dmarc_report`, `email.dmarc_failure`) for bounces and reports;the payload shape is otherwise identical. Code runs onPrimitive's edge runtime; there is no infrastructure to manage.Secrets land in `env` as encrypted bindings and are refreshed onevery redeploy.
Primitive Functions API is one of 22 APIs that Primitive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Functions. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 20 operations across 12 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://api.primitive.dev/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Primitive Functions API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (BearerAuth).
An API key is passed in the query as token (DownloadToken).
BearerAuth— API key with prim prefix or OAuth access token with primoat prefix: Authorization: Bearer . Access is governed by the caller's organization role (owner, admin,…DownloadToken— Signed download token provided in webhook payloads
Paths & Operations 20
Across 12 paths, the API surfaces 20 operations — 4 DELETE, 8 GET, 4 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.
Deploy JavaScript handlers that run on inbound mail. Each function is a single ESM module whose default export is an object with an async fetch(request, env) method, in the shape…
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are GateDenial (6 properties), ErrorResponse (2 properties), GateFix (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Primitive 12
Other APIs Primitive publishes across the network.
This is an independent, third-party profile of Primitive Functions 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.