--- title: "Parameters" source: https://dev.pageseeder.com/api/usage/parameters.html description: "Comprehensive guide to PageSeeder service parameters, covering basic and common datatypes, constraints, format requirements, paging mechanisms, and API versioning conventions." last_updated: 2026-09-08T11:47:06+10:00 tokens: ~2254 --- # Parameters Most services accept or require parameters. For some parameters, specific constraints apply to their values. The datatypes below provide an indication of what PageSeeder expects and what is likely to cause an error. > **Note:** The name of the datatype is not case sensitive. For example, *string* and *String* refer to the same type. ## Basic types ### String (default) A single string of characters. This is the default type. If no data type is specified in the documentation, developers should assume that the parameter can accept any string value. Unless specified otherwise, a string value has no maximum length and can contain any Unicode characters. Always reference the parameter description for additional constraints. ### Integer An integer value from -2,147,483,648 to 2,147,483, 647. ### Long A long value is a (64-bit signed two's complement) integer value.  If it is the type used for an ID, such as a Member ID or Group ID, it must be **strictly positive**. ### Boolean The value can be either `true` or `false`. Unless specified otherwise, the value is case-sensitive. ### Date All dates should use the ‘-’ delimited ISO 8601 calendar date format (YYYY-MM-DD). The timezone information is not required. Unless specified otherwise, the default timezone value is that of the server. For example: `2018-12-31` ### Datetime All dates should use the ‘-’ delimited ISO 8601 calendar datetime format (YYYY-MM-DD'T'hh:mm:ssZ). The timezone information may be provided. Unless specified otherwise, the default timezone value is that of the server. For example: `2012-11-23T22:35:12+10:00` ### Enum A value in a list of enumerated values. Generally, the list of possible values will be in the parameter description. ### Email A valid email address. See [RFC 5322 - Internet Message Format](http://tools.ietf.org/html/rfc5322). ### URL A valid URL. See [RFC 3986 - Uniform Resource Identifier](https://datatracker.ietf.org/doc/html/rfc3986). ### Mediatype A valid media type (without any encoding information) from the list of media types defined in the [MIME Properties](../../guide/configuration/properties/mime_properties.md). ## Common types The types below correspond to other commonly used types for parameters introduced to clarify and simplify the documentation. In some cases, the documentation may still refer to a basic type instead. ### Host A host as specified by [RFC 3986 - 3.2.2 Host](https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.2). In most cases, a parameter of type *host* refers* *to a host in PageSeeder or one of its aliases. The default host is defined in the [global properties](../../guide/configuration/properties/global_properties.md). ### Label A valid label name, it can only contain the following characters `[a-z][A-Z][0-9][-_]` . ### Labels A comma separated list of label names, it can only contain the following characters `[a-z][A-Z][0-9][-_,]` . ### Notification Defines how a member receives an event notification for a particular group: - `none` – only notify of special group announcements (aka Announcements only). - `essential` – only notify relevant task assignments and replies to posts. - `immediate` – notify immediately for all new comments and tasks (aka Normal). - `daily` – Essential setting plus a digest daily of new comments and tasks. - `weekly` – Essential setting plus a weekly digest of new comments and tasks. For more information, *see* [Notification](../../reference/glossary/notification.md). ### Notify Defines which members will receive a notification of the [comment](../../reference/glossary/comment.md), [task](../../reference/glossary/task.md), [workflow](../../reference/glossary/workflow.md), document or URL update: - `normal` – notify according to the notification settings of each member. - `announce` – notify regardless of the member notification settings. - `minimal` – notify only the discussion authors, assigned member and depending on status, the group approvers. Discussion authors are not included for workflows. - `silent` – no notification. > **Note:** If comment `contentype` is not `text/plain`, then  notify will automatically default to `silent`. When a member with a role of Reviewer or below adds a comment/task, `notify` is forced to `normal`. This can be overridden if the member is an Administrator. For more information, *see* [Notification](../../reference/glossary/notification.md). ### Path A valid path using '/' as a file separator. ### Port A parameter of type *port*, must be a positive integer between 1 and 65535. See [RFC 3986 - 3.2.3 Port](https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.3). The default port is defined in the *global properties*. ### Priority A parameter of type *priority*, should be one of the priority values defined in the [Group Properties](../../guide/configuration/properties/group_properties.md). It can only contain the following characters `[a-z][A-Z][0-9][, -_]` . The default priority values are `High`, `Medium`, `Low`. > **Note:** The system will tolerate values other than the ones defined in the group properties; and will not throw an error if different values are used. However, best practice recommends using parameter values that match the group properties. ### Publicationid A valid publication ID contains only the following characters `[a-z][A-Z][0-9][-_]` and can be up to 250 characters long. ### Publicationtype A valid value for a publication type contains only the following characters `[a-z][A-Z][0-9][-]` and can be up to 250 characters long. ### Scheme A scheme as specified by [RFC 3986 - 3.1 Scheme](https://datatracker.ietf.org/doc/html/rfc3986#section-3.1). PageSeeder does not enforce the use of a particular scheme, but there is no reason to use a scheme other than `http` or `https`. The default scheme is defined in the [global properties](../../guide/configuration/properties/global_properties.md). ### Status A parameter of type *status* should be one of the status values defined in the [Group Properties](../../guide/configuration/properties/group_properties.md). Multiple properties define status values based on either [task status](../../reference/glossary/task_status.md) or [document status](../../reference/glossary/document_status.md). It can only contain the following characters `[a-z][A-Z][0-9][, -_]` . - For tasks, the default status values are `Open`, `Resolved`, `Closed`. - For workflows, they are `Initiated`, `In progress`, `Complete`, `Suspended`, `Terminated` > **Note:** The system will tolerate values other than the ones defined in the group properties; and will not thrown an error if different values are used. However, best practice recommends using parameter values that match the group properties. ## Paging Most services that return collections of objects provide a paging mechanism using the `page` and `pagesize` parameters. > **Note:** Unless specified otherwise, if the value of  `page` or `pagesize` is not a positive integer, the system will ignore it and fall back to the default value. ### Pagesize The `pagesize` parameter defines the maximum number of objects to return for each page. Services should specify which elements are counted. Unless specified otherwise the maximum possible value for the `pagesize` is 10000. ### Page The `page` returns the collection of objects that correspond to that page after the entire collection has been divided up based on the `pagesize` parameter. Many services implement the paging efficiently so that the entire collection needn't be loaded. The default value for `page` is 1, a request for a page number that greater than the available pages will return an empty collection. ## Other conventions When the plural is used, it usually indicates a comma separated list of values. ## The ‘`v`’ parameter The `v` parameter on any service URL will call a specific version of the web services API. The value of this parameter is the corresponding PageSeeder version with an optional `;strict` afterwards (e.g. `v=5.9200;strict` ). Each service can have `@since`,  `@deprecated` and `@obsolete` PageSeeder version numbers associated with it. The `;strict` suffix or the global PageSeeder property `serviceStrict=true` will invoke strict mode. The rules applied are as follows: - If requested service has `@obsolete`, return `410 "Gone"` error AND set header: ```text Warning: 299 - "Obsolete API [(strict)]" "[@obsolete]" ``` - If requested service has `@deprecated`, set header: ```text Warning: 299 - "Deprecated API [(strict)]" "[@deprecated]" ``` - If `v` is before `@since` on requested service, set header: ```text Warning: 299 - "Since API [(strict)]" "[@obsolete]" ``` - If `v` is after or equal to `@deprecated` on requested service AND strict mode, return `410 "Gone"` error - If `v` is before `@since` on requested service AND strict mode, return `404 "Not found"` error With no `v` parameter on the request, `v` is the current PS version.