> For the complete documentation index, see [llms.txt](https://docs.silk.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silk.us/api-reference/endpoints/replication/rpo-history.md).

# RPO history

The history of replication rounds for each replication session. Each round records when it started and ended, its target RPO, and how much data it transmitted.

Use this endpoint to confirm that replication is meeting its recovery point objective (RPO), or to investigate rounds that took longer than expected. By default, it returns the last 100 rounds, newest first.

## Get RPO history

> Returns the history of replication rounds. By default the API returns the last 100 items, sorted in descending order by \`round\_start\`.\
> \
> Supported filters: \`session\` (\`=\`, \`\_\_in\`), \`role\` (\`=\`, \`\_\_in\`, \`\_\_contains\`, \`\_\_prefix\`), and \`generation\_number\`, \`round\_start\`, \`round\_end\`, \`target\_rpo\`, \`bytes\_transmitted\_logical\`, \`bytes\_transmitted\_physical\` (\`=\`, \`\_\_in\`, \`\_\_gt\`, \`\_\_gte\`, \`\_\_lt\`, \`\_\_lte\`).

```json
{"openapi":"3.0.3","info":{"title":"Silk RESTful API","version":"9.5.20"},"tags":[{"name":"RPO history","description":"The history of replication rounds for each replication session. Each round records when it started and ended, its target RPO, and how much data it transmitted.\n\nUse this endpoint to confirm that replication is meeting its recovery point objective (RPO), or to investigate rounds that took longer than expected. By default, it returns the last 100 rounds, newest first."}],"servers":[{"url":"https://{host-address}/api/v2","description":"Your Silk Data Pod (SDP)","variables":{"host-address":{"default":"sdp.example.com","description":"Management address of your SDP."}}}],"security":[{"basicAuth":[]}],"components":{"securitySchemes":{"basicAuth":{"type":"http","scheme":"basic","description":"HTTP Basic authentication. The server responds only to HTTPS requests. Access to object URLs, operations, and fields depends on the user's role (for example `admin` or `viewer`)."}},"parameters":{"limit":{"name":"__limit","in":"query","schema":{"type":"integer"},"description":"Caps the number of returned entities. Requires a sort parameter when paging."},"offset":{"name":"__offset","in":"query","schema":{"type":"integer"},"description":"Returns results starting from this offset. Requires a sort parameter when paging."},"sort":{"name":"__sort","in":"query","schema":{"type":"string"},"description":"Comma-separated object properties to sort by."},"sort_order":{"name":"__sort_order","in":"query","schema":{"type":"string","enum":["asc","desc"]},"description":"Sort direction."}},"schemas":{"Collection":{"type":"object","properties":{"hits":{"type":"array","items":{},"description":"The matching objects."},"limit":{"type":"integer","description":"Page size."},"offset":{"type":"integer","description":"Offset of the first returned object."},"total":{"type":"integer","description":"Total number of matching objects."}}},"ReplicationRpoHistory":{"type":"object","properties":{"session":{"$ref":"#/components/schemas/Ref","description":"Reference to the replication session this history record belongs to. Shape: `{ \"ref\": \"/replication/sessions/{id}\" }`."},"generation_number":{"type":"integer","description":"Generation/round number for the session."},"role":{"type":"string","description":"Role of this SDP for the round, e.g. `target` or `source`."},"round_start":{"type":"integer","description":"Unix timestamp when the round started."},"round_end":{"type":"integer","description":"Unix timestamp when the round ended. `0` indicates the round has not yet completed."},"target_rpo":{"type":"integer","description":"Target RPO in seconds in effect for the round."},"bytes_transmitted_logical":{"type":"integer","description":"Logical bytes transmitted during the round."},"bytes_transmitted_physical":{"type":"integer","description":"Physical bytes transmitted during the round."}}},"Ref":{"type":"object","description":"Reference to another object by its canonical URL.","properties":{"ref":{"type":"string"}},"required":["ref"]},"Error":{"type":"object","properties":{"message":{"type":"string","description":"Readable description of the error."}}}},"responses":{"Error":{"description":"Error. See the **Errors** page for status codes.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}}},"paths":{"/replication/rpo_history":{"get":{"tags":["RPO history"],"summary":"Get RPO history","operationId":"listReplicationRpoHistory","description":"Returns the history of replication rounds. By default the API returns the last 100 items, sorted in descending order by `round_start`.\n\nSupported filters: `session` (`=`, `__in`), `role` (`=`, `__in`, `__contains`, `__prefix`), and `generation_number`, `round_start`, `round_end`, `target_rpo`, `bytes_transmitted_logical`, `bytes_transmitted_physical` (`=`, `__in`, `__gt`, `__gte`, `__lt`, `__lte`).","parameters":[{"$ref":"#/components/parameters/limit"},{"$ref":"#/components/parameters/offset"},{"$ref":"#/components/parameters/sort"},{"$ref":"#/components/parameters/sort_order"}],"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/Collection"},{"type":"object","properties":{"hits":{"type":"array","items":{"$ref":"#/components/schemas/ReplicationRpoHistory"}}}}]}}}},"default":{"$ref":"#/components/responses/Error"}}}}}}
```

## GET /replication/rpo\_history/{id}

> Get RPO history for a session

```json
{"openapi":"3.0.3","info":{"title":"Silk RESTful API","version":"9.5.20"},"tags":[{"name":"RPO history","description":"The history of replication rounds for each replication session. Each round records when it started and ended, its target RPO, and how much data it transmitted.\n\nUse this endpoint to confirm that replication is meeting its recovery point objective (RPO), or to investigate rounds that took longer than expected. By default, it returns the last 100 rounds, newest first."}],"servers":[{"url":"https://{host-address}/api/v2","description":"Your Silk Data Pod (SDP)","variables":{"host-address":{"default":"sdp.example.com","description":"Management address of your SDP."}}}],"security":[{"basicAuth":[]}],"components":{"securitySchemes":{"basicAuth":{"type":"http","scheme":"basic","description":"HTTP Basic authentication. The server responds only to HTTPS requests. Access to object URLs, operations, and fields depends on the user's role (for example `admin` or `viewer`)."}},"schemas":{"Collection":{"type":"object","properties":{"hits":{"type":"array","items":{},"description":"The matching objects."},"limit":{"type":"integer","description":"Page size."},"offset":{"type":"integer","description":"Offset of the first returned object."},"total":{"type":"integer","description":"Total number of matching objects."}}},"ReplicationRpoHistory":{"type":"object","properties":{"session":{"$ref":"#/components/schemas/Ref","description":"Reference to the replication session this history record belongs to. Shape: `{ \"ref\": \"/replication/sessions/{id}\" }`."},"generation_number":{"type":"integer","description":"Generation/round number for the session."},"role":{"type":"string","description":"Role of this SDP for the round, e.g. `target` or `source`."},"round_start":{"type":"integer","description":"Unix timestamp when the round started."},"round_end":{"type":"integer","description":"Unix timestamp when the round ended. `0` indicates the round has not yet completed."},"target_rpo":{"type":"integer","description":"Target RPO in seconds in effect for the round."},"bytes_transmitted_logical":{"type":"integer","description":"Logical bytes transmitted during the round."},"bytes_transmitted_physical":{"type":"integer","description":"Physical bytes transmitted during the round."}}},"Ref":{"type":"object","description":"Reference to another object by its canonical URL.","properties":{"ref":{"type":"string"}},"required":["ref"]},"Error":{"type":"object","properties":{"message":{"type":"string","description":"Readable description of the error."}}}},"responses":{"Error":{"description":"Error. See the **Errors** page for status codes.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}}},"paths":{"/replication/rpo_history/{id}":{"get":{"tags":["RPO history"],"summary":"Get RPO history for a session","operationId":"getReplicationRpoHistory","responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/Collection"},{"type":"object","properties":{"hits":{"type":"array","items":{"$ref":"#/components/schemas/ReplicationRpoHistory"}}}}]}}}},"default":{"$ref":"#/components/responses/Error"}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.silk.us/api-reference/endpoints/replication/rpo-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
