For information about prerequisites, see 

To change the state of a Facility, call the 

 endpoint and pass the following parameters in the request body:

Request bodies are specified in JSON format. The following example request body shows how to change the state of the Facility:

Learn how to change the state of a Facility by following the instructions in this document. Discover the required parameters, including the desired state, reason code (optional), and additional data (optional), which you need to include in the JSON reques

How to: Retrieve the State of a Facility

How to: Change the State of a Facility

clientID

How to: Update a Facility

Platform

What is OS1?

Who can benefit from OS1?

Why use OS1?

OS1 Architecture

OS1 Overview

Create an Account

Make your First API Call

Obtain your Credentials

Quick Start

Working with Callbacks

Asynchronous APIs

Custom Code

Working with GraphQL

Custom Attributes Ownership

Attribute-Based Access Control (ABAC)

Concepts

Authentication And Authorization

How to use Entities?

Entity

Integrate with Participants

Participant

Integrate with Containers

Container

User API

How To: Create a User

How to: Change State of a User

How to: Retrieve State of a User

How to: Retrieve a Designation

How to: Find the User ID of a User

How to: Update a User

User Management Service

Teams Management Service

Integrate with Platform Order Management

Platform Order Attributes and Lifecycle

Work Order Attributes and Lifecycle

Order Validation and Enrichment Plugins

Order Service

Jobs and Objectives

Integrate with Dispatch

Dispatch Service

Integrate with Orchestrator

Job Manager Plugin

Container Manager Plugin

Work Order Manager Plugin

Workflow Manager Plugin

Cancellation Manager Plugin

Orchestrator Service

Execution Task and Macro Payloads

Workflow Service

Getting Started

MTS API Migration Guide

MTS Geofences

MTS Tiles

MTS ETA

Speed Profiling

MTS Nearby Search

Motion Tracking System

Location Tracking

Country Data

Location Service

Use Cases and Features

Messaging

Mobile Push Notifications

Messaging and Mobile Push Notifications

Secure Data Storage

File Management Service

Scheduler Service

Search Query Format

Data Listing and Query (DLQS) Search

Publishing Webhook Events

Subscribing to Webhook Events

Egress Events for Publishers

Webhooks

State Machine

What Services OS1 Offer?

Get Started with Apps and Solutions

OS1 App Developer’s Guide

Registering Your App

Update App Attributes

Add Solutions Compatibility

Submit for Review

App Version Management

Get App Details

Retrieving Production Credentials

Untitled

OS1 Solution Developer Guide

Register Your Solution

Update Solution

Submit Solution for Review

Solution Version Management

Get Solution Details

Solns

Console Banner

Common APIs Overview

Onboarding Apps and Solutions

Managing App and Solution Artifacts

Troubleshooting

Common

SDK Overview

MTS SDK

Dispatch SDK

AAA SDK

Workflow Designer SDK

Console SDK

Platform SDKs

Vehicle Management App

Container App

Sample Apps

SDKs & Sample Apps

Glossary

FAQs

Reason Codes

Error Codes

Data Types Used in OS1

App Development Guidelines

Soln Development Guidlines

Development Guidelines

Console UI Overview

Additional Resources

DispatchOne Overview

Integrate with Logistics Order

Predefined Logistics Order API Attributes

LogisticsOrder API Functionalities

LogisticsOrder API

Integrate with Facilities

Property and Facility Attributes

Creating Property and Facility

Property and Facility Lifecycle

Facility API

Integrate with Vehicles

Vehicle Attributes

Vehicle Lifecycle

Vehicle API

DispatchOne Solution

Member	Description
toState	One of the valid state codes: onboarding, active, deboarding, or inactive.
reasonCode (optional)	A valid reason code associated with the event.
data (optional)	Any additional information about the transition.