Integration of reuses check functionality from the "Advacheck" system into your information system will allow you to use the most accurate and advanced technology within your own business logic. This means that the search for reuses can be embedded exactly where it is needed, called when you need it, check only the necessary texts and show the results as required by the logic of your information system. This site contains descriptions of methods and data structures for working with API, links to usage examples and additional information materials.

Data for test connection:

WSDL: https://api.advacheck.com:4959/apiCorp/testapi?wsdl
Login: testa.nosp@m.pi@a.nosp@m.dvache.nosp@m.ck..nosp@m.com
Password: testapi

Please pay attention that this account is publicly available for testing purposes, so the documents uploaded to this account are available to other users, and we are not responsible for their distribution.

Check is performed by own collection (id: testapi), english wikipedia from 2019 (id: wikipedia). It is recommended to send for check documents of at least 200-500 characters. In order for reuses to be detected, we recommend taking the texts of articles from Wikipedia created no later than 2019.

We reserve the right to clear this collection of documents at any time, so please note that the link to your document or its id will be valid for a limited period of time.

Integration requirements

The integration of Advacheck solution via API into your information system (IS) should meet the following requirements:

1. The IS must have a form for entering API connection data, which must be filled out by the IS administrator. A set of fields for this form:
   • url of company in "Advacheck" system. For example https://testapi.advacheck.com.
   • e-mail and password of API user, the technical user through whom the verification of documents will take place.
   • url of API access , for example https://api.advacheck.com:4959/apiCorp/testapi?wsdl.
2. In addition to digital verification results (percentage of originality, similarity, citation and text recycling) users of your IP should be able to:
   • receive all kinds of check reports of "Advacheck" system (brief report, full report without editing, full report with editing) according to user's roles in IS;
   • receive "Advacheck" system reports in PDF.
3. Next to the numeral results of the check, if it is possible to switch to an editable report, the "Update results" button should be implemented, initiating the receipt of updated results after editing the report.
4. For suspicious documents a suspicious symbol should be displayed in the IS interface.
5. Checking for reuses should be asynchronous for IS users. The users should be able to receive a result of checking the document for reuses (at the subsequent login to the personal account in the IS) even if they close the browser page or the document check form during check.
6. After uploading the document, the user in the IS should be able to see the current phase of working with the document: the document is loaded, the document is checked, an error occurred during check, the document was successfully checked.
7. Only documents of supported formats should be sent for check (FileType field). For other formats, the corresponding error should be displayed without sending a request for check.
8. The document should not be automatically downloaded or sent for check again if its upload or check failed with an error. For such documents, the corresponding status should be displayed and it should be possible to run the check manually.
9. Users of IS should have a possibility to add documents to index according to IS settings. Adding documents to the index should be available to the IS administrator or automatically performed within the document lifecycle.
10. An error may occur when uploading/checking a document (FailDetails field). For users, the correct notifications of such errors should be displayed.
11. Integration with the "Advacheck" system should pass the user ID in IS (ExternalUserId field). This id must be a string no longer than 40 characters. For example: integer; surname + student card number; GUID for a specific user; email; md5 hash of email, etc. This id is used to detect leaks of user credentials in the IS and will be reported to the IS administrator for investigation.
12. If you implement integration in your box solution, then you can certify this solution and get a DeveloperId. The received DeveloperID must be transmitted from all installations of your boxed solution.

Recommended procedure for integrating "Advacheck" reuses search solution into the information system:

1. Download and study examples in one of the programming languages. Examples in all languages are provided with detailed comments that reveal the point of what is happening.
2. Find on the Internet how to connect a web service for your programming language, if there is a WSDL. Connect here.
3. Integrate "Advacheck" system API calls into your information system and check it for compliance with the integration requirements.
4. Debug the interaction on the test account and inform the support service that you are ready for "real-life" integration. In the request, you need to specify the e-mail of the account on whose behalf API will work, it should not coincide with the root administrator account, and a recipient should read it, because notifications about technical work and changes in API will be sent to this address.
5. After receiving the "real-life" data, change the connection settings of your integration.

Additional materials:

• examples of using API (.net, php, python);
• API methods' description.

Please send questions and comments on API to the email address support@advacheck.com.

Planned changes

New functionality

• (In design) Multiple API users in the company. In order for the external IS to be able to connect to API, it will be provided with a token, and not credentials as it is now. The system administrator will be able to map the user to the cabinet to which the documents with the token will be uploaded by default. Thus, integrators will not have access to login credentials, and each IS will use its own token.
• (In design) Calculation of statistics of the document text via API.
• (In testing) Adding a document to the index will occur asynchronously. After executing the indexing status change command, the change will not occur instantly. For each document, you can request the current status of the change.
• (In testing) Information about the type of source (citation, similarity, text recycling) can be obtained via API.