Create job post location

Id of the job_post to attach this location to. The post's parent job board must also allow the supplied type — boards configured for office or custom_list locations reject free_text values, and vice versa.

How the location is sourced. Drives how value is interpreted: free_text treats value as a literal location string, office resolves it to an organization office id, and custom_list resolves it to a job_board_custom_locations id. Must match the parent job board's configured location strategy.

Location value, interpreted per type. For free_text, the candidate-facing string (e.g. Remote (US)). For office, the integer office id as a string. For custom_list, the integer job_board_custom_locations id as a string — and the custom location must belong to the same job board as the post.

Free-text location string shown on the job post (e.g. New York, NY, Remote (US)). Populated when type is free_text; null for office and custom_list rows, where the displayable text is resolved from the linked office or job_board_custom_location instead.

Id of the organization office this location resolves to. Populated when type is office; null otherwise. Cross-reference with /v3/offices to fetch the office name and address.

How this location is sourced. free_text is an admin-typed string in plain_text_location; office references an organization office via office_id; custom_list references a board-scoped custom location via custom_location_id. Drives which of the three id/text fields is populated and is set by the parent job board's location configuration.

Id of the job_post this location is attached to. A single post can have multiple job_post_locations rows — one per location it's published in (e.g. San Francisco, Remote (US), New York on one multi-location post).

Id of the job_board_custom_locations row this location resolves to. Populated when type is custom_list; null otherwise. Custom locations are board-scoped — confirm the parent post lives on the same job_board_id before reusing an id.