• |
POST - http://<archivemanager>/API/v1/logins.xml |
• |
PUT - http://<archivemanager>/API/v1/logins/15.xml |
• |
OK – http://<archivemanager>/API/v1/logins/1/mailboxes |
• |
BAD – http://<archivemanager>/API/v1/logins/1/mailboxes/2/messages |
• |
OK – http://<archivemanager>/API/v1/mailboxes/2/messages |
• |
limit: specifies the maximum number of entries to display on a single page. If not specified, the setting WWW Page Size (default value: 20) in Configuration Console will be applied.To display all the entries on a single page, set limit to 0. |
• |
• |
top: specifies the maximum number of entries to retrieve. Effective when the lastId parameter is not specified. |
• |
Data objects can be filtered if the API supports for the parameter fields. Use commas to separate multiple field properties. |
• |
When creating a new mailbox, if no OwnerLoginId is provided, the currently logged in user's LoginId is used. If an OwnerLoginId is provided, the newly-created mailbox is owned by that user. If the mailbox is created using a login's Mailboxes sub-collection, access to the mailbox is delegated to the login specified. |
• |
X-ApplicationId: ApiTestApplication |
• |
• |
X-QueryId: Returns the current query ID for you to perform the same query with it if needed. |
• |
rel=”next”: Navigates to the subsequent page of results when the parameter lastId is specified. |
• |
API access can be over HTTP or HTTPS, using the URL prefix: http://<archivemanager>/API or https://<archivemanager>/API. The <archivemanager> specifies the domain name or IP address of the server where the REST service endpoint is hosted. The reference documentation for each API call shows the REST resource, method, and parameters that must be appended to the base URL to form a request. The following is an example of a well-formed REST URL: http://<archivemanager>/API/v1/logins. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center