Skip to main content

31 posts tagged with "api"

View All Tags

MCP: motorical_whoami works for every connection

  • Fixed. motorical_whoami was listed under read:analytics, but the API route behind it needed a different scope (config.read) that read:analytics does not carry. A connection holding only read:analytics saw the tool and got 403 missing_scope; a connection holding only send:transactional or manage:webhooks never saw it.
  • Now. Any OAuth connection can call it, whatever scopes it holds, and every hosted server except signup lists it, so an agent can always ask what it holds. It stays visible after the sandbox phase.
  • Unchanged. Every other credential (an account-key token, a dashboard token) still needs config.read to read it, because the owner email is returned in full.
  • Packages. @motorical/mcp 1.21.0 and @motorical/scope-catalog 0.6.0 are on npm; the hosted servers already run the change.

Documentation changed

Send Email pages: every field, shown the same way

  • One field list. "Connect and send your first email" and the Transactional Email API quickstart now show the full list of POST /v1/send fields (fromName, cc, bcc, replyTo, headers, attachments, dryRun and the Idempotency-Key header included), generated from the API definition, so it cannot fall behind the API.
  • Consistent examples. The examples across the section now include fromName, and there are examples for copies, a reply address and your own headers (threading and one-click unsubscribe).
  • A separate message per person. The pages now say that an array in to is one message that every recipient can see; send one request per person for separate messages.
  • SMTP. The SMTP quickstart has a short section on how To, Cc, Bcc, the display name and your own headers work over SMTP, where there are no JSON fields.
  • A check keeps it that way. A field added to the API, or an example using a field that does not exist, now fails the documentation build.

Documentation changed

HTTP send: attachments (rolling out)

  • New field on POST /v1/send: attachments, a list of { filename, content (base64), contentType?, contentId?, disposition? }. Inline images use contentId and disposition: "inline".
  • Rolling out per Motor Block. A Motor Block that has not been moved to the new sending path answers 422 with code: "feature_not_enabled" and sends nothing, so a file is never silently dropped.
  • Same rules as SMTP. Your plan decides the number of files, the size per file, the total per message and the file types; every file is scanned for malware before the message is accepted; a refusal names the plan and the limit.
  • dryRun: true runs the same plan check without queueing anything and returns the refusal a real send would get.
  • A request body can be as large as the platform message capacity; above it the answer is 413 with error: "payload_too_large".

Documentation changed

HTTP send: cc, bcc and replyTo (rolling out)

  • New fields on POST /v1/send: cc, bcc (a string or a list each) and replyTo. cc recipients are named in the Cc header; bcc recipients receive the message but are named in no header; replyTo is written as Reply-To.
  • Rolling out per Motor Block. A Motor Block that has not been moved to the new sending path answers 422 with code: "feature_not_enabled" and sends nothing, so a copy is never silently dropped.
  • One list of rules for everyone. to, cc and bcc together may name at most 50 addresses; an address is used once; every recipient is checked against the sandbox and Free-account rules; a suppressed recipient is skipped and reported in data.skipped.
  • Attachments follow the same rollout: see the 2026-10-22 entry.

Documentation changed

MCP: read your domains with read access

Everything you can only look at on a domain no longer needs permission to change domains.

  • Health and config with read access. motorical_get_config and motorical_get_domain_health now need only the read:domains permission. Before, they needed manage:domains, which also lets an agent add and verify domains.
  • Three new read-only tools on the main and Domains servers: motorical_domain_get (one domain), motorical_domain_dns_records (the records to publish, with optional live lookup) and motorical_domain_health (SPF, DKIM and DMARC health of one domain by id, for domains that do not have a Motor Block yet).
  • Matching Public API routes: GET /api/public/v1/domains/{id}, /domains/{id}/health and /domains/{id}/dns-records, all with the config.read scope.
  • Removing a domain is not offered to agents. It stays in the dashboard.

If you use the local server, update to @motorical/mcp 1.14.0.

Documentation changed

MCP: whoami, and Motor Block usage

  • New tool: motorical_whoami. An agent can now ask who it is acting for instead of guessing. It returns the account (id, owner email, name), the plan, and, over OAuth, the permissions the connection holds, the Motor Blocks it covers and the permissions that could still be added, with the page where you add them. The Public API route is GET /api/public/v1/account/whoami.
  • Motor Block usage shows real numbers. The daily, hourly and burst usage of a single Motor Block (dashboard, GET /motor-blocks/{id}/rate-limits and the overview) used to read 0 whatever you had sent. It now matches what was actually sent. Account-level usage was already correct.
  • Cleaner tool list over OAuth. The two 6-digit-code allowlist tools, which only ever worked from a dashboard session, are no longer listed to an OAuth connection; use motorical_free_recipient_add there. Domain tool descriptions now state the scope they need. motorical_get_logs documents its query terms (code: and id:).

If you use the local server, update to @motorical/mcp 1.13.0.

Documentation changed

Sandbox sends to unconfirmed recipients are now refused

A real POST /v1/send from a developer sandbox to a recipient that is not on the allowlist is now refused with 403 and code: "sandbox_outbound_locked" (a locked sandbox, the default) or "sandbox_recipient_denied" (after an explicit unlock), exactly as SMTP already does. Previously the message was silently redirected to your own account address.

Documentation changed

setupToken is now required to set a password

POST /api/auth/set-password now requires the setupToken returned by POST /api/auth/verify-code (or the emailed verification link). A request without a valid token is rejected with 401; a token can be used once and expires after 30 minutes.

The browser sign-up flow already sends it. If you automate signup, update your flow to the order below and pass the token from step 2 to step 3:

  1. POST /api/auth/register with the email
  2. POST /api/auth/verify-code with the emailed code: the response includes setupToken
  3. POST /api/auth/set-password with email, password and setupToken

If your request is rejected, request a fresh code and repeat from step 2. The full request shapes are in Authentication and the OpenAPI document.

Documentation changed

One password rule everywhere

Every place that sets a password now applies the same rule: at least 8 characters, including a lowercase letter, an uppercase letter and a number. A symbol is welcome but does not replace a number.

  • The sign-up, set-password, reset-password and change-password forms all check the rule before you submit, so a password the server would refuse can no longer look acceptable.
  • The API returns a single message for every violation: "Password must be at least 8 characters and include a lowercase letter, an uppercase letter and a number".
  • If setting the password fails after your verification code was accepted, you can retry without requesting a new code.
  • The sign-up password form now includes your email as the username, so your browser's save-password prompt stores a complete login.

Email signup: verify-code now returns a setupToken

POST /api/auth/verify-code (and the emailed verification link) now returns a single-use setupToken, valid for 30 minutes. It proves that the person setting the password owns the email address.

Pass it to POST /api/auth/set-password together with the email and password:

{ "email": "you@example.com", "password": "<choose one>", "setupToken": "<from verify-code>" }

What you need to do. If you script or automate signup (agents, CLI-style flows), send the token from the verify step. It has been required since 2026-10-04 15:23 UTC: a set-password request without a valid token is rejected with 401. See the announcement.

Accounts that sign in with Google or through the Gluo portal cannot have a password set through this endpoint.

Documentation changed