Production Access

Full reference for the Production Access resource in the bluefox.email API. See the API overview for authentication, the response envelope, and pagination.

Before requesting production access, it is worth confirming your sending domain authenticates cleanly. Our free deliverability tools check SPF, DKIM, DMARC, and MX from public DNS.

Get production access status

GET /v1/projectId/{projectId}/production-access

Combined view of the project's production-access request status and domain verification readiness.

Parameters

NameInTypeRequiredDescription
projectIdpathstringyesThe project _id, found in the app under Project Settings.

Responses

StatusDescription
200OK
403Missing or invalid API key

Response body

FieldTypeRequiredDescription
requestStatusstring (none | pending | approved | declined | revoked)"none" means no request has been submitted yet.
domainStatusstring (none | pending | verified)
verifiedDomainstringEmpty string if none is verified yet.
monthlyLimitinteger
sendingRatesarray of object
sendingRates[].regionstring
sendingRates[].ratePerSecondinteger
limitIncreasesarray
restrictedbooleanTrue if the project is currently blocked from sending on bluefox.email's shared infrastructure (see Project.restricted). Approval here does not lift a restriction - switch to BYO-AWS instead if this is true.
restrictedReasonstring

Apply for production access

POST /v1/projectId/{projectId}/production-access

The standard way to move a project past sandbox limits while still sending through bluefox.email's shared infrastructure - no AWS account of its own required. (PATCH .../projectId/{projectId} awsConfig is the separate, less common path for a project that wants to send through its own AWS account instead.) Requires at least one domain with SPF, MX, and DKIM all verified (see the Domains endpoints) - resubmitting after a decline only requires DKIM to still be verified. Approval is manual and not part of this API.

Parameters

NameInTypeRequiredDescription
projectIdpathstringyesThe project _id, found in the app under Project Settings.

Request body

FieldTypeRequiredDescription
volumeintegeryesExpected monthly sending volume.
whyBluefoxstringyes
typeOfEmailsstringyes
contactsSourcestringyes
productDescriptionstringyes
websitestringyes

Responses

StatusDescription
201Created
400Invalid request body or query - every violation found (missing/invalid/unexpected fields) is reported in one response, semicolon-separated, not just the first one hit.
403Missing or invalid API key

Response body

FieldTypeRequiredDescription
_idstring
statusstring (pending)

Request a sending-limit increase

POST /v1/projectId/{projectId}/production-access/limit-increase

Production projects only, and only once a production-access request already exists. Fails if a limit-increase is already pending.

Parameters

NameInTypeRequiredDescription
projectIdpathstringyesThe project _id, found in the app under Project Settings.

Request body

FieldTypeRequiredDescription
monthlyLimitintegeryesMust be higher than the project's current monthlyLimit, except 0 which is always accepted (used to reset/clear the limit).
reasonstringyesAt least 10 characters.

Responses

StatusDescription
200OK
400Invalid request body or query - every violation found (missing/invalid/unexpected fields) is reported in one response, semicolon-separated, not just the first one hit.
403Missing or invalid API key

Response body

FieldTypeRequiredDescription
requestStatusstring (none | pending | approved | declined | revoked)"none" means no request has been submitted yet.
domainStatusstring (none | pending | verified)
verifiedDomainstringEmpty string if none is verified yet.
monthlyLimitinteger
sendingRatesarray of object
sendingRates[].regionstring
sendingRates[].ratePerSecondinteger
limitIncreasesarray
restrictedbooleanTrue if the project is currently blocked from sending on bluefox.email's shared infrastructure (see Project.restricted). Approval here does not lift a restriction - switch to BYO-AWS instead if this is true.
restrictedReasonstring