> ## Documentation Index > Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt > Use this file to discover all available pages before exploring further. # Add one site, with the same numbering, rules, reference checks and approval gate as the Sites screen. > `p_values` holds the site's fields — `name` is the only one that must be sent, and the site code is assigned by the tenant's numbering. `p_custom_fields` holds answers to the tenant's own fields, keyed by field key. Returns the new site, or `status: PENDING_APPROVAL` where the tenant's approval rules hold it. To change a site afterwards, call `update_record` with `core.sites` as the entity. ## OpenAPI ````yaml /api-reference/openapi.json post /rpc/create_site openapi: 3.0.0 info: description: '' title: >- The only schema PostgREST exposes. Reads are security_invoker views; writes are SECURITY DEFINER functions. Rebuilt wholesale on every deploy — it holds no data. version: 12.2.3 servers: - url: https://app.assetinfinity.ai/api security: [] tags: - name: Signing in - name: Profile - name: My work - name: Sites and locations - name: Assets - name: Asset lifecycle - name: Asset components - name: Work lifecycle - name: Work order execution - name: Work sequencing - name: Maintenance - name: Inspections - name: Checklists - name: Verification - name: Self verification - name: Inventory - name: Inventory detail - name: Parts demand - name: Procurement - name: Vendors and contracts - name: Contracts - name: Amendments - name: Vendor spend forecast - name: Workforce - name: Workforce detail - name: Capacity - name: Dispatch - name: Shutdown - name: Permits - name: Tools - name: Tools on jobs - name: Bookings - name: Calibration history - name: Reliability - name: Sensors and meters - name: Readers - name: Trackers - name: Real-time location - name: Feeds - name: Energy - name: IT assets - name: IT asset software - name: IT asset topology - name: Map - name: Floor plans - name: Labels - name: Lost and found - name: Visitors - name: Root cause analysis - name: Costing - name: Finance - name: Budgets - name: Capex plans - name: FF&E plans - name: Documents - name: Document control - name: Document folders - name: Document tree - name: Knowledge - name: Reports - name: Dashboards - name: Extracts - name: Data exports - name: Audit center - name: Audit feed - name: Activity - name: Conversations - name: Notifications - name: Date reminders - name: Channels - name: Search - name: Copilot - name: Import - name: Bulk jobs - name: File exchange - name: Filing exceptions - name: Files - name: Sync - name: Support - name: API keys - name: Webhooks - name: MCP connections - name: MCP sign-in - name: SCIM provisioning - name: Directory sync - name: Security streams - name: Single sign-on - name: Two-factor sign-in - name: Admin - name: Access - name: Lookups - name: Read models - name: Reference - name: Reference columns - name: Reference entry - name: List views - name: Mapping - name: Numbering - name: Branding - name: Custom fields - name: Form studio - name: Workflows - name: Workflow studio - name: Rules - name: Statuses and transitions - name: Currencies and locales - name: Today - name: Work configuration - name: Asset configuration - name: Inventory configuration - name: Tool configuration - name: Workforce configuration - name: Vendor and contract configuration - name: Document configuration - name: Inspection configuration - name: Sites, locations and the organisation - name: Setup - name: Features - name: Billing - name: Licence - name: Welcome - name: Tray - name: Tenant switch - name: Release - name: Telegram - name: Inbound mail - name: Platform externalDocs: description: PostgREST Documentation url: https://postgrest.org/en/v12/references/api.html paths: /rpc/create_site: post: tags: - Sites and locations summary: >- Add one site, with the same numbering, rules, reference checks and approval gate as the Sites screen. description: >- `p_values` holds the site's fields — `name` is the only one that must be sent, and the site code is assigned by the tenant's numbering. `p_custom_fields` holds answers to the tenant's own fields, keyed by field key. Returns the new site, or `status: PENDING_APPROVAL` where the tenant's approval rules hold it. To change a site afterwards, call `update_record` with `core.sites` as the entity. parameters: - $ref: '#/components/parameters/preferParams' requestBody: content: application/json: schema: description: >- Add one site, with the same numbering, rules, reference checks and approval gate as the Sites screen. `p_values` holds the site's fields — `name` is the only one that must be sent, and the site code is assigned by the tenant's numbering. `p_custom_fields` holds answers to the tenant's own fields, keyed by field key. Returns the new site, or `status: PENDING_APPROVAL` where the tenant's approval rules hold it. To change a site afterwards, call `update_record` with `core.sites` as the entity. properties: p_custom_fields: format: jsonb p_values: description: >- The fields of the new record. Send only the ones you have; the rest take their defaults. properties: address_line1: description: Address line 1. maxLength: 200 type: string address_line2: description: Address line 2. maxLength: 200 type: string alternate_site_head_user_id: description: >- Alternate Site Head. Who answers for the site when the head does not. Named separately on a workflow step, so a step that should reach both says both. The id of a row from users. format: uuid type: string business_unit_id: description: >- Business Unit. How the site rolls up for reporting. The id of a row from business units. format: uuid type: string city: description: City. maxLength: 120 type: string company_id: description: >- Company. The legal entity that owns it. The id of a row from companies. format: uuid type: string country_id: description: Country. The id of a row from countries. format: uuid type: string currency_id: description: >- Currency. The currency costs are entered in here by default. The id of a row from currencies. format: uuid type: string is_active: description: >- Active. Turning this off keeps the site's history but stops new work being raised against it. type: boolean latitude: description: >- Coordinates. Decimal degrees. Used to place the site on a map and to work out travel time to it. type: number locale_id: description: >- Locale. How dates and numbers are formatted for people working at this site. The id of a row from locales. format: uuid type: string name: description: Name. The full name of the site or depot. maxLength: 200 type: string postal_code: description: Postal Code. maxLength: 30 type: string site_head_user_id: description: >- Site Head. Who is accountable for everything that happens at this site. Approvals and escalations routed to the site's head reach this person. The id of a row from users. format: uuid type: string state_province_id: description: State Province. The id of a row from states provinces. format: uuid type: string timezone: description: >- Timezone. The site's own clock. Due dates, shift patterns and SLA clocks are all read in it, so leaving this at UTC for a site that is not in UTC makes work appear late. maxLength: 100 type: string required: - name type: object required: - p_values type: object application/vnd.pgrst.object+json: schema: description: >- Add one site, with the same numbering, rules, reference checks and approval gate as the Sites screen. `p_values` holds the site's fields — `name` is the only one that must be sent, and the site code is assigned by the tenant's numbering. `p_custom_fields` holds answers to the tenant's own fields, keyed by field key. Returns the new site, or `status: PENDING_APPROVAL` where the tenant's approval rules hold it. To change a site afterwards, call `update_record` with `core.sites` as the entity. properties: p_custom_fields: format: jsonb p_values: description: >- The fields of the new record. Send only the ones you have; the rest take their defaults. properties: address_line1: description: Address line 1. maxLength: 200 type: string address_line2: description: Address line 2. maxLength: 200 type: string alternate_site_head_user_id: description: >- Alternate Site Head. Who answers for the site when the head does not. Named separately on a workflow step, so a step that should reach both says both. The id of a row from users. format: uuid type: string business_unit_id: description: >- Business Unit. How the site rolls up for reporting. The id of a row from business units. format: uuid type: string city: description: City. maxLength: 120 type: string company_id: description: >- Company. The legal entity that owns it. The id of a row from companies. format: uuid type: string country_id: description: Country. The id of a row from countries. format: uuid type: string currency_id: description: >- Currency. The currency costs are entered in here by default. The id of a row from currencies. format: uuid type: string is_active: description: >- Active. Turning this off keeps the site's history but stops new work being raised against it. type: boolean latitude: description: >- Coordinates. Decimal degrees. Used to place the site on a map and to work out travel time to it. type: number locale_id: description: >- Locale. How dates and numbers are formatted for people working at this site. The id of a row from locales. format: uuid type: string name: description: Name. The full name of the site or depot. maxLength: 200 type: string postal_code: description: Postal Code. maxLength: 30 type: string site_head_user_id: description: >- Site Head. Who is accountable for everything that happens at this site. Approvals and escalations routed to the site's head reach this person. The id of a row from users. format: uuid type: string state_province_id: description: State Province. The id of a row from states provinces. format: uuid type: string timezone: description: >- Timezone. The site's own clock. Due dates, shift patterns and SLA clocks are all read in it, so leaving this at UTC for a site that is not in UTC makes work appear late. maxLength: 100 type: string required: - name type: object required: - p_values type: object application/vnd.pgrst.object+json;nulls=stripped: schema: description: >- Add one site, with the same numbering, rules, reference checks and approval gate as the Sites screen. `p_values` holds the site's fields — `name` is the only one that must be sent, and the site code is assigned by the tenant's numbering. `p_custom_fields` holds answers to the tenant's own fields, keyed by field key. Returns the new site, or `status: PENDING_APPROVAL` where the tenant's approval rules hold it. To change a site afterwards, call `update_record` with `core.sites` as the entity. properties: p_custom_fields: format: jsonb p_values: description: >- The fields of the new record. Send only the ones you have; the rest take their defaults. properties: address_line1: description: Address line 1. maxLength: 200 type: string address_line2: description: Address line 2. maxLength: 200 type: string alternate_site_head_user_id: description: >- Alternate Site Head. Who answers for the site when the head does not. Named separately on a workflow step, so a step that should reach both says both. The id of a row from users. format: uuid type: string business_unit_id: description: >- Business Unit. How the site rolls up for reporting. The id of a row from business units. format: uuid type: string city: description: City. maxLength: 120 type: string company_id: description: >- Company. The legal entity that owns it. The id of a row from companies. format: uuid type: string country_id: description: Country. The id of a row from countries. format: uuid type: string currency_id: description: >- Currency. The currency costs are entered in here by default. The id of a row from currencies. format: uuid type: string is_active: description: >- Active. Turning this off keeps the site's history but stops new work being raised against it. type: boolean latitude: description: >- Coordinates. Decimal degrees. Used to place the site on a map and to work out travel time to it. type: number locale_id: description: >- Locale. How dates and numbers are formatted for people working at this site. The id of a row from locales. format: uuid type: string name: description: Name. The full name of the site or depot. maxLength: 200 type: string postal_code: description: Postal Code. maxLength: 30 type: string site_head_user_id: description: >- Site Head. Who is accountable for everything that happens at this site. Approvals and escalations routed to the site's head reach this person. The id of a row from users. format: uuid type: string state_province_id: description: State Province. The id of a row from states provinces. format: uuid type: string timezone: description: >- Timezone. The site's own clock. Due dates, shift patterns and SLA clocks are all read in it, so leaving this at UTC for a site that is not in UTC makes work appear late. maxLength: 100 type: string required: - name type: object required: - p_values type: object text/csv: schema: description: >- Add one site, with the same numbering, rules, reference checks and approval gate as the Sites screen. `p_values` holds the site's fields — `name` is the only one that must be sent, and the site code is assigned by the tenant's numbering. `p_custom_fields` holds answers to the tenant's own fields, keyed by field key. Returns the new site, or `status: PENDING_APPROVAL` where the tenant's approval rules hold it. To change a site afterwards, call `update_record` with `core.sites` as the entity. properties: p_custom_fields: format: jsonb p_values: description: >- The fields of the new record. Send only the ones you have; the rest take their defaults. properties: address_line1: description: Address line 1. maxLength: 200 type: string address_line2: description: Address line 2. maxLength: 200 type: string alternate_site_head_user_id: description: >- Alternate Site Head. Who answers for the site when the head does not. Named separately on a workflow step, so a step that should reach both says both. The id of a row from users. format: uuid type: string business_unit_id: description: >- Business Unit. How the site rolls up for reporting. The id of a row from business units. format: uuid type: string city: description: City. maxLength: 120 type: string company_id: description: >- Company. The legal entity that owns it. The id of a row from companies. format: uuid type: string country_id: description: Country. The id of a row from countries. format: uuid type: string currency_id: description: >- Currency. The currency costs are entered in here by default. The id of a row from currencies. format: uuid type: string is_active: description: >- Active. Turning this off keeps the site's history but stops new work being raised against it. type: boolean latitude: description: >- Coordinates. Decimal degrees. Used to place the site on a map and to work out travel time to it. type: number locale_id: description: >- Locale. How dates and numbers are formatted for people working at this site. The id of a row from locales. format: uuid type: string name: description: Name. The full name of the site or depot. maxLength: 200 type: string postal_code: description: Postal Code. maxLength: 30 type: string site_head_user_id: description: >- Site Head. Who is accountable for everything that happens at this site. Approvals and escalations routed to the site's head reach this person. The id of a row from users. format: uuid type: string state_province_id: description: State Province. The id of a row from states provinces. format: uuid type: string timezone: description: >- Timezone. The site's own clock. Due dates, shift patterns and SLA clocks are all read in it, so leaving this at UTC for a site that is not in UTC makes work appear late. maxLength: 100 type: string required: - name type: object required: - p_values type: object required: true responses: '200': description: OK components: parameters: preferParams: description: Preference in: header name: Prefer required: false schema: enum: - params=single-object type: string ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.