MailConfigLab

MailConfigLab

API Documentation

API access is not currently publicly available.

Authentication

Future requests will use a one-time API key in a Bearer authorization header. Stored keys are hashed and can be revoked.

Scopes

The planned diagnostics scope is diagnostics:read.

Request controls

Technical burst limits and commercial daily or monthly quotas are separate controls. Quota responses will use HTTP 429 and may include Retry-After.

Status

Disabled by design

Future error format

{
  "error": {
    "code": "quota_exceeded",
    "message": "The commercial API quota has been reached.",
    "retry_after": 3600
  }
}

Defined codes include invalid_key, revoked_key, insufficient_scope, api_not_available, quota_exceeded, and rate_limited.