---
title: "Create custom field office"
method: POST
path: "/v3/custom_field_offices"
tags: ["Custom Field Offices"]
---

# Create custom field office

`POST /v3/custom_field_offices`

Restrict a custom field's visibility to one additional office. Each call adds one (custom_field_id, office_id) pair; repeat the call for each office the field should appear under. Once any custom_field_office rows exist for a field, it stops being visible to offices outside the list — so partners running multi-office or multi-region rollouts must add every office that should retain access.

## Request body

- object
  - `custom_field_id` integer, required — Id of the custom field to scope. The field becomes visible only on jobs, openings, or offers whose office matches one of the field's `custom_field_offices` rows. Combines with any `custom_field_departments` rows — both scopings can restrict the same field at once.
  - `office_id` integer, required — Id of the office to grant visibility to. Must belong to the same organization as the custom field.

## Response `201`

Successful

- object
  - `id` integer
  - `created_at` string, date-time
  - `updated_at` string, date-time
  - `custom_field_id` integer — Id of the custom field whose visibility is being scoped. References a `/v3/custom_fields` row.
  - `office_id` integer — Id of the office the custom field is restricted to. References a `/v3/offices` row.

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `422` — Unprocessable Content

---

[API](https://skmtc.dev/greenhouse/apis/auth-api.md) · [All operations](https://skmtc.dev/greenhouse/apis/auth-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/greenhouse/auth-api/revisions/9517a2e54640/schema)