> ## Documentation Index > Fetch the complete documentation index at: https://developers.nexspace365.com/llms.txt > Use this file to discover all available pages before exploring further. # Create new facility > Create a new facility (super admin only) ## OpenAPI ````yaml https://api.nexspace365.com/api/openapi.json post /api/facilities openapi: 3.0.3 info: title: NexSpace 365 API description: > Multi-industry enterprise workforce management platform — scheduling, HR, payroll, CRM, AI, and messaging suites. ## Authentication Three schemes: session cookie, JWT bearer, or API key (`nex_live_…` / `nex_test_…` / `nex_pat_…`). AI agents should use API keys with appropriate scopes. ## Authorization Endpoints require specific permissions via the RBAC system: - **Internal team**: Full platform access - **Facility users**: Scoped to their org/facilities - **Staff**: Limited to own data ## Error Contract All errors return `{ error: { message, code?, suggestion?, retryable? }, requestId? }`. The `suggestion` field hints at how to fix the request; `retryable` signals whether retry-with-backoff is appropriate. ## Versioning Pin your integration to a specific API version via the `NexSpace-Version` header (date-based, e.g. `2026-05-10`). When absent, the latest version is assumed. Deprecated versions include `Sunset` and `Deprecation` headers. Discovery at `GET /.well-known/api-versions`. ## Idempotency Write operations (POST/PUT/PATCH) accept an `Idempotency-Key` header. If the same key + body combination is sent again within 24 hours, the original response is replayed. Different body with the same key returns 409 Conflict. ## MCP (Model Context Protocol) AI agents interact via `POST /mcp` using JSON-RPC 2.0. Call `tools/list` to discover available verbs, then `tools/call` to invoke them. version: 1.0.0 contact: name: NexSpace API Support email: support@nexspace365.com license: name: MIT url: https://opensource.org/licenses/MIT servers: - url: https://api.nexspace365.com description: Production server security: - bearerAuth: [] - apiKeyAuth: [] tags: - name: Authentication description: User authentication and session management - name: Facilities description: Facility management - name: Staff description: Staff member management and profiles - name: Credentials description: Staff credential tracking — licenses, certifications, and training - name: Shifts description: Shift scheduling and management - name: Dashboard description: Dashboard statistics and widgets - name: API Keys description: API key lifecycle — create, list, revoke, rotate - name: MCP description: Model Context Protocol endpoint for AI agent tool calling - name: OAuth description: OAuth 2.1 authorization server — DCR, authorize, token - name: Webhooks description: Outbound webhook subscription management - name: Analytics description: API usage analytics and observability paths: /api/facilities: post: tags: - Facilities summary: Create new facility description: Create a new facility (super admin only) operationId: createFacility requestBody: required: true content: application/json: schema: type: object properties: name: type: string description: Facility name type: type: string description: Facility/site type (industry-specific, free-form) address: type: string city: type: string state: type: string zip: type: string phone: type: string email: type: string format: email website: type: string nullable: true licenseNumber: type: string nullable: true bedCount: type: integer nullable: true required: - name - type - address - city - state - zip - phone - email responses: '201': description: Facility created successfully content: application/json: schema: $ref: '#/components/schemas/Facility' '400': description: Invalid facility data content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Super admin access required content: application/json: schema: $ref: '#/components/schemas/Error' security: - bearerAuth: [] components: schemas: Facility: type: object properties: id: type: integer description: Unique facility identifier name: type: string description: Facility name type: type: string description: >- Facility/site type (industry-specific, free-form — e.g. clinic, branch, warehouse, store) address: type: string description: Facility address city: type: string description: City state: type: string description: State zip: type: string description: ZIP code phone: type: string description: Primary phone number email: type: string format: email description: Primary email address website: type: string nullable: true description: Facility website URL licenseNumber: type: string nullable: true description: Facility license number bedCount: type: integer nullable: true description: Number of beds in the facility departments: type: array items: type: string description: List of departments in the facility isActive: type: boolean description: Whether the facility is active createdAt: type: string format: date-time description: Facility creation timestamp updatedAt: type: string format: date-time description: Last update timestamp example: id: 1 name: Downtown Distribution Center type: warehouse address: 500 Industrial Pkwy city: Columbus state: OH zip: '43004' phone: +1-614-555-0142 email: ops@acme.example.com website: https://acme.example.com licenseNumber: null bedCount: null departments: - Receiving - Fulfillment - Shipping isActive: true createdAt: '2026-01-15T09:00:00Z' updatedAt: '2026-05-02T14:30:00Z' Error: type: object properties: error: type: object properties: message: type: string description: Human-readable error message code: type: string description: Machine-readable error code (e.g. VALIDATION_FAILED, NOT_FOUND) details: type: object description: Structured details (e.g. Zod validation issues) suggestion: type: string description: Hint for agents on how to recover retryable: type: boolean description: Whether the same request might succeed on retry required: - message requestId: type: string description: Correlation ID for logs and Sentry required: - error securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: JWT token authentication apiKeyAuth: type: http scheme: bearer bearerFormat: NexSpaceApiKey description: | API key or personal access token (NEX-1042). Send as `Authorization: Bearer `. Token format: - `nex_live_…` — live API key (server-to-server) - `nex_test_…` — sandbox API key - `nex_pat_…` — personal access token (acts as the issuing user) Authorization is decided by the key's `scopes` array, not the owning user's RBAC role. See `POST /api/api-keys` to mint a key. ````