---
title: "Apply for production access"
method: POST
path: "/v1/projectId/{projectId}/production-access"
tags: ["Production Access"]
---

# Apply for production access

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

## Request

- Base URL: `https://api.bluefox.email`
- URL: `https://api.bluefox.email/v1/projectId/{projectId}/production-access`
- Auth: HTTP bearer

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.

## Path parameters

- `projectId` string, required

## Request body

- ProductionAccessReqInput
  - `volume` integer, required: Expected monthly sending volume.
  - `whyBluefox` string, required
  - `typeOfEmails` string, required
  - `contactsSource` string, required
  - `productDescription` string, required
  - `website` string, required

## Response `201`

Created

- object
  - `status` integer
  - `result` object
    - `_id` string
    - `status` 'pending'

## Other responses

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

---

[API](https://skmtc.dev/bluefox/apis/bluefox-email-public-api.md) · [All operations](https://skmtc.dev/bluefox/apis/bluefox-email-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bluefox/apis/bluefox-email-public-api/revisions/fa1a0a835c7f?raw)