diff --git a/src/data/nav/platform.ts b/src/data/nav/platform.ts
index 383a459861..6b83565d5d 100644
--- a/src/data/nav/platform.ts
+++ b/src/data/nav/platform.ts
@@ -247,7 +247,7 @@ export default {
pages: [
{
name: 'Overview',
- link: '/docs/account',
+ link: '/docs/platform/account',
index: true,
},
{
diff --git a/src/pages/docs/ai-transport/messaging/citations.mdx b/src/pages/docs/ai-transport/messaging/citations.mdx
index 4bf502ca2a..d79f1c9709 100644
--- a/src/pages/docs/ai-transport/messaging/citations.mdx
+++ b/src/pages/docs/ai-transport/messaging/citations.mdx
@@ -6,7 +6,7 @@ meta_keywords: "citations, references, source attribution, message annotations,
AI agents often draw information from external sources such as documents, web pages, or databases. Citations to those sources enable users to verify information, explore sources in detail, and understand where responses came from. Ably's [message annotations](/docs/messages/annotations) provide a model-agnostic, structured way to attach source citations to AI responses without modifying the response content. It enables clients to append information to existing messages on a channel.
-This pattern works when publishing complete responses as messages on a channel or when streaming responses using the [message-per-response](/docs/ai-transport/message-per-response) pattern.
+This pattern works when publishing complete responses as messages on a channel or when streaming responses using the [message-per-response](/docs/ai-transport/token-streaming/message-per-response) pattern.
## Why citations matter
-When streaming response tokens using the [message-per-response](/docs/ai-transport/message-per-response) pattern, you can publish citations while the response is still streaming since the `serial` of the response message becomes known after you [publish the initial message](/docs/ai-transport/token-streaming/message-per-response#publishing).
+When streaming response tokens using the [message-per-response](/docs/ai-transport/token-streaming/message-per-response) pattern, you can publish citations while the response is still streaming since the `serial` of the response message becomes known after you [publish the initial message](/docs/ai-transport/token-streaming/message-per-response#publishing).
diff --git a/src/pages/docs/ai-transport/messaging/human-in-the-loop.mdx b/src/pages/docs/ai-transport/messaging/human-in-the-loop.mdx
index c81807289a..7a2212bdb5 100644
--- a/src/pages/docs/ai-transport/messaging/human-in-the-loop.mdx
+++ b/src/pages/docs/ai-transport/messaging/human-in-the-loop.mdx
@@ -223,7 +223,7 @@ Set [`echoMessages`](/docs/api/realtime-sdk/types#client-options) to `false` in
The agent listens for human decisions and acts accordingly. When a response arrives, the agent retrieves the pending request using the `toolCallId`, verifies that the user is permitted to approve that specific action, and either executes the action or handles the rejection.
-For audit trails, use [integration rules](/docs/integrations) to stream approval messages to external systems.
+For audit trails, use [integration rules](/docs/platform/integrations) to stream approval messages to external systems.
### Verify by user identity
-For more details on rate limits and rollup behavior, see [Token streaming limits](/docs/ai-transport/token-rate-limits#rollup).
+For more details on rate limits and rollup behavior, see [Token streaming limits](/docs/ai-transport/token-streaming/token-rate-limits#rollup).
## Subscribing to token streams
-Unlike the [message-per-response](/docs/ai-transport/token-streaming/message-per-response) pattern, the message-per-token pattern requires you to [manage rate limits directly](/docs/ai-transport/token-rate-limits#per-token).
+Unlike the [message-per-response](/docs/ai-transport/token-streaming/message-per-response) pattern, the message-per-token pattern requires you to [manage rate limits directly](/docs/ai-transport/token-streaming/token-rate-limits#per-token).
diff --git a/src/pages/docs/api/index.mdx b/src/pages/docs/api/index.mdx
index 37c6332da9..71ff9bc9ca 100644
--- a/src/pages/docs/api/index.mdx
+++ b/src/pages/docs/api/index.mdx
@@ -60,9 +60,9 @@ The API reference for the [Chat SDK](https://sdk.ably.com/builds/ably/ably-chat-
In addition to the API references listed previously, our developer documentation also provides information on how these interfaces are used, and this covers key concepts such as connections, channels, messages and the pub/sub pattern. You can find that information on the following pages:
-* [Client library Realtime SDK - Overview](/docs/realtime)
-* [Client library REST SDK - Overview](/docs/rest)
-* [Realtime and REST interface use cases](/docs/realtime#realtime-vs-rest)
-* [REST API - Overview](/docs/rest-api)
+* [Client library Realtime SDK - Overview](/docs/api/realtime-sdk)
+* [Client library REST SDK - Overview](/docs/api/rest-sdk)
+* [Realtime and REST interface use cases](/docs/api/realtime-sdk#realtime-vs-rest)
+* [REST API - Overview](/docs/api/rest-api)
* [SSE API - Overview](/docs/protocols/sse)
-* [Control API - Overview](/docs/platform/account/control-api)
+* [Control API - Overview](/docs/api/control-api)
diff --git a/src/pages/docs/api/realtime-sdk.mdx b/src/pages/docs/api/realtime-sdk.mdx
index 0c12de70ef..708907b2a4 100644
--- a/src/pages/docs/api/realtime-sdk.mdx
+++ b/src/pages/docs/api/realtime-sdk.mdx
@@ -206,7 +206,7 @@ A reference to the [ARTLocalDevice](/docs/api/realtime-sdk/push#local-device) ob
### `Channels` `channels` `Connection` `connection` action Action | the event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) | `enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { Absent, Present, Enter, Leave, Update }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { :absent, :present, :enter, :leave, :update }` `ARTPresenceAction` |
| data Data | The presence update payload, if provided | `String`, `ByteArray`, `JSONObject`, `JSONArray` `String`, `byte[]`, plain C# object that can be converted to Json `String`, `StringBuffer`, `JSON Object` `String`, `Binary` (ASCII-8BIT String), `Hash`, `Array` `String`, `NSData`, `Dictionary`, `Array` `NSString *`, `NSData *`, `NSDictionary *`, `NSArray *` |
-| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/channels/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects. | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `JSON Object` `Hash`, `Array` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` |
+| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects. | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `JSON Object` `Hash`, `Array` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` |
| id Id | Unique ID assigned by Ably to this presence update | `String` |
| clientId client_id ClientId clientId | The client ID of the publisher of this presence update | `String` |
| connectionId connection_id ConnectionId connectionId | The connection ID of the publisher of this presence update | `String` |
@@ -701,7 +701,7 @@ Returns a new `PaginatedResult` loaded with the next page of results. If there a
`Task> NextAsync()`
-Returns a new [`PaginatedResult`](/docs/api/realtime-sdk/historypaginated-result) loaded with the next page of results. If there are no further pages, then a blank PaginatedResult will be returned. The method is asynchronous and return a Task which needs to be awaited to get the `PaginatedResult`
+Returns a new [`PaginatedResult`](/docs/api/realtime-sdk/history#paginated-result) loaded with the next page of results. If there are no further pages, then a blank PaginatedResult will be returned. The method is asynchronous and return a Task which needs to be awaited to get the `PaginatedResult`
diff --git a/src/pages/docs/api/realtime-sdk/presence.mdx b/src/pages/docs/api/realtime-sdk/presence.mdx
index 5e04e9ac8f..d612324043 100644
--- a/src/pages/docs/api/realtime-sdk/presence.mdx
+++ b/src/pages/docs/api/realtime-sdk/presence.mdx
@@ -1237,7 +1237,7 @@ A `PresenceMessage` represents an individual presence update that is sent to or
|----------|-------------|------|
| action action Action | the event signified by a PresenceMessage. See [`Presence action`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage::ACTION`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) | `enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { Absent, Present, Enter, Leave, Update }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { :absent, :present, :enter, :leave, :update }` `ARTPresenceAction` |
| data Data | The presence update payload, if provided | `String`, `ByteArray`, `JSONObject`, `JSONArray` `String`, `byte[]`, plain C# object that can be converted to Json `String`, `StringBuffer`, `JSON Object` `String`, `Binary` (ASCII-8BIT String), `Hash`, `Array` `String`, `NSData`, `Dictionary`, `Array` `NSString *`, `NSData *`, `NSDictionary *`, `NSArray *` |
-| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/channels/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects. | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `JSON Object` `Hash`, `Array` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` `Map`, `List` |
+| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects. | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `JSON Object` `Hash`, `Array` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` `Map`, `List` |
| id Id | Unique ID assigned by Ably to this presence update | `String` |
| clientId client_id ClientId | The client ID of the publisher of this presence update | `String` |
| connectionId connection_id ConnectionId | The connection ID of the publisher of this presence update | `String` |
diff --git a/src/pages/docs/api/realtime-sdk/types.mdx b/src/pages/docs/api/realtime-sdk/types.mdx
index 64452764e7..bd7c646d03 100644
--- a/src/pages/docs/api/realtime-sdk/types.mdx
+++ b/src/pages/docs/api/realtime-sdk/types.mdx
@@ -615,7 +615,7 @@ A `PresenceMessage` represents an individual presence update that is sent to or
|----------|-------------|------|
| action Action | The event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) [Presence action](/docs/api/realtime-sdk/types#presence-action) [`PresenceAction`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage::ACTION`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage::action`](/docs/api/realtime-sdk/types#presence-action) | `enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { :absent, :present, :enter, :leave, :update }` `ARTPresenceAction` `enum { Absent, Present, Enter, Leave, Update }` `const PresenceMessage::PresenceAbsent,PresencePresent,PresenceEnter,PresenceLeave,PresenceUpdate` |
| data Data | The presence update payload, if provided | `String`, `ByteArray`, `JSONObject`, `JSONArray` `String`, `StringBuffer`, `JSON Object` `String`, `Binary` (ASCII-8BIT String), `Hash`, `Array` `String`, `Bytearray`, `Dict`, `List` `String`, `NSData`, `Dictionary`, `Array` `NSString *`, `NSData *`, `NSDictionary *`, `NSArray *` `String`, `byte[]`, plain C# object that can be converted to Json `String`, `[]byte` `String`, `Map`, `List` |
-| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/channels/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects | `JSONObject`, `JSONArray` `JSON Object` `Hash`, `Array` `Dict`, `List` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` plain C# object that can be converted to Json `String`, `[]byte` `Map`, `List` |
+| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects | `JSONObject`, `JSONArray` `JSON Object` `Hash`, `Array` `Dict`, `List` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` plain C# object that can be converted to Json `String`, `[]byte` `Map`, `List` |
| id Id | Unique ID assigned by Ably to this presence update | `String` |
| clientId client_id ClientId | The client ID of the publisher of this presence update | `String` |
| connectionId connection_id ConnectionId | The connection ID of the publisher of this presence update | `String` |
diff --git a/src/pages/docs/api/rest-sdk.mdx b/src/pages/docs/api/rest-sdk.mdx
index 0967d0235c..06353568fb 100644
--- a/src/pages/docs/api/rest-sdk.mdx
+++ b/src/pages/docs/api/rest-sdk.mdx
@@ -206,7 +206,7 @@ A reference to the channels Channels AblyRest Methods Ably.Rest Methods io.ably.lib.AblyRest Methods Ably::Rest::Client Methods ARTRest Methods ably.Rest Methods action Action Action | the event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`Presence action`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceAction`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage::ACTION`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage::ACTION`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage::action`](/docs/api/realtime-sdk/types#presence-action) | `enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { Absent, Present, Enter, Leave, Update }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { :absent, :present, :enter, :leave, :update }` `const PresenceMessage::ABSENT,PRESENT,ENTER,LEAVE,UPDATE` `ARTPresenceAction` `const PresenceMessage::PresenceAbsent,PresencePresent,PresenceEnter,PresenceLeave,PresenceUpdate` |
| data Data | The presence update payload, if provided | `String`, `ByteArray`, `JSONObject`, `JSONArray` `String`, `byte[]`, plain C# object that can be converted to Json `String`, `StringBuffer`, `JSON Object` `String`, `[]byte` `String`, `Binary` (ASCII-8BIT String), `Hash`, `Array` `String`, `Bytearray`, `Dict`, `List` `String`, `NSData`, `Dictionary`, `Array` `NSString *`, `NSData *`, `NSDictionary *`, `NSArray *` `String`, `Binary String`, `Associative Array`, `Array` |
-| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/channels/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects. | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `String`, `[]byte` `JSON Object` `Hash`, `Array` `Dict`, `List` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` `Associative Array`, `Array` |
+| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects. | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `String`, `[]byte` `JSON Object` `Hash`, `Array` `Dict`, `List` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` `Associative Array`, `Array` |
| id Id | Unique ID assigned by Ably to this presence update | `String` |
| clientId client_id ClientId | The client ID of the publisher of this presence update | `String` |
| connectionId connection_id ConnectionId | The connection ID of the publisher of this presence update | `String` |
diff --git a/src/pages/docs/api/rest-sdk/presence.mdx b/src/pages/docs/api/rest-sdk/presence.mdx
index 27114807d3..2a244191a5 100644
--- a/src/pages/docs/api/rest-sdk/presence.mdx
+++ b/src/pages/docs/api/rest-sdk/presence.mdx
@@ -255,7 +255,7 @@ A `PresenceMessage` represents an individual presence update that is sent to or
|----------|-------------|------|
| action Action Action | the event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`Presence action`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceAction`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage::ACTION`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage::ACTION`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) the event signified by a PresenceMessage. See [`PresenceMessage::action`](/docs/api/realtime-sdk/types#presence-action) | `enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { Absent, Present, Enter, Leave, Update }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { :absent, :present, :enter, :leave, :update }` `const PresenceMessage::ABSENT,PRESENT,ENTER,LEAVE,UPDATE` `ARTPresenceAction` `const PresenceMessage::PresenceAbsent,PresencePresent,PresenceEnter,PresenceLeave,PresenceUpdate` |
| data Data | The presence update payload, if provided | `String`, `ByteArray`, `JSONObject`, `JSONArray` `String`, `byte[]`, plain C# object that can be converted to Json `String`, `StringBuffer`, `JSON Object` `String`, `[]byte` `String`, `Binary` (ASCII-8BIT String), `Hash`, `Array` `String`, `Bytearray`, `Dict`, `List` `String`, `NSData`, `Dictionary`, `Array` `NSString *`, `NSData *`, `NSDictionary *`, `NSArray *` `String`, `Binary String`, `Associative Array`, `Array` |
-| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/channels/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects. | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `String`, `[]byte` `JSON Object` `Hash`, `Array` `Dict`, `List` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` `Associative Array`, `Array` `Map`, `List` |
+| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects. | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `String`, `[]byte` `JSON Object` `Hash`, `Array` `Dict`, `List` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` `Associative Array`, `Array` `Map`, `List` |
| id Id | Unique ID assigned by Ably to this presence update | `String` |
| clientId client_id ClientId | The client ID of the publisher of this presence update | `String` |
| connectionId connection_id ConnectionId | The connection ID of the publisher of this presence update | `String` |
diff --git a/src/pages/docs/api/rest-sdk/types.mdx b/src/pages/docs/api/rest-sdk/types.mdx
index 646ef6c8f3..fdfc4f1b0b 100644
--- a/src/pages/docs/api/rest-sdk/types.mdx
+++ b/src/pages/docs/api/rest-sdk/types.mdx
@@ -469,7 +469,7 @@ A `PresenceMessage` represents an individual presence update that is sent to or
|-----------|-------------|------|
| action Action | The event signified by a PresenceMessage. See [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) [`Presence action`](/docs/api/realtime-sdk/types#presence-action) [`PresenceAction`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage::ACTION`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage::ACTION`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage.action`](/docs/api/realtime-sdk/types#presence-action) [`PresenceMessage::action`](/docs/api/realtime-sdk/types#presence-action) [`Presence action`](/docs/api/realtime-sdk/types#presence-action) | `enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { Absent, Present, Enter, Leave, Update }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `int enum { ABSENT, PRESENT, ENTER, LEAVE, UPDATE }` `enum { :absent, :present, :enter, :leave, :update }` `const PresenceMessage::ABSENT,PRESENT,ENTER,LEAVE,UPDATE` `ARTPresenceAction` `const PresenceMessage::PresenceAbsent,PresencePresent,PresenceEnter,PresenceLeave,PresenceUpdate` |
| data Data | The presence update payload, if provided | `String`, `ByteArray`, `JSONObject`, `JSONArray` `String`, `byte[]`, plain C# object that can be converted to Json `String`, `StringBuffer`, `JSON Object` `String`, `[]byte` `String`, `Binary` (ASCII-8BIT String), `Hash`, `Array` `String`, `Bytearray`, `Dict`, `List` `String`, `NSData`, `Dictionary`, `Array` `NSString *`, `NSData *`, `NSDictionary *`, `NSArray *` `String`, `Binary String`, `Associative Array`, `Array` `String`, `StringBuffer`, `JSON Object` |
-| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/channels/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `String`, `[]byte` `JSON Object` `Hash`, `Array` `Dict`, `List` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` `Associative Array`, `Array` `Map`, `List` |
+| extras Extras | Metadata and/or ancillary payloads, if provided. The only currently valid payloads for extras are the [`push`](/docs/push/publish#sub-channels), [`ref`](/docs/messages#interactions) and [`privileged`](/docs/platform/integrations/webhooks#skipping) objects | `JSONObject`, `JSONArray` plain C# object that can be converted to Json `String`, `[]byte` `JSON Object` `Hash`, `Array` `Dict`, `List` `Dictionary`, `Array` `NSDictionary *`, `NSArray *` `Associative Array`, `Array` `Map`, `List` |
| id Id | Unique ID assigned by Ably to this presence update | `String` |
| clientId client_id ClientId | The client ID of the publisher of this presence update | `String` |
| connectionId connection_id ConnectionId | The connection ID of the publisher of this presence update | `String` |
diff --git a/src/pages/docs/channels/index.mdx b/src/pages/docs/channels/index.mdx
index 803e3a4781..72b2a7cb2e 100644
--- a/src/pages/docs/channels/index.mdx
+++ b/src/pages/docs/channels/index.mdx
@@ -28,7 +28,7 @@ redirect_from:
Channels are used to separate messages into different topics. They are the building block of creating a realtime application using the publish-subscribe pattern. Channels are also the unit of security and scalability. Clients should only ever be provided the [capabilities](/docs/auth/capabilities) for channels that they should have access to.
-[Messages](/docs/channels/messages) contain the data that a client is communicating, such as the contents of an individual chat message, or an event that has occurred, such as updated financial information.
+[Messages](/docs/messages) contain the data that a client is communicating, such as the contents of an individual chat message, or an event that has occurred, such as updated financial information.
With [basic pub-sub](/docs/pub-sub) you create a channel, subscribe to it, and then publish messages to it. Most other Ably features utilize channels, or a group of channels, to provide additional functionality to your realtime applications.
@@ -134,7 +134,7 @@ channel := rest.Channels.Get("{{RANDOM_CHANNEL_NAME}}")
-Although Ably recommends that you use channels to distribute work more evenly across the cluster, there is an [associated cost](/docs/pricing) for a high number of channels.
+Although Ably recommends that you use channels to distribute work more evenly across the cluster, there is an [associated cost](/docs/platform/pricing) for a high number of channels.
Don't use different channels just to indicate different types of data, or different events, if all messages are going to the same set of clients. Use a single channel and distinguish between them using a different message `name`.
diff --git a/src/pages/docs/channels/options/deltas.mdx b/src/pages/docs/channels/options/deltas.mdx
index 7e6ef52956..c644fc3f8a 100644
--- a/src/pages/docs/channels/options/deltas.mdx
+++ b/src/pages/docs/channels/options/deltas.mdx
@@ -19,7 +19,7 @@ Using delta mode can significantly reduce the encoded size of each message when
## Delta processing
-LiveObjects synchronization events do not replace [connection](/docs/connect/states) or [channel](/docs/channel/states) states. You should still monitor these states and handle [connection](/docs/connect/states#handling-failures) and [channel](/docs/channel/states#failure) failures to ensure your application behaves as expected. LiveObjects synchronization events specifically inform you about the progress of LiveObjects data synchronization and should be used alongside other state management mechanisms.
+LiveObjects synchronization events do not replace [connection](/docs/connect/states) or [channel](/docs/channels/states) states. You should still monitor these states and handle [connection](/docs/connect/states#handling-failures) and [channel](/docs/channels/states#failure) failures to ensure your application behaves as expected. LiveObjects synchronization events specifically inform you about the progress of LiveObjects data synchronization and should be used alongside other state management mechanisms.
## Handle object lifecycle events
```shell
diff --git a/src/pages/docs/livesync/mongodb/index.mdx b/src/pages/docs/livesync/mongodb/index.mdx
index 2939fb868a..24d35dc975 100644
--- a/src/pages/docs/livesync/mongodb/index.mdx
+++ b/src/pages/docs/livesync/mongodb/index.mdx
@@ -8,7 +8,7 @@ Use the MongoDB database connector to distribute document changes from a MongoDB
The MongoDB database connector utilizes the MongoDB [change streams](https://www.mongodb.com/docs/v8.0/changeStreams/) feature to distribute changes from the database to clients over Ably Pub/Sub channels.
-By using Ably Pub/Sub channels and SDKs, clients subscribing to messages published by the MongoDB database connector benefit from features like [connection-recovery](/docs/connect/states), [exactly-once delivery](/docs/achieving-exactly-once-message-processing-with-ably) and [ordering guarantees](https://faqs.ably.com/reliable-message-ordering-for-connected-clients) out of the box.
+By using Ably Pub/Sub channels and SDKs, clients subscribing to messages published by the MongoDB database connector benefit from features like [connection-recovery](/docs/connect/states), [exactly-once delivery](/docs/platform/architecture/idempotency) and [ordering guarantees](https://faqs.ably.com/reliable-message-ordering-for-connected-clients) out of the box.
diff --git a/src/pages/docs/livesync/postgres/index.mdx b/src/pages/docs/livesync/postgres/index.mdx
index 5567b410f9..91cd03eee8 100644
--- a/src/pages/docs/livesync/postgres/index.mdx
+++ b/src/pages/docs/livesync/postgres/index.mdx
@@ -111,8 +111,8 @@ The Postgres database connector automatically listens for new records written to
The following describes the key columns in the outbox table:
- `channel`: the name of the channel the outbox record will be published to.
-- `name`: the [name](/docs/channels/messages#properties) given to the message.
-- `data`: the [data](/docs/channels/messages#properties) carried in the message.
+- `name`: the [name](/docs/messages#properties) given to the message.
+- `data`: the [data](/docs/messages#properties) carried in the message.
- `mutation_id` is the identifier for the mutation. Required for use with [frontend data models](/docs/livesync/postgres/models) and [optimistic updates](/docs/livesync/postgres/models#optimistic-updates).
The following table describes the full schema of the outbox table in your database:
diff --git a/src/pages/docs/livesync/postgres/models.mdx b/src/pages/docs/livesync/postgres/models.mdx
index 0801e0391a..b674a248e8 100644
--- a/src/pages/docs/livesync/postgres/models.mdx
+++ b/src/pages/docs/livesync/postgres/models.mdx
@@ -9,7 +9,7 @@ The Models SDK extends the capability of the LiveSync Postgres database connecto
## How it works
```sql
diff --git a/src/pages/docs/livesync/postgres/quickstart.mdx b/src/pages/docs/livesync/postgres/quickstart.mdx
index 525dff7fdd..726a6f83af 100644
--- a/src/pages/docs/livesync/postgres/quickstart.mdx
+++ b/src/pages/docs/livesync/postgres/quickstart.mdx
@@ -132,7 +132,7 @@ setModel(model);
The sync function is used by the Models SDK to fetch the latest data from your backend to hydrate the application initially upon load. There are two objects returned within the response:
-- [`sequenceId`](/docs/livesync/models#sequence-id), which is used to identify the point in the stream of change events that corresponds to the current version of the database's state.
+- [`sequenceId`](/docs/livesync/postgres/models#sequence-id), which is used to identify the point in the stream of change events that corresponds to the current version of the database's state.
- The data relevant to the expected data model, in this instance, it's the current state of the post defined by its `id`. In this example, the sync function called is [`getPost`](https://github.com/ably-labs/live-comments/lib/models/hook.ts#L11-L29), which is found in the `/lib/models/hook.ts` file of the repository you cloned.
@@ -213,7 +213,7 @@ There are two parts of the backend that are key for the LiveSync integration in
#### The sync function
```javascript
@@ -258,5 +258,5 @@ export async function withOutboxWrite(
This quickstart introduced the basic concepts of LiveSync and provided a quick demo to illustrate how LiveSync works. The next steps are to:
-* Read more about [LiveSync Models](/docs/livesync/models).
+* Read more about [LiveSync Models](/docs/livesync/postgres/models).
* Find out more about the [Database Connector](/docs/livesync/postgres).
diff --git a/src/pages/docs/metadata-stats/stats.mdx b/src/pages/docs/metadata-stats/stats.mdx
index 1d3206f039..87df7857cb 100644
--- a/src/pages/docs/metadata-stats/stats.mdx
+++ b/src/pages/docs/metadata-stats/stats.mdx
@@ -634,7 +634,7 @@ Connection metrics include all realtime [connections](/docs/connect) made to Abl
| **connections.all.min** | Minimum connection count. |
| **connections.all.mean** | Mean connection count. |
| **connections.all.opened** | Total number of connections opened. |
-| **connections.all.refused** | Total number of connections refused, for example for exceeding the [connection creation rate](/docs/platform/pricing/limits/connection). |
+| **connections.all.refused** | Total number of connections refused, for example for exceeding the [connection creation rate](/docs/platform/pricing/limits#connection). |
### Channels
An [Enterprise](/docs/platform/pricing/enterprise) account is required to use organizations. [Contact us](https://ably.com/support) to enable organizations for your account.
diff --git a/src/pages/docs/platform/ai-llms/index.mdx b/src/pages/docs/platform/ai-llms/index.mdx
index 42a03a8203..656541511d 100644
--- a/src/pages/docs/platform/ai-llms/index.mdx
+++ b/src/pages/docs/platform/ai-llms/index.mdx
@@ -22,7 +22,7 @@ These markdown versions strip out navigation and UI elements, providing clean co
### llms.txt
-The [`llms.txt`](/docs/ai-llms/llms-txt) file provides a complete index of all documentation pages, organized by product category. Access it at:
+The [`llms.txt`](/docs/platform/ai-llms/llms-txt) file provides a complete index of all documentation pages, organized by product category. Access it at:
```text
diff --git a/src/pages/docs/platform/errors/codes.mdx b/src/pages/docs/platform/errors/codes.mdx
index 0e6eb53a13..acac0bd4e4 100644
--- a/src/pages/docs/platform/errors/codes.mdx
+++ b/src/pages/docs/platform/errors/codes.mdx
@@ -73,7 +73,7 @@ Examples of this error are when:
## 40009: Maximum message length exceeded
-Webhook messages are subject to rate [limits](/docs/pricing/limits#integrations), similar to REST publishes.
+Webhook messages are subject to rate [limits](/docs/platform/pricing/limits#integrations), similar to REST publishes.
## Configure an incoming webhook
-If you want to send data from Kafka to Ably, you can use the [Ably Kafka Connector.](/docs/general/kafka-connector)
+If you want to send data from Kafka to Ably, you can use the [Ably Kafka Connector.](/docs/platform/integrations/inbound/kafka-connector)
## Create a Kafka integration
-This feature is only available to [enterprise](/docs/pricing/enterprise) packages.
+This feature is only available to [enterprise](/docs/platform/pricing/enterprise) packages.
## Create a Pulsar integration ` header. If using token auth, you can use an `accessToken` querystring parameter or an `Authorization: Bearer ` header. See [REST API authentication](/docs/auth) for more information.
@@ -169,7 +169,7 @@ You can subscribe to messages in delta mode, using the SSE transport, as follows
eventSource.onmessage = function(event) {
/* event.data is JSON-encoded Ably Message
- (see https://ably.com/docs/docs/realtime/types#message) */
+ (see https://ably.com/docs/api/realtime-sdk/types#message) */
var message = JSON.parse(event.data);
var { id, extras } = message;
var { data } = message;
diff --git a/src/pages/docs/push/configure/device.mdx b/src/pages/docs/push/configure/device.mdx
index d3a740ecb1..199e06c03c 100644
--- a/src/pages/docs/push/configure/device.mdx
+++ b/src/pages/docs/push/configure/device.mdx
@@ -543,7 +543,7 @@ private ClientOptions GetAblyOptions(string clientId)
#### Test your push notification activation
Push subscriptions do not count toward your connection limit since devices don't need to maintain an active connection to receive push notifications. However, publishing push notifications via channels does activate those channels, so your concurrent peak channel count will equal the number of channels you publish to simultaneously.
@@ -53,7 +53,7 @@ Publish push notifications using Ably via [channels](/docs/push/publish#channel-
* Publishing directly allows for the delivery of push notifications straight to individual devices or browsers. This process is beneficial for targeting a specific device or browser using a unique [`deviceId`](/docs/push/publish#device-id), [`clientId`](/docs/push/publish#client-id), or [`recipient`](#recipient). Direct publishing is akin to sending a personal, targeted message to a user's device or browser.
-* Publishing via channels operates similarly to Ably's [Pub/Sub](/docs/channels/messages) messaging model, broadcasting notifications to all channel subscribers. This process leverages Ably [channels](/docs/channels) to distribute push notifications efficiently to all devices or browsers subscribed to those channels. It is ideal for scenarios where the same information, such as alerts or updates, needs to be sent to multiple users.
+* Publishing via channels operates similarly to Ably's [Pub/Sub](/docs/messages) messaging model, broadcasting notifications to all channel subscribers. This process leverages Ably [channels](/docs/channels) to distribute push notifications efficiently to all devices or browsers subscribed to those channels. It is ideal for scenarios where the same information, such as alerts or updates, needs to be sent to multiple users.
#### Subscribe
diff --git a/src/pages/docs/spaces/space.mdx b/src/pages/docs/spaces/space.mdx
index e544e70d21..f794c9602e 100644
--- a/src/pages/docs/spaces/space.mdx
+++ b/src/pages/docs/spaces/space.mdx
@@ -130,7 +130,7 @@ The following events will trigger a space event:
Space state contains a single object called `members`. Any events that trigger a change in space state will always return the current state of the space as an array of `member` objects.
-[Avatar stacks](/docs/spaces/avatar) and [member location](/docs/spaces/locations) events can be subscribed to on their individual namespaces; `space.members` and `space.locations`. These events are filtered versions of space state events. Only a single [message](/docs/channels/messages) is published per event by Ably, irrespective of whether you register listeners for space state or individual namespaces. If you register listeners for both, it is still only a single message.
+[Avatar stacks](/docs/spaces/avatar) and [member location](/docs/spaces/locations) events can be subscribed to on their individual namespaces; `space.members` and `space.locations`. These events are filtered versions of space state events. Only a single [message](/docs/messages) is published per event by Ably, irrespective of whether you register listeners for space state or individual namespaces. If you register listeners for both, it is still only a single message.
The key difference between subscribing to space state or to individual feature events is that space state events return the current state of the space as an array of all members in each event payload. Individual member and location event payloads only include the relevant data for the member that triggered the event.