# - Entry

Get Entry Requirements for destinations as HTML, Text, JSON or a PDF document.

Use: \
.../content/entry/html - to show content in a web browser / HTML viewer. \
.../content/entry/text - to show content directly as text. \
.../content/entry/json - to show your own content based on data. \
.../content/entry/pdf - to save & share content for offline viewing.

Endpoint: POST /content/entry/{type}
Version: 2.0.0
Security: oAuth, bearerAuth

## Path parameters:

  - `type` (any, required)
    Enum: "html", "text", "json", "pdf"

## Query parameters:

  - `language` (string)
    Language code for response content.
    Enum: "de", "en", "fr", "it", "nl", "pl", "es", "pt", "ru", "bg", "cs", "da", "el", "fi", "hu", "nb", "ro", "sk", "sl", "sv", "tr"

  - `destinations` (string)
    Comma separated list of destination country codes.
    Example: "ES,FR,IT"

  - `nationalities` (string)
    Comma separated list of travellers' nationality codes.
    Example: "DE,AT"

  - `target_device` (string)
    Send this parameter if the content is to be displayed on a device with limited screen space.
    Enum: "mobile"

## Request fields (application/json):

  - `filters` (object)

  - `filters.documents` (object)

  - `filters.documents.document_code` (object)
    The 'document_code' key should be one of the document keys supported by API. You can get possible values by using .../api/v2/entry/documents endpoint.

  - `filters.documents.document_code.entry_allowed` (boolean)

  - `filters.additional_info` (object)

  - `filters.additional_info.list` (object)

  - `filters.additional_info.list.code` (object)
    The code key should be one of the keys supported by API. You can get possible values by using .../api/v2/entry/additional-info endpoint.

  - `filters.additional_info.list.code.status` (string)
    Enum: "not_required", "required"


## Response 401 fields