2021-03-08 11:56:43 +00:00
<!-- This file was generated based on handlebars templates. Do not edit directly! -->
2021-04-26 16:55:33 +00:00
# obs-websocket 5.0.0 protocol reference
## General Introduction
obs-websocket provides a feature-rich RPC communication protocol, giving access to much of OBS's feature set. This document contains everything you should know in order to make a connection and use obs-websocket's functionality to the fullest.
## Table of Contents
- [Connecting to obs-websocket ](#connecting_to_obs-websocket )
- [Connection steps ](#connecting_steps )
- [Creating an authentication string ](#connecting_authentication_string )
- [Base message types ](#message_types )
- [Hello ](#basemessage_hello )
- [Identify ](#basemessage_identify )
- [Identified ](#basemessage_identified )
- [Reidentify ](#basemessage_reidentify )
- [Event ](#basemessage_event )
- [Request ](#basemessage_request )
- [RequestResponse ](#basemessage_requestresponse )
- [RequestBatch ](#basemessage_requestbatch )
- [RequestBatchResponse ](#basemessage_requestbatchresponse )
- [Requests ](#requests )
- [Events ](#events )
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
## Connecting to obs-websocket {connecting_to_obs-websocket}
Here's info on how to connect to obs-websocket
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### Connection steps {connecting_steps}
- Step 1
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### Creating an authentication string {connecting_authentication_string}
- Start by
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
## Message Types {message_types}
The following message types (`messageType`) are the base message types which may be sent to and from obs-websocket. Sending a message with a `messageType` that is not recognized to the obs-websocket server will result in your connection being closed with `WebsocketCloseCode::UnknownMessageType` .
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### Hello {basemessage_hello}
- Sent from: obs-websocket
- Sent to: Freshly connected websocket client
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### Identify {basemessage_identify}
- Sent from: Freshly connected websocket client
- Sent to: obs-websocket
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### Identified {basemessage_event}
- Sent from: obs-websocket
- Sent to: Freshly identified client
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### Reidentify {basemessage_reidentify}
- Sent from: Identified client
- Sent to: obs-websocket
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### Event {basemessage_event}
- Sent from: obs-websocket
- Sent to: All subscribed and identified clients
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### Request {basemessage_request}
- Sent from: Identified client
- Sent to: obs-websocket
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### RequestResponse {basemessage_requestresponse}
- Sent from: obs-websocket
- Sent to: Identified client which made the request
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### RequestBatch {basemessage_requestbatch}
- Sent from: Identified client
- Sent to: obs-websocket
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
### RequestBatchResponse {basemessage_requestbatchresponse}
- Sent from: obs-websocket
- Sent to: Identified client which made the request
- Description:
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
# Table of Contents
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
<!-- toc -->
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
- [Events ](#events )
- [Requests ](#requests )
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
<!-- tocstop -->
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
## Events
2021-03-08 11:56:43 +00:00
2021-04-26 16:55:33 +00:00
## Requests
2021-03-08 11:56:43 +00:00