1 User web services specification
2 ===============================
4 Source: Provozní řád ISDS, version 2016-02-07
5 Source: Webové služby rozhraní ISDS pro manipulaci s datovými zprávami,
6 version 2.48 (2015-11-01)
7 Source: Webové služby ISDS pro vyhledávání datových schránek,
8 version 2.48 (2015-11-01)
11 These services are intended for working with messages inside a box by
14 SOAP web services defined in: dm_operations.wsdl, dm_info.wsdl, db_search.wsdl
15 (Appendix 2 of Provozní řád ISDS)
17 Data types: dmBaseTypes.xsd (Appendix 1)
19 Documentation: DataMessage_ws.pdf, DBSearch_ws.pdf (Appendix 2)
21 List of SOAP requests follows. Those marked with asterisk DO NOT MARK incoming
22 messages as delivered. Those marked with plus has access to envelopes of
30 Constraints: Client must be authenticated in Access Manager
33 Create and send a message
34 CreateMultipleMessage (*)
35 Create and send a message to multiple recipients
37 Download incoming message
39 Download incoming message with digital signature of ministry of interiors
40 SignedSentMessageDownload
41 Download outgoing message with digital signature of ministry of interiors
42 AuthenticateMessage (*+)
43 Submit local message copy to ISDS to confirm message authenticity
44 Re-signISDSDocument (*)
45 Replace CMS signature of old message signed without time stamp
47 Void operation used to log in and to keep connection alive
54 Constraints: Client must be authenticated in Access Manager
57 Verify local copy of message with remote original stored in ISDS
58 MessageEnvelopeDownload (+)
59 Download envelope of incoming message
60 MarkMessageAsDownloaded (*)
63 Mark commercial message as accepted by recipient
65 Remove message from long term storage
67 Download info-sheet about message post and delivery
68 GetSignedDeliveryInfo (+)
69 Download info-sheet about message post and delivery with signature of
71 GetListOfRecievedMessages
72 Download list of incoming messages
74 Download list of outgoing messages
76 Get details about sender
77 GetMessageStateChanges
78 Download list of outgoing messages that changed state
87 Find boxes conforming to search criteria
88 FindPersonalDataBox (*)
89 Search for active personal boxes
91 Return state of given box
95 Get rules for sending commercial messages from given box
97 Get details about credit for comercial services
99 Search for boxes conforming to full text criteria
100 GetDataBoxActivityStatus (*)
101 Get history of box accessibility states
107 Create and send a message.
109 Envelope of outgoing message must contain dbIDRecipient and dmAnnotation.
110 Other elements are optional (dmRecipientOrgUnit, dmRecipientOrgUnitNum,
111 dmSenderOrgUnit, dmSenderOrgUnitNum, dmToHands, dmPersonalDelivery,
112 dmAllowSubstDelivery, dmRecipientRefNumber, dmRecipientIdent,
113 dmSenderRefNumber, dmSenderIdent, dmLegalTitleLaw, dmLegalTitleYear,
114 dmLegalTitleSect, dmLegalTitlePar, dmLegalTitlePoint, dmOVM, dmPublishOwnID).
116 Outgoing message envelope can specify dmType to declare subtype of commercial
117 message. If dmType is `I', then dmSenderRefNumber must be defined. If dmType
118 is `O', then dmRecipientRefNumber must be defined.
120 Constraints: Sender must have PRIVIL_CREATE_DM permission.
121 Constraints: Exactly one document in message must be main type.
122 Constraints: Total size of all documents must not be bigger than a limit
123 (20 MB usually, depends on a box).
125 Identifier of just sent message assigned by system is returned.
128 0000 Message sent successfully
129 Non-normative error codes:
130 1214 Document description is not a file name with acceptable file name
132 1214 Document description extension does not match document content
133 1214 Provided MIME type does not match document
134 2010 First document structure invalid
135 2032 Message does not carry any document
136 9005 Message not valid (probably)
138 In case of positive virus detection (processed after sending), infected
139 document is removed, message state is set to value 3 (from point of view of
140 recipient) and sender get new message originated by server.
143 CreateMultipleMessage (*)
144 =====================
146 Create and send a message to multiple recipients.
148 Input composes of nonempty list of recipients (maximal count is 50),
149 one envelope (different from envelope for CreateMessage, misses elements from
150 dmRecipient) and list of documents to send to all of them to each recipient.
152 Only dbIDRecipient and dmToHands are mandatory. Other dmRecipient children are
156 CreateMultipleMessage
159 | | + dbIDRecipient – recipient box ID
160 | | + dmRecipientOrgUnit
161 | | + dmRecipientOrgUnitNum
162 | | + dmToHands – can be empty, but must not missing
166 | + <other elements, usually empty>: dmSenderOrgUnit, dmSenderOrgUnitNum,
167 | | dmAnnotation, dmRecipientRefNumber, dmSenderRefNumber,
168 | | dmRecipientIdent, dmSenderIdent, dmLegalTitleLaw,
169 | | dmLegalTitleYear, dmLegalTitleSect, dmLegalTitlePar,
170 | | dmLegalTitlePoint, dmPersonalDelivery, dmAllowSubstDelivery
172 | + dmPublishOwnID – optional
175 It's not possible to send commercial message to multiple recipients. Though the
176 dmEnvelope has @dmType attribute, so it should be possible to send a commercial
177 message to one recient using CreateMultipleMessage service.
179 ISDS outputs list of assigned message IDs (each copy gets independent ID),
180 list of sent status for each message ID and one cumulative status of
181 whole CreateMultipleMessage operation.
183 If operation fails before replicating messages for each recipient
184 (i.e. sending), global error code will be non-zero. If operation fails on some
185 message copies (i.e. while sending) special global error code 0004 will be
186 returned and erroneous recipients can be gather by recipient specific error
187 code (failed ones will have non-zero code). If all messages are sent
188 successfully, global error code will be 0000.
191 CreateMultipleMessageResponse
194 | | + dmID – assigned message ID, optional, missing if error occurred
195 | | + dmStatus – message local error code and textual description
198 + dmStatus – global error code and textual description
201 0000 Messages sent successfully
202 0004 Some message failed while sending
208 Retrieve incoming message identified by message ID.
210 This service can return message without digital time-stamp (more precisely
211 with empty dmQTimesamp element, see schema).
213 Commercial message has set dmReturnedMessage/@dmType="K".
216 0000 Message sent successfully
217 Non-normative error codes:
218 1219 Message with ID does not exist in ISDS in current box.
221 SignedMessageDownload
222 =====================
224 Download incoming message with digital signature of ministry of interiors
225 identified by message ID.
227 Return PKCS#7 structure containing data as defined in MessageDownload and
228 digital signature of the message by ministry.
230 The data are XML document with mangled ISDS name space:
231 http://isds.czechpoint.cz/v20/ vs. http://isds.czechpoint.cz/v20/message:
233 <q:MessageDownloadResponse
234 xmlns:q="http://isds.czechpoint.cz/v20/message">
235 <q:dmReturnedMessage>
236 <p:dmDm xmlns:p="http://isds.czechpoint.cz/v20">
237 <p:dmID>151916</p:dmID>
240 <q:dmHash algorithm="SHA-1">...</q:dmHash>
242 <q:dmAttachmentSize>260</q:dmAttachmentSize>
243 </q:dmReturnedMessage>
244 </q:MessageDownloadResponse>
247 SignedSentMessageDownload
248 =========================
250 Download outgoing message with digital signature of ministry of interiors
253 Return PKCS#7 structure containing data as defined in MessageDownload and
254 digital signature of the message by ministry.
256 The data are XML document with mangled ISDS name space:
257 http://isds.czechpoint.cz/v20/ vs. http://isds.czechpoint.cz/v20/SentMessage:
259 <q:MessageDownloadResponse
260 xmlns:q="http://isds.czechpoint.cz/v20/SentMessage">
261 <q:dmReturnedMessage>
262 <p:dmDm xmlns:p="http://isds.czechpoint.cz/v20">
263 <p:dmID>151916</p:dmID>
266 <q:dmHash algorithm="SHA-1">...</q:dmHash>
268 <q:dmAttachmentSize>260</q:dmAttachmentSize>
269 </q:dmReturnedMessage>
270 </q:MessageDownloadResponse>
273 1229 This just sent message has not yet been signed
276 GetListOfRecievedMessages
277 =========================
279 Download list of incoming messages matching search criteria.
281 See GetListOfSentMessages for more details.
284 GetListOfSentMessages
285 =====================
287 Download list of outgoing messages matching search criteria.
289 Criteria are: delivery time not before, not after, organisation unit number of
290 sender, message status filter, offset of first message in a list and limit on
291 number of messages to get.
293 Message status filter is union of distinct message states expressed as
294 exponents of 2. Effectively it's a polynom \sum_{x \in message_statux} 2^x.
295 Special value -1 means all messages. Meaning for value 1 or 0 is undefined.
297 Messages are sorted in order of delivery time. Message type is stored in
300 Offset starts on 1. Limit defaults to 1000.
302 Non-normative error codes:
303 2017 Syntax error in date-time
309 Get information about sender as un user of given message.
311 Input is mandatory message identifier. Output is optional userType and
314 userType (unknown and undefined for older messages) is type of user who has
315 sent the message. Be ware there is special additional type `VIRTUAL'. Be ware
316 the userType is a string unconstrained by XML schema:
319 --------------------------------------------------------------------------
320 PRIMARY_USER The sender was a owner of the box
321 ENTRUSTED_USER The sender was an entrusted user associated to the box
322 ADMINISTRATOR The sender was administrator assiciated to the box
323 OFFICIAL The sender was ISDS (for system messages)
324 VIRTUAL The sender was an application authenticated by `system'
327 Non-normative: New user types OFFICIAL_CERT and LIQUIDATOR are not listed in
328 official documentation for this service. However LIQUIDATOR is said to be
329 equivalent to PRIMARY_USER and PRIMARY_USER can send messages, thus I conclude
330 these two now user types can occur in output of this service.
332 authorName is a name of user logged into senders box (not a login name) if
333 sender allowed to reveal his name explicitely.
336 GetMessageStateChanges
337 ======================
339 Download list of outgoing messages that changed state in given time range.
341 If a message changed state multiple times, it is listed more times. Only
342 changes from state 2 to 4, from 4 to {5, 6, 8} are reported. Only recent
343 changes (not older than 15 days currently) are reported.
345 This service is designed for polling state changes of sent messages.
347 Input are start (dmFromTime element) and end (dmToTime element) ISO times.
348 Empty dmFromTime meands since last 15 days, empty dmToTime means till now.
350 Server does not report changes recent more than few minutes.
352 Output is list of records with message state changes. The order of records is
356 GetMessageStateChangesResponse
357 + dmRecords – optional, possibly empty element
358 | + dmRecord – one state change
359 | | + dmId – identifier of message that changed state
360 | | + dmEventTime – ISO time of state change
361 | | + dmMessageStatus – new message state in numeric notation
364 + dmStatus – global error code and textual description
367 AuthenticateMessage (*+)
370 Allows to verify message authenticity by providing copy to ISDS.
372 Only signed message encapsuleted into CMS structure with digital signature can
373 be verified by this service. Client pass the raw message in Base64 encoding to
374 ISDS, system performs checks and return boolean value: true if message has
375 not been modified and has been delivered through ISDS, false if message
376 has is unkown to ISDS. In both cases 0000 error code will be returned.
378 If message cannot be processed (e.g. broken CMS or XML syntax) or message
379 contains has been signed by non-ISDS certificate or other error, non-zero
380 error code will be returned.
383 Re-signISDSDocument (*)
386 Re-sign old message or delivery info that has been generated with CMS without
387 time stamp. These messages have been produced before 2011-04-16.
389 Input is dmDoc element carrying Base64-encoded original signed message or
390 delivery info in text node.
392 Output is dmResultDoc element with Base64-encoded re-signed message or
393 delivery info supplied in request, optional dmValidTo element of xs:date type,
394 and dmStatus of tStatus type. dmValidTo advertises end of validity of
395 time stamp added into CMS.
398 0000 Message has been re-signed and returned in CadES-T CMS format
399 2200 Input message is bad
400 2201 Input message is not original (see AuthenticateMessage service)
401 2204 Input message already contains time stamp in CAdES-EPES or CAdES-T
403 2207 Time stamp could not been generated in time
409 Retrieve message hash (dmHash element) for given message from ISDS.
411 Works for not yet deleted messages only.
413 Only SHA-1 algorithm is in use currently. SHA-2 family is expected after
416 Hash input is isds:dmDM subtree processed as raw bit stream without XML
417 canonicalization. Authoritative isds:dmDM element can be get via
418 MessageDownload service. God bless ISDS developers to not change XML
421 Non-normative error codes:
422 1219 Message with ID does not exist in ISDS.
425 MessageEnvelopeDownload (+)
426 =======================
428 Download envelope of incoming message. That is message without documents.
429 Message type is stored in dmReturnedMessageEnvelope/@dmType.
431 Returned hash and time-stamp are computed from whole message. You must get
432 complete message including documents to be able to verify them.
435 MarkMessageAsDownloaded (*)
436 =======================
438 Change status of a message identified by its ID as read.
440 That means next GetListOfRecievedMessages service can exclude such message if
441 only unread messages requested.
447 Mark commercial message as accepted by recipient.
449 XXX: This service has been removed from ISDS because commercial messages get
450 accepted by logging-in (since 2011-11).
452 Changes message state from delivered (4) to accepted (6). Applicable only to
453 commercial messages. Messages from public offices (municipalities, government
454 etc.) are accepted automatically by log-in on interactive web portal or by
455 triggering most of SOAP operations.
457 Must be called before downloading (signed or unsigned) incoming message
458 [Signed]MessageDownload.
464 Delete a message from long term storage (know as data safe formerly).
466 Input is message ID in `dmID' element and boolean in `dmIncoming' element
467 (true for incoming message, false for outgoing mesage).
469 Output is standard `dmStatus' subtree.
471 Only message in long term storage can be removed on user request through
472 this service. Other message cannot be removed on request, they get removed
473 automatically after 90-days period.
476 1211 The message belongs to other (= not currently logged-in user) box
477 1218 Insufficient permissions (PRIVIL_ERASE_VAULT) to remove the message
478 1219 The message is not in long term storage or is not incoming or
479 outgoing as requested.
485 Download info-sheet about incoming or outgoing message post and delivery or
486 deliver impossibility. The message is specified by message ID.
488 It returns complete message envelope, hash, time-stamp. Delivery time and
489 acceptance time only if message has been delivered to recipient box or
490 accepted by recipient. Precise status of message is returned too.
492 In addition, non-empty list of events is attached. Each event compounds of
493 ISO time and text description. The text description has well-known prefix to
494 distinguish the event meaning. Following prefixes are defined:
497 -----------------------------------------------------
498 EV0: Message enterend into ISDS
499 EV1: Message has been accepted by recipient action
500 EV2: Message has been delivered to box and is considered as accepted by
501 no-user-action time out (through fiction)
502 EV3: Recipient box has been made inaccessible retrospectively
503 (even after successful delivery or acceptance,
504 this event is retroactive). In this case special system-generated
505 message is sent to sender in addition.
506 EV4: Commercial message has been accepted by recipient confirmation
507 EV5: Message has been delivered into recipent box
508 EV11: Primary user has logged into his box
509 EV12: Entrusted user havin permission to read this message has logged in
510 EV13: Application (not a human) has logged into box using `system'
514 GetSignedDeliveryInfo (+)
515 =====================
517 Download info-sheet about incoming or outgoing message post and delivery or
518 deliver impossibility as signed PKCS#7 structure. See GetDeliveryInfo for
519 details about returned data.
521 The PKCS#7 structure carries digital signature made by ministry of interiors.
523 There is mangled namespace again: http://isds.czechpoint.cz/v20/ vs.
524 http://isds.czechpoint.cz/v20/delivery:
526 <q:GetDeliveryInfoResponse xmlns:q="http://isds.czechpoint.cz/v20/delivery">
528 <p:dmDm xmlns:p="http://isds.czechpoint.cz/v20">
529 <p:dmID>170272</p:dmID>
532 <q:dmHash algorithm="SHA-1">...</q:dmHash>
534 </q:dmEvents>...</q:dmEvents>
536 </q:GetDeliveryInfoResponse>
542 Find boxes conforming to search criteria or exact ID and return corresponding
543 (possibly truncated) list of boxes.
545 Returned boxes exist, but it does not mean they can receive messages. Use
546 CheckDataBox to figure out.
548 There are three different search cases distinguished in this order:
550 – If dbID is filled in request, it will search for exact box only, other
551 criteria will be ignored.
553 – If identifier and registryCode are filled, it will search for exact
554 box only, other criteria will be ignored.
556 – Otherwise search against other criteria.
558 Returns list of boxes (possibly empty).
560 List can be truncated or search request refused because of not enough
561 specific criteria to protect user privacy. There are following constrains
562 differentiated by box type now:
564 Gross Box type Constraints (required search criteria)
565 ------------------------------------------------------
568 PO ic or prefix (at least 3 characters) of firmName
569 OVM ic or prefix of firmName
571 String search criteria are matched case insensitive (except dbID). Strings are
572 compared to prefix. Except firmName, adCity, adStreet and biCity that are
573 matched as substrings.
575 Search results depends or logged-in user type. Users of boxes with open
576 addressing can search other open-addressing boxes, otherwise only OVM type
577 boxes can be searched. Search based on exact box identifier finder unlimited.
580 0002 No box suits to search request (by other criteria)
581 0003 To much boxes suit to search request (by other criteria),
582 response truncated. Returned list of boxes is still valid.
583 1109 More than one box matches the search request
584 5001 No such box exists (by box ID or registry identifier)
585 Non-normative error codes:
586 1101 Box type (dbType) must be specified
587 2017 Syntax error in date (biDate)
590 FindPersonalDataBox (*)
593 Return list of active FO-type boxes matching given criteria.
595 Input is `dbOwnerInfo' element specifying search criteria for box owner by
596 these children elements:
598 Element Type At search Meaning
599 --------------------------------------------------------------------------------
601 aifoIsds Boolean Ignored Reference to citizen registry exists
602 pnFirstName String Given name
603 pnMiddleName String Middle name
604 pnLastName String Surname
605 biDate Date Birth date
606 biCity String Birth place
607 biCounty String Birth district (`okres' in Czech)
608 biState String Ignored Birth state
609 adCode Integer RUIAN address code
610 adCity String Municipality name
611 adDistrict String Ignored Municipality part
612 adStreet String Street
613 adNumberInStreet String Entrance number
614 adNumberInMunicipality String Building number
615 adZipCode String Ignored Post office code
617 nationality String State citizenship
619 Syntactically, all of the `dbOwnerInfo' children can be empty. Semantically,
620 if `dbID' is specified, other criteria will be ignored. Otherwise `pnLastName'
621 must be specified and it is matched as exact string. Values except `dbID' are
622 matched case insensitively.
624 Output is list of `dbResults' and `dbStatus' elements. `dbResults' is optional
625 and possibly empty list of `dbOwnerInfo' elements that have the same structure
626 as the input `dbOwnerInfo' element.
628 The output differs from FindDataBox output. Here are `aifoIsds', `adCode', and
629 `adDistrict' elements added. Some unused elements are missing.
631 This service can be used only by an user with PRIVIL_SEARCH_DB permisson to a
636 0003 Too many boxes match, result list is truncated but still valid
642 Return state of one box identified by dbID.
644 State of the box is stored in dbStatus element. Only state 1 means box is
645 capable of receiving messages.
648 5001 Box does not exist
649 1007 Box ID malformed
650 2011 Box ID malformed
656 Get comma-separate list of all boxes of given type.
658 Input is type of boxes of interrest (dblType element):
660 Value Description File name Permission
661 -------------------------------------------------------------------------------
662 ALL All active boxes actdsYYYYMMDD.csv OVM, OVM_EXEKUT,
663 OVM_NOTAR, OVM_REQ, or
665 authenticated by commercial
666 certificate or user with
667 PRIVIL_BILLING permission
668 UPG Effectively OVM active effovmYYYYMMDD.csv Anybody
670 POA Active boxes that puboaYYYYMMDD.csv Anybody
674 Non-normative: Following types are not documented anymore.
676 Value Description File name Permission
677 -------------------------------------------------------------------------------
678 OVM OVM gross type boxes ovmYYYYMMDD.csv PRIVIL_BILLING only
679 OPN Boxes that allow to opendsYYYYMMDD.csv PRIVIL_BILLING only
683 Output is Base64-encoded ZIP file containing a file with name from the table.
684 The Base64 string is stored in dblData element. The name of the file embeds
685 date of list creation (Y is year digit, M is month, D is day).
687 The file is created daily and its format a comma-separate list with following
690 Columns for ALL and UPG lists:
693 ----------------------
705 adNumberInMunicipality
711 Columns for POA lists:
718 The inner file is encoded in UTF-8. First line of the file is a header. Each
719 next line is a box. If a value is undefined, it will be empty. Values in
720 a line are separated by a comma (`,'). If a value contains comma or quotation
721 (`"'), the value will be enclosed into quotes (`"'). If value contains quotes,
722 they will be escaped by a quotes (e.g. `"lazy, ""fox""' means `lazy, "fox"').
725 1004 Operation not permitted
731 Return posibilities of sending commerical messages. Only if one of the
732 possibility is the payer is the recipient (PDZType is `O'), then calling this
733 service will cause marking messages as delivered.
735 Input is `PDZSender' element with a box ID as the only text node child.
737 Ouput is orderer list of rules for sending commercial messages wrapped in
738 dbPDZRecords element. The list can be empty what means no permission is
739 available. Each list item is a subtree:
742 + PDZType – rule type; see below for known values
743 + PDZRecip – only this recipient box ID is possible. Empty value means no
744 | restriction on the recipient.
745 + PDZPayer – the message is payed by this box ID owner
746 + PDZExpire – expiration time of this rule. Empty value means no
748 + PDZCnt – number of remaining commecrial messages that can be sent based
749 | on thid rule. Empty value means no limit.
750 + ODZIdent – identifier referring to message enabling sending pre-paid
751 answer. Must be added as dmRecipientRefNumber into sent message.
754 -------------------------------------------------------------------------------
755 D Externally subsidized (undocumented)
756 E Commercial message pre-paid by the sender
757 G PDZPayer owner pays for all commercial messages
758 K Commercial message paid by sender based on an agreement with the
760 O Answer on a commercial message is pre-paid by PDZPayer. ODZIdent
761 value must be added into an outgoing message to bind the message to
762 the payer and requesting message.
763 Z Limitedly subsidized (undocumented)
766 DataBoxCreditInfo (*)
769 Return current credit value and and history of credit changes for given box
772 Input is `dbID' element with box ID whose credit you want to obtain and
773 possibly empty elements `ciFromDate' and `ciTodate' carrying start and end
774 date (inclusive) for history records to obtain.
776 Output is `currentCredit' element delivering current credit value,
777 `notifEmail' element delivering e-mail address to send notifications
778 about changes in the commercial services to, and `ciRecords' tree with history
779 of changes that occurred in the given interval. All these elements are optional.
781 The `ciRecords' element contains possibly (if interval is not defined) empty
782 time-sorted list of `ciRecord' trees:
785 + ciEventTime – time of the change
786 + ciEventType – type of the change expressed as an integer
787 + ciCreditChange – value of the credit change
788 + ciCreditAfter – value of the credit after the change
791 ------------------------------------------
794 3 Sending commercial message
795 4 Setting long term storage
798 `ciRecord' contains other elements depending on `ciEventType':
800 Element ciEventType Meaning
801 ------------------------------------------------------------------
802 ciTransID 1, 2 String; not specified
803 ciRecipientID 3 Recipient's box ID of the sent message
804 ciPDZID 3 ID of the sent message
805 ciNewCapacity 4 Integer; new capacity of storage in messages
806 ciNewFrom 4 Date when the new capacity is effective
807 ciNewTo 4 Date when the new capacity expires
808 ciOldCapacity 4 Integer, optional; former capacity in messages
809 ciOldFrom 4 Date, optional
810 ciOldTo 4 Date, optional
811 ciDoneBy 4 String, optional; Name of user who initiated
814 All credit values are integers in hundredths of Czech Crowns.
816 Output carries standard `dbStatus' tree with status code and status message.
818 Error codes (codes are not normative):
819 1004 Insufficient priviledges for the box
820 2011 The box does not exist
821 1093 Date is too long (history is not available after 15 months)
822 1137 Interval is too long (limit is 3 months)
829 Return list of boxes matching a full text criteria.
831 The search is perfomed on an index cached each 3 hours.
833 The search phrase is splitted on word boundaries and the words are looked up
834 in the index. Only whole words matches. All search phrase words must be found
835 in the same box metadata (not necessarily in the same attribute and in the
836 same order). Diacritics supplementing, case folding, and lemmatization is
839 Non-OVM users still cannot see FO boxes which cannot receive commercial
840 messages and whose owners forbade listing on a public index.
842 Input is this list of these elements:
845 --------------------------------------------------------------------------------
846 searchText String Mandatory, non-empty
847 searchType Enumerated string Mandatory, can be empty,
849 searchScope Enumerated string Mandatory, can be empty,
851 page Non-negative integer Mandatory, can be empty,
852 defaults to 0, counts from 0
853 pageSize Non-negative integer Mandatory, can be empty,
854 defaults to 50, counts from 0,
855 server clamps the value to 100
856 highlighting Boolean Optional, can be empty,
859 Acceptable values for `searchType' element are:
862 --------------------------------------------------------------------------
863 GENERAL Search a phrase in names, addresses, organization identifiers,
865 ADDRESS Search a phrase in addresses only
866 ICO Search in organization identifiers only by equivalence
867 DBID Search in box IDs only by equivalence
869 If `searchType' is `ICO' or `DBID', `searchScope' restriction is ignored.
871 `searchScope' element restricts box types. See `Box types' section in `box'
872 file for the semantics, acceptable values are:
875 ------------------------------------------------------------------------
876 ALL Search over all box types
878 OVM_MAIN Search over main (without suboridanated, with secondary) OVM
892 Output is this list of these optional elements
895 ------------------------------------------------------------------------
896 totalCount Non-negative integer Number of matching boxes
897 currentCount Non-negative integer Number of boxes in this response
898 position Non-negative integer Ordinal number of first box in this
899 response, counts from 0
900 lastPage Boolean True if no more boxes match
901 dbResults List of elements
903 Last mandatory element is the standard response status of the service call
904 `dbStatus' element with status code and status message.
906 `dbResults' content is a possibly empty list of `dbResult' elements.
907 The list is sorted according to a search relevance. The `dbResult' element
914 + dbAddress – residence address as one string
915 + dbBiDate – can be empty, date of birth
916 + dbICO – can be empty, identifier of an organization
917 + dbEffectiveOVM – boolean, true for a box upgraded to an OVM role
918 + dbSendOptions – enumerated string, capability to deliver different
919 kinds of messages, it depends on querrier's box type and the found box
921 Acceptable values for `dbSendOptions' element are:
925 DZ Only noncommecrial messages can be sent
926 ALL Noncommercial and commercial messages can be sent
927 PDZ Only commercial messages can be sent
928 NONE No message can be sent
929 DISABLED The box is not active
931 If input `highlighting' is true, output `dbName' and `dbAddress' can contain
932 delimeters highlighting the phrase found in the strings. The start of the
933 phrase is marked by `|$*HL_START*$|' string, the end of the phrase is marked
934 by `|$*HL_END*$|' string.
937 1004 Not allowed to search
938 1152 `searchText' is empty
939 1153 Searched box ID is malformed
940 1154 Searched organization ID is malformed
942 1156 `pageSize' is too large
943 9002 Search engine internal error
946 GetDataBoxActivityStatus (*)
947 ========================
949 Retrive box state changes in given history time frame.
951 Input is list of these elements:
953 Element Type Mandatory Meaning
954 --------------------------------------------------------------------------
955 dbID String Mandatory Box ID
956 baFrom Time Optional Interval beginning, inclusive, second accuracy
957 defaults to box creation
958 baTo Time Optional Interval end, inclusive, second accuracy,
961 Non-normative: XML schema does not match textual documentation regarding
962 obligatority of the elements and their values. The table conforms to the
963 textual specification.
965 Output is list of optional `dbID', optional `Periods', and mandatory
966 `dbStatus' elements. `Periods' element is possibly empty list of these
970 + PeriodFrom – xs:dateTime
971 + PeriodTo – xs:dateTime
972 + DbState – non-negative integer
974 `DbState' is 1 for accessible state. Inaccessible state is signaled by 0 for
975 OVM users authenticated by system certificate, by 2--6 as defined in box
976 states for some internal priviledged users. Other users are not allowed to