> For the complete documentation index, see [llms.txt](https://dev.ropo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ropo.com/guides/basics/invoice/cover-page.md).

# Cover page

Use a cover page when you send a ready-made PDF that does not follow Ropo's print layout.

Ropo adds the cover page as the first page. The sender and receiver details stay visible in the envelope window. The actual letter stays hidden behind the cover page.

Cover page is only used for printed documents. If the document is delivered through a digital channel, the cover page is not used.

### How to enable

Set `post_cover_letter` in the dataset-level `propertyrow` when you post a new job to Ropo One.

### Request example

Add `post_cover_letter` to the dataset-level `propertyrow` of the same document payload as the PDF you send.

```json
{
  "datastream": {
    "dataset": [
      {
        "jobtype": "301",
        "sendtype": "post",
        "customertype": "2",
        "person": "Nelli Niirulainen",
        "address": "Kellokoskenkatu 15 A 3",
        "postcode": "70100",
        "city": "KUOPIO",
        "propertyrow": [
          {
            "propname": "post_cover_letter",
            "propvalue": "1"
          }
        ],
        "image": {
          "filename": "letter.pdf",
          "file": "<base64-pdf>"
        }
      }
    ]
  }
}
```

Use `propvalue` `1` to enable the cover page.

### When to use it

* The PDF is already finalized.
* The PDF does not match Ropo's layout instructions for printing.
* You need the sender and receiver details visible in the envelope window.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.ropo.com/guides/basics/invoice/cover-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.