JavaScript Integration

JavaScriptインテグレーション

JavaScript Integration

Intégration de JavaScript

JavaScript Integration

Examples using REST method:

RESTメソッドの使用例：

Examples using REST method:

Des exemples utilisant la méthode REST:

Examples using REST method:

• JavaScript example of /cvx/rest/api/v1/profile/full/json.
• JavaScript example of /cvx/rest/api/v1/profile/full/json.
• JavaScript example of /cvx/rest/api/v1/profile/full/json.
• Exemple en JavaScript de /cvx/rest/api/v1/profile/full/json.
• JavaScript example of /cvx/rest/api/v1/profile/full/json.
• JavaScript example of /cvx/rest/api/v1/profile/personal/json.
• JavaScript example of /cvx/rest/api/v1/profile/personal/json.
• JavaScript example of /cvx/rest/api/v1/profile/personal/json.
• Exemple en JavaScript de /cvx/rest/api/v1/profile/personal/json.
• JavaScript example of /cvx/rest/api/v1/profile/personal/json.

REST integration data formats

REST integration data formats

REST integration data formats

Formats de données d'intégration de REST

REST integration data formats

DaXtra REST architecture is extremely flexible in using different request data formats.

DaXtra REST architecture is extremely flexible in using different request data formats.

DaXtra REST architecture is extremely flexible in using different request data formats.

L'architecture de DaXtra REST est extrêmement flexible en utilisant de différents formats de données requête.

DaXtra REST architecture is extremely flexible in using different request data formats.

Request data format

Request data format

Request data format

Formats de données requête

Request data format

• multipart/form-data - JavaScript example
  
  This is the most efficient data transfer mechanism because it does not require file content to be Base64-encoded. To make it even more efficient you can either zip the file before POST-ing it or you can gzip a form part with file content; in the latter case you will need to specify "Content-Transfer-Encoding: gzip" in the header of that part (on the following line after Content-Type: application/octet-stream).

• multipart/form-data - JavaScript example
  
  This is the most efficient data transfer mechanism because it does not require file content to be Base64-encoded. To make it even more efficient you can either zip the file before POST-ing it or you can gzip a form part with file content; in the latter case you will need to specify "Content-Transfer-Encoding: gzip" in the header of that part (on the following line after Content-Type: application/octet-stream).

• multipart/form-data - JavaScript example
  
  This is the most efficient data transfer mechanism because it does not require file content to be Base64-encoded. To make it even more efficient you can either zip the file before POST-ing it or you can gzip a form part with file content; in the latter case you will need to specify "Content-Transfer-Encoding: gzip" in the header of that part (on the following line after Content-Type: application/octet-stream).

• multipart/form-data - exemple en JavaScript
  
  Ceci est la méthode de transfert de données la plus efficace parce qu'elle n'exige pas que le contenu soit encodé en Base64. Pour la rendre même plus efficace, ou vous pouvez zipper le ficher avant le POST ou vous pouvez gzip une partie du formulaire avec le contenu du ficher; dans ce dernier cas il faudra préciser "Content-Transfer-Encoding: gzip" dans l'en-tête de cette partie (sur la ligne qui suit Content-Type: application/octet-stream).

multipart/form-data - JavaScript example

this is the most efficient data transfer mechanism because it does not require file content to be Base64-encoded. To make it even more efficient you can either zip the file before POST-ing it or you can gzip a form part with file content; in the latter case you will need to specify "Content-Transfer-Encoding: gzip" in the header of that part (on the following line after Content-Type: application/octet-stream).

curl --request POST  --form "account=MY_ACCOUNT" --form "file=@myfile.doc"  http://cvx.daxtra.com/cvx/rest/api/v1/profile/full/json

POST / HTTP/1.1
Content-Type: multipart/form-data; boundary=------------------------------4921c809ff44

------------------------------4921c809ff44
Content-Disposition: form-data; name="account"

MYACCOUNT
------------------------------4921c809ff44
Content-Disposition: form-data; name="file"; filename="myfile.doc"
Content-Type: application/octet-stream

ÐÏ^Qࡱ^Zá^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@>^@^C^@þÿ   
...................................... 
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
------------------------------4921c809ff44--

• application/x-www-form-urlencoded:

curl --request POST --data 'account=MYACCOUNT&file=This%20is%20text%20to%20process' http:/cvx.daxtra.com/cvx/rest/api/v1/profile/full/json

POST / HTTP/1.1
Content-Type: application/x-www-form-urlencoded

account=MYACCOUNT&file=This%20is%20text%20to20%process

curl --request POST --data 'account=MYACCOUNT&file=This%20is%20text%20to%20process' http:/cvx.daxtra.com/cvx/rest/api/v1/profile/full/json

POST / HTTP/1.1
Content-Type: application/x-www-form-urlencoded

account=MYACCOUNT&file=This%20is%20text%20to20%process

curl --request POST --data 'account=MYACCOUNT&file=This%20is%20text%20to%20process' http:/cvx.daxtra.com/cvx/rest/api/v1/profile/full/json

POST / HTTP/1.1
Content-Type: application/x-www-form-urlencoded

account=MYACCOUNT&file=This%20is%20text%20to20%process

curl --request POST --data 'account=MYACCOUNT&file=This%20is%20text%20to%20process' http:/cvx.daxtra.com/cvx/rest/api/v1/profile/full/json

POST / HTTP/1.1
Content-Type: application/x-www-form-urlencoded

account=MYACCOUNT&file=This%20is%20text%20to20%process

curl --request POST --data 'account=MYACCOUNT&file=This%20is%20text%20to%20process' http:/cvx.daxtra.com/cvx/rest/api/v1/profile/full/json

POST / HTTP/1.1
Content-Type: application/x-www-form-urlencoded

account=MYACCOUNT&file=This%20is%20text%20to20%process

• application/json -- JSON string in POST body - JavaScript example:

• application/json -- JSON string in POST body - JavaScript example:

• pplication/json -- JSON string in POST body - JavaScript example:

• application/json -- chaîne JSON dans le corps de POST - exemple de JavaScript:

• application/json -- JSON string in POST body - JavaScript example:

curl --request POST -H "Content-Type: application/json" --data '{"file":"This is a sample file", "account":"MY_ACCOUNT"}'  http:/cvx.daxtra.com/cvx/rest/api/v1/profile/full/json

POST / HTTP/1.1
Content-Type: application/json

{"file":"This is a sample file", "account":"MY_ACCOUNT"}

• text/xml -- XML string in POST body - VB6 example:

• text/xml -- XML string in POST body - VB6 example:

• text/xml -- XML string in POST body - VB6 example:

• text/xml -- chaîne XML dans le corps de POST - exemple de VB6:

• text/xml -- XML string in POST body - VB6 example:

curl --request POST -H "Content-Type: text/xml" --data '<Request><file>This is a sample file</file><account>MY_ACCOUNT</account></Request>' http:/cvx.daxtra.com/cvx/rest/api/v1/profile/full/json

POST / HTTP/1.1
Content-Type: text/xml

<Request><file>This is a sample file</file><account>MY_ACCOUNT</account></Request>

Integration through HTTP POST request

Integration through HTTP POST request

Integration through HTTP POST request

Intégrations à travers une demande à HTTP POST

Integration through HTTP POST request

/cvx/http is a call which facilitates interaction with DaXtra Parser by means of the HTTP POST protocol. It supports both multipart/form-data and application/x-www-form-urlencoded styles. The calling arguments are as follows:

/cvx/http is a call which facilitates interaction with DaXtra Parser by means of the HTTP POST protocol. It supports both multipart/form-data and application/x-www-form-urlencoded styles. The calling arguments are as follows:

/cvx/http is a call which facilitates interaction with DaXtra Parser by means of HTTP POST protocol. It supports both multipart/form-data and application/x-www-form-urlencoded styles. The calling arguments are as follows:

/cvx/http est un appel qui facilite l'interaction avec DaXtra Parser au moyen du protocole HTTP POST. Il soutien les styles multipart/form-data et application/x-www-form-urlencoded. Les arguments sont:

/cvx/http is a call which facilitates interaction with DaXtra Parser by means of HTTP POST protocol. It supports both multipart/form-data and application/x-www-form-urlencoded styles. The calling arguments are as follows:

• action - API action (as specified below) API action (as specified below) API action (as specified below) action d'API (comme précisée ci-dessous) API action (as specified below)
• account - account name or Secure Token which was assigned to you by DaXtra account name or Secure Token which was assigned to you by DaXtra account name or Secure Token which was assigned to you by DaXtra nom de compte ou Secure Token que DaXtra vous a donné Kontoname or Secure Token which was assigned to you by DaXtra
• file - file which needs to be processed. It can be a "file upload" type in multipart/form-data POST style or can be file content (Base64-encoded or not) in application/x-www-form-urlencoded POST style. Please note that in the latter case it needs to be URL-encoded to be transferred properly. - file which needs to be processed. It can be a "file upload" type in multipart/form-data POST style or can be file content (Base64-encoded or not) in application/x-www-form-urlencoded POST style. Please note that in the latter case it needs to be URL-encoded to be transferred properly. - file which needs to be processed. It can be "file upload" type in multipart/form-data POST style or can be file content (Base64-encoded or not) in application/x-www-form-urlencoded POST style. Please note that in the latter case it needs to be URL-encoded to be transferred properly. - fichier à traiter. Cela peut être du type «file upload» style multipart/form-data POST, ou peut être contenu de fichier (soit encodé en Base64 soit non), en style application/x-www-form-urlencoded POST. Veuillez noter que dans ce dernier cas il faut être encodé URL pour le transférer correctement. - file which needs to be processed. It can be "file upload" type in multipart/form-data POST style or can be file content (Base64-encoded or not) in application/x-www-form-urlencoded POST style. Please not that in the latter case it needs to be URL-encoded to be transferred properly.

Here is an example of a call (application/x-www-form-urlencoded):

Here is an example of a call (application/x-www-form-urlencoded):

Here is an example of a call (application/x-www-form-urlencoded):

Voici un exemple d'un appel (application/x-www-form-urlencoded):

Here is an example of a call (application/x-www-form-urlencoded):

curl --data "action=ProcessCV_json&account=MYACCOUNT&file=This%20is%20text%20to%20process" http://cvx.daxtra.com/cvx/http

curl --data "action=ProcessCV_json" -data "account=MYACCOUNT" --data "file=This%20is%20text%20to%20process" http://cvx.daxtra.com/cvx/http

POST / HTTP/1.1
action=ProcessCV&account=MYACCOUNT&file=This%20is%20text%20to20%process

Here is an example of a call (multipart/form-data):

Here is an example of a call (multipart/form-data):

Here is an example of a call (multipart/form-data):

Voici un exemple d'un appel (multipart/form-data):

Here is an example of a call (multipart/form-data):

curl -v --form "action=ProcessCV_json"  --form "account=MYACCOUNT" --form "file=\@myfile.doc" http://cvx.daxtra.com/cvx/http

POST / HTTP/1.1
Content-Type: multipart/form-data; boundary=------------------------------4921c809ff44
Content-Length: 8834

------------------------------4921c809ff44
Content-Disposition: form-data; name="action"

ProcessCV_json
------------------------------4921c809ff44
Content-Disposition: form-data; name="account"

MYACCOUNT
------------------------------4921c809ff44
Content-Disposition: form-data; name="file"; filename="myfile.doc"
Content-Type: application/octet-stream

ÐÏ^Qࡱ^Zá^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@>^@^C^@þÿ   
...................................... 
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
------------------------------4921c809ff44--

API calls

API calls

API calls

Appels d'API

API-Aufrufe

• ProcessCV - sends a resume for processing to a DaXtra server and receives back a string with structured XML representation wrapped inside <hrxml> element
• ProcessCV - returns a string with structured XML representation wrapped inside <hrxml> element
• ProcessCV_simple - returns a string with structured XML representation
• ProcessCV_json - returns a string with structured JSON representation
• ProcessCVphase1 and ProcessCVphase2 -- in the first phase ProcessCVphase1 extracts only personal and contact data which is in general 50% faster than extraction of the full profile. Together with the HR-XML profile it returns a phase2_token which can be used by calling ProcessCVphase2 to fetch the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.
  • ProcessCVphase1 - returns a string with structured XML representation wrapped inside <hrxml> element
  • ProcessCVphase1_simple - returns a string with structured XML representation
  • ProcessCVphase1_json - returns a string with structured JSON representation

Examples:

Examples:

Examples:

Exemples:

Beispiele:

• JavaScript example of ProcessCV_json.
• JavaScript example of ProcessCVphase1_json/ProcessCVphase1_json.
• VB6 example of ProcessCV_simple.

DaXtra Server

DaXtra Server

DaXtra Server

DaXtra Server

DaXtra Server

URL or IP of a computer provided to you by DaXtra on which CVXtractor Services are installed

URL or IP of a computer provided to you by DaXtra on which CVXtractor Services are installed

URL or IP of a computer provided to you by DaXtra on which CVXtractor Services are installed

URL ou IP d'un ordinateur que DaXtra vous a donné, sur lequel sont installés les services de CVXtractor

URL or IP of a computer provided to you by DaXtra on which CVXtractor Services are installed

DaXtra Account

DaXtra Account

DaXtra Account

Compte de DaXtra

DaXtra Account

A unique name provided to you by DaXtra which you must use to get access to CVXtractor Services.

A unique name provided to you by DaXtra which you must use to get access to CVXtractor Services.

A unique name provided to you by DaXtra which you must use to get access to CVXtractor Services.

Un nom unique que DaXtra vous a donné, et que vous devrez utiliser pour accéder au services de CVXtractor.

A unique name provided to you by DaXtra which you must use to get access to CVXtractor Services.

Output XML

Output XML

Output XML

Sortie XML

Ausgabe-XML

Identified (extracted) information from a processed resume is delivered back in a string containing an XML representation. Two main forms DaxML and HR-XML v2.4 are supported by default (for more information see "Output Schemas"). There are also several other XML representations (HRML).

Identified (extracted) information from a processed resume is delivered back in a string containing an XML representation. Two main forms DaxML and HR-XML v2.4 are supported by default (for more information see "Output Schemas"). There are also several other XML representations (HRML).

Identified (extracted) information from a processed resume is delivered back in a string containing an XML representation. Two main forms DaxML and HR-XML v2.4 are supported by default (for more information see "Output Schemas"). There are also several other XML representations (HRML).

L'information qui a été identifiée (extraite) d'un CV qui a été traité est renvoyé dans une chaîne qui contient une représentation XML. Deux des formats principaux, DaxML et HR-XML v2.4, sont supportés par défaut (pour en savoir plus, voir «Schémas de Sorties»). Il y a aussi plusieurs autres représentations (HRML).

Identified (extracted) information from a processed resume is delivered back in a string containing an XML representation. Two main forms DaxML and HR-XML v2.4 are supported by default (for more information see "Output Schemas"). Several other XML representation (HRML).

ProcessCV SOAP API call

ProcessCV SOAP API call

ProcessCV SOAP API call

Appel d'API SOAP ProcessCV

ProcessCV SOAP API call

Sends a resume to a DaXtra server and receives back a string with an extracted profile in XML representation:

Sends a resume to a DaXtra server and receives back a string with an extracted profile in XML representation:

Sends a resume to a DaXtra server and receives back a string with an extracted profile in XML representation:

Envoie un CV à un serveur de DaXtra et reçoit une chaîne avec un profil extrait dans une représentation XML:

Sends a resume to a DaXtra server and receives back a string with an extracted profile in XML representation:

Input: 
    ProcessCV wrapper containing
      document_url - Base64-encoded string containing the URL of a file or the full contents of a file
      account - string with a unique name supplied to you by DaXtra

Input: 
    ProcessCV wrapper containing
      document_url - Base64-encoded string containing the URL of a file or the full contents of a file
      account - string with a unique name supplied to you by DaXtra

Input: 
    ProcessCV wrapper containing
      document_url - Base64-encoded string containing the URL of a file or the full contents of a file
      account - string with a unique name supplied to you by DaXtra

Entrée:
    Wrapper de ProcessCV qui contient
      document_url - chaîne encodée en Base64, qui contient ou l'URL d'un fichier ou le contenu complet d'un fichier
      account - chaîne avec nom unique, que DaXtra vous a donné

Eingabe:
    ProcessCV wrapper containing
      document_url - Base64-encoded string containing the URL of a file or the full contents of a file
      account - string with a unique name supplied to you by DaXtra

Output:
    ProcessCVResponse wrapper containing
      hrxml - string (UTF-8 encoded) with XML representation

Output:
    ProcessCVResponse wrapper containing
      hrxml - string (UTF-8 encoded) with XML representation

Output:
    ProcessCVResponse wrapper containing
      hrxml - string (UTF-8 encoded) with XML representation

Sortie:
    Wrapper de ProcessCVResponse qui contient
       hrxml - chaîne (encodée en UTF-8) avec représentation en XML

Ausgabe:
    ProcessCVResponse wrapper containing
      hrxml - string (UTF-8 encoded) with XML representation

Here is an example of a ProcessCV request:

Here is an example of a ProcessCV request:

Here is an example of a ProcessCV request:

Voici un exemple d'une demande à ProcessCV:

Here is an example of a ProcessCV request:

<soapenv:Envelope>
<soapenv:Body>
 <ProcessCV xmlns="CVXtractorService">
   <document_url>PGRpdiB4bWxuczp3PSJodHRwOi8........
      .............
   </document_url>
   < account>YOUR_ACCOUNT</account>
 </ProcessCV>
</soapenv:Body>
</soapenv:Envelope>

Here is an example of a ProcessCV response:

Here is an example of a ProcessCV response:

Here is an example of a ProcessCV response:

Voici un exemple d'une réponse de ProcessCV:

Here is an example of a ProcessCV response:

<soapenv:Envelope>
 <soapenv:Body>
  <ProcessCVResponse xmlns="CVXtractorService">
    <hrxml>XML profile</hrxml>
  </ProcessCVResponse>
 </soapenv:Body>
</soapenv:Envelope>

Pseudocode example:

Pseudocode example:

Pseudocode example:

Exemple en pseudocode:

Pseudocode example:

  daxtra_soap_client = CreateSoapClient("http://www.daxtra.com/cvx/CVXtractorService.wsdl");
  process_cv_response = daxtra_soap_client->ProcessCV(
                                    'document_url' =>  fileContent_base64, 
                                    'account' => service_account);
  hrxml_string = process_cv_response->getXMLContent("hrxml"); 

Please note that document transfer through a SOAP attachment can be implemented in a ProcessCVattach call. This is a more efficient way to transfer data to the DaXtra Server.

Please note that document transfer through a SOAP attachment can be implemented in a ProcessCVattach call. This is a more efficient way to transfer data to the DaXtra Server.

Please note that document transfer through a SOAP attachment can be implemented in a ProcessCVattach call. This is a more efficient way to transfer data to the DaXtra Server.

Veuillez noter que le transfert des fichiers à travers une pièce jointe SOAP est inclus dans un appel de ProcessCVattach; c'est une façon plus efficace pour transférer des données au serveur DaXtra.

Please note that document transfer through a SOAP attachment can be implemented in a ProcessCVattach call. This is a more efficient way to transfer data to the DaXtra Server.

Sample integrations:

Sample integrations:

Sample integrations:

Exemples d'intégrations:

Sample integrations:

ProcessJobOrder SOAP API call

ProcessJobOrder SOAP API call

ProcessJobOrder SOAP API call

Appel d'API SOAP ProcessJobOrder

ProcessJobOrder SOAP API call

Sends a job order to a DaXtra server and receives back a string with an extracted profile in XML representation.

Sends a job order to a DaXtra server and receives back a string with an extracted profile in XML representation.

Sends a job order to a DaXtra server and receives back a string with extracted profile in XML representation.

Envoie un ordre de travail à un serveur DaXtra, et retourne un profil extrait en format XML.

Sends a job order to a DaXtra server and receivds back a string with an extracted profile in XML representation.

Input:
    ProcessJobOrder wrapper containing
      document_url - Base64-encoded string containing URL of a file or full content of a file
      account - string with a unique name supplied to you by DaXtra

Input:
    ProcessJobOrder wrapper containing
      document_url - Base64-encoded string containing URL of a file or full content of a file
      account - string with a unique name supplied to you by DaXtra

Input:
    ProcessJobOrder wrapper containing
      document_url - Base64-encoded string containing URL of a file or full content of a file
      account - string with a unique name supplied to you by DaXtra

Entrée:
    Wrapper de ProcessJobOrder qui contient
      document_url - chaîne encodée en Base64, qui contient ou l'URL d'un fichier ou le contenu complet d'un fichier
      account - chaîne avec nom unique, que DaXtra vous a donné

Eingabe:
    ProcessJobOrder wrapper containing
      document_url - Base64-encoded string containing URL of a file or full content of a file
      account - string with a unique name supplied to you by DaXtra

Output:
     ProcessJobOrderResponse wrapper containing
       hrxml - string (UTF-8 encoded) with XML representation

Output:
     ProcessJobOrderResponse wrapper containing
       hrxml - string (UTF-8 encoded) with XML representation

Output:
     ProcessJobOrderResponse wrapper containing
       hrxml - string (UTF-8 encoded) with XML representation

Sortie:
     Wrapper de ProcessJobOrderResponse wrapper qui contient
       hrxml - chaîne (encodée en UTF-8) avec représentation en XML

Ausgabe:
     ProcessJobOrderResponse wrapper containing
       hrxml - string (UTF-8 encoded) with XML representation

Here is an example of a ProcessJobOrder request:

Here is an example of a ProcessJobOrder request:

Here is an example of a ProcessJobOrder request:

Voici un exemple d'une demande à ProcessJobOrder:

Here is an example of a ProcessJobOrder request:

<soapenv:Envelope>
<soapenv:Body>
 <ProcessJobOrder xmlns="CVXtractorService">
   <document_url>PGRpdiB4bWxuczp3PSJodHRwOi8........
      .............
   </document_url>
   < account>YOUR_ACCOUNT</account>
 </ProcessJobOrder>
</soapenv:Body>
</soapenv:Envelope>

Here is an example of a ProcessCV response:

Here is an example of a ProcessCV response:

Here is an example of a ProcessCV response:

Voici un exemple d'une réponse de ProcessCV:

Here is an example of a ProcessCV response:

<soapenv:Envelope>
 <soapenv:Body>
  <ProcessJobOrderResponse xmlns="CVXtractorService">
    <hrxml>XML profile</hrxml>
  </ProcessJobOrderResponse>
 </soapenv:Body>
</soapenv:Envelope>

Example pseudocode:

Example pseudocode:

Example pseudocode:

Exemple en pseudocode:

Example pseudocode:

  daxtra_soap_client = CreateSoapClient("http://www.daxtra.com/cvx/CVXtractorService.wsdl");
  process_joborder_response = daxtra_soap_client->ProcessJobOrder(
                                    'document_url' =>  fileContent_base64, 
                                    'account' => service_account);
  xml_string = process_joborder_response->getXMLContent("hrxml"); 

Please note that document transfer through SOAP attachments is implemented in a ProcessJobOrderattach call; it is a more efficient way to transfer data to the DaXtra Server.

Please note that document transfer through SOAP attachments is implemented in a ProcessJobOrderattach call; it is a more efficient way to transfer data to the DaXtra Server.

Please note that document transfer through SOAP attachments is implemented in a ProcessJobOrderattach call; it is a more efficient way to transfer data to the DaXtra Server.

Veuillez noter que le transfert des fichiers à travers des pièces jointes SOAP est inclus dans un appel de ProcessJobOrderattach; c'est une façon plus efficace de transférer des données au serveur DaXtra.

Please note that document transfer through SOAP attachments is implemented in ProcessJobOrderattach call; it is a more efficient way to transfer data to the DaXtra Server.

ProcessCVattach SOAP API call

ProcessCVattach SOAP API call

ProcessCVattach SOAP API call

Appel d'API SOAP ProcessCVattach

ProcessCVattach SOAP API call

Sends a resume to a DaXtra server and receives back a string with XML representation.

Sends a resume to a DaXtra server and receives back a string with XML representation.

Sends a resume to a DaXtra server and receives back a string with XML representation.

Envoie un CV à un serveur DaXtra, et reçoit une chaîne avec représentation en XML.

Sends a resume to a DaXtra server and receives back a string with XML representation.

Input:
    ProcessCVattach wrapper containing
      account - string with a unique name supplied to you by DaXtra
      CVattachment - reference to the MIME part containing document content

Input:
    ProcessCVattach wrapper containing
      account - string with a unique name supplied to you by DaXtra
      CVattachment - reference to the MIME part containing document content

Input:
    ProcessCVattach wrapper containing
      account - string with a unique name supplied to you by DaXtra
      CVattachment - reference to the MIME part containing document content

Entrée:
    Wrapper de ProcessCVattach qui contient
      account - chaîne avec nom unique, que DaXtra vous a donné
      CVattachment - référence à la partie MIME qui contient le contenu du fichier

Eingabe:
    ProcessCVattach wrapper containing
      account - string with a unique name supplied to you by DaXtra
      CVattachment - reference to the MIME part containing document content

Output:
    ProcessCVattachResponse wrapper containing
      hrxml - string (UTF-8 encoded) with XML representation

Output:
    ProcessCVattachResponse wrapper containing
      hrxml - string (UTF-8 encoded) with XML representation

Output:
    ProcessCVattachResponse wrapper containing
      hrxml - string (UTF-8 encoded) with XML representation

Sortie:
    Wrapper de ProcessCVattachResponse qui contient
      hrxml - chaîne (encodée en UTF-8) avec représentation en XML

Ausgabe:
    ProcessCVattachResponse wrapper containing
      hrxml - string (UTF-8 encoded) with XML representation

Please note that although CVattachment is declared in WSDL as base64Binary it takes binary content of the file without Base64 encoding.

Please note that although CVattachment is declared in WSDL as base64Binary it takes binary content of the file without Base64 encoding.

Please note that although CVattachment is declared in WSDL as base64Binary it takes binary content of the file without Base64 encoding.

Veuillez noter que bien que CVattachment est déclaré en WSDL comme base64Binary, il prend le contenu binaire sans l'encodage Base64.

Please note that although CVattachment is declared in wsdl as base64Binary it take binary content of the file without Base64 encoding.

More information on SOAP with attachments can be found at http://www.w3.org/TR/SOAP-attachments.

More information on SOAP with attachments can be found at http://www.w3.org/TR/SOAP-attachments.

More information on SOAP with attachments can be found at http://www.w3.org/TR/SOAP-attachments.

Vous trouverez davantage d'informations sur SOAP avec pièces jointes à http://www.w3.org/TR/SOAP-attachments.

More information on SOAP with attachments can be found at http://www.w3.org/TR/SOAP-attachments.

Here is an example of a ProcessCVattach request. A SOAP envelope is passed in the first MIME part and includes a reference to the second MIME part which contains the actual document content.

Here is an example of a ProcessCVattach request. A SOAP envelope is passed in the first MIME part and includes a reference to the second MIME part which contains the actual document content.

Here is an example of a ProcessCVattach request. A SOAP envelope is passed in the first MIME part and includes a reference to the second MIME part which contains the actual document content.

Voici un exemple d'une demande ProcessCVattach. Une enveloppe SOAP est transmise dans l'élément MIME et inclut une référence au deuxième élément MIME qui contient le fichier réel.

Here is an example of a ProcessCVattach request. A SOAP envelope is passed in the first MIME part and includes a reference to the second MIME part which contains the actual document content.

Content-Type: multipart/related; 
    type="application/xop+xml"; 
    boundary="uuid:82505732-3eab-43a9-882a-f48887b8830b";

--uuid:82505732-3eab-43a9-882a-f48887b8830b
Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
Content-Transfer-Encoding: binary
Content-ID: <root.message@cxf.apache.org>

<soapenv:Envelope>
  <soapenv:Body>
    <ProcessCVattach xmlns="CVXtractorService">
       <account>YOUR_ACCOUNT</account>
    </ProcessCVattach>
    <CVattachment xmlns="CVXtractorService">
      <xop:Include 
        xmlns:xop="http://www.w3.org/2004/08/xop/include"
        href="cid:abdfth-abdfth"
      />
    </CVattachment>
 </soapenv:Body>
</soapenv:Envelope>
--uuid:82505732-3eab-43a9-882a-f48887b8830b
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <abdfth-abdfth

PK^C^D^T^@^F^@^H^@^@^@!^@?gHw³^A..................
............................

Here is an example of a ProcessCVattach response:

Here is an example of a ProcessCVattach response:

Here is an example of a ProcessCVattach response:

Voici un exemple d'une réponse de ProcessCVattach:

Here is an example of a ProcessCVattach response:

<soapenv:Envelope>
 <soapenv:Body>
  <ProcessCVattachResponse xmlns="CVXtractorService">
    <hrxml>XML profile</hrxml>
  </ProcessCVattachResponse>
 </soapenv:Body>
</soapenv:Envelope>

ProcessCVphase1 and ProcessCVphase2 SOAP API calls

ProcessCVphase1 and ProcessCVphase2 SOAP API calls

ProcessCVphase1 and ProcessCVphase2 SOAP API calls

Appels d'API SOAP ProcessCVphase1 et ProcessCVphase2

ProcessCVphase1 and ProcessCVphase2 SOAP API calls

These two calls support extraction of information in two stages to speed up information delivery to the user.

These two calls support extraction of information in two stages to speed up information delivery to the user.

These two calls support extraction of information in two stages to speed up information delivery to the user.

Ces deux appels soutiennent l'extraction d'informations en deux étapes, pour accélérer la livraison d'informations à l'utilisateur.

These two calls support extraction of information in two stages to speed up information delivery to the user.

Unlike "ProcessCV", the "ProcessCVphase1" call extracts only personal and contact data (which is about 50% faster) and at the same time extraction of the full profile is initiated. "ProcessCVphase1" returns an HR-XML profile (with personal details only) and also a token which then can be used by a "ProcessCVphase2" call to pick up the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

Unlike "ProcessCV", the "ProcessCVphase1" call extracts only personal and contact data (which is about 50% faster) and at the same time extraction of the full profile is initiated. "ProcessCVphase1" returns an HR-XML profile (with personal details only) and also a token which then can be used by a "ProcessCVphase2" call to pick up the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

Unlike "ProcessCV", the "ProcessCVphase1" call extracts only personal and contact data (which is about 50% faster) and at the same time extraction of the full profile is initiated. "ProcessCVphase1" returns an HR-XML profile (with personal details only) and also a token which then can be used by a "ProcessCVphase2" call to pick up the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

Contrairement à «ProcessCV», l'appel «ProcessCVphase1» n'extrait que les données personnelles et les coordonnées (ce qui est plus rapide de 50%), tandis qu'en même temps l'extraction du profil complet est initiée. «ProcessCVphase1» renvoie un profil HR-XML (avec des données personnelles seulement) et aussi un token qui peut être utilisé par un appel de «ProcessCVphase2» pour récupérer le profil complet. L'appel ProcessCVphase2 doit être entré aussi vite que possible après l'appel ProcessCVphase1.

Unlike "ProcessCV", the "ProcessCVphase1" call extracts only personal and contact data (which is about 50% faster) and at the same time extraction of the full profile is initiated. "ProcessCVphase1" returns an HR-XML profile (with personal details only) and also a token which then can be used by a "ProcessCVphase2" call to pick up the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

<soapenv:Envelope>
 <soapenv:Body>
  <ProcessCVphase1Response xmlns="CVXtractorService">
    <hrxml>XML profile</hrxml>
    <phase2_token>PGRpdiB4bW</phase2_token>
  </ProcessCVphase1Response>
 </soapenv:Body>
</soapenv:Envelope>

At this stage results of personal data extraction can be served to the user, and immediately a "ProcessCVphase2" SOAP call can be issued to fetch the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

At this stage results of personal data extraction can be served to the user, and immediately a "ProcessCVphase2" SOAP call can be issued to fetch the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

At this stage results of personal data extraction can be served to the user, and immediately a "ProcessCVphase2" SOAP call can be issued to fetch the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

À ce stade les résultats de l'extraction des données personnelles peuvent être livrés à l'utilisateur, et immédiatement un appel SOAP «ProcessCVphase2» peut être entré pour extraire le profil complet. L'appel ProcessCVphase2 doit être entré aussi vite que possible après l'appel ProcessCVphase1.

At this stage results of personal data extraction can be served to the user, and immediately a "ProcessCVphase2" soap call can be issued to fetch the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

"ProcessCVphase2" takes two arguments - phase2_token returned by the ProcessCVphase1 call, and account string. Here is an example of a ProcessCVphase2 request:

"ProcessCVphase2" takes two arguments - phase2_token returned by the ProcessCVphase1 call, and account string. Here is an example of a ProcessCVphase2 request:

"ProcessCVphase2" takes two arguments - phase2_token returned by the ProcessCVphase1 call, and account string. Here is an example of a ProcessCVphase2 request:

«ProcessCVphase2» prend deux arguments - phase2_token retourné par l'appel ProcessCVphase1, et chaîne de compte. Voici un exemple d'une demande ProcessCVphase2:

"ProcessCVphase2" takes two arguments - phase2_token returned by ProcessCVphase1 call, and account string. Here is an example of a ProcessCVphase2 request:

<soapenv:Envelope>
 <soapenv:Body>
  <ProcessCVphase2 xmlns="CVXtractorService">
    <phase2_token>PGRpdiB4bW</phase2_token>
    <account>YOUR_ACCOUNT</account>
  </ProcessCVphase2>
 </soapenv:Body>
</soapenv:Envelope>

This SOAP request returns an HR-XML profile in exactly the same form as a ProcessCV call.

This SOAP request returns an HR-XML profile in exactly the same form as a ProcessCV call.

This SOAP request returns an HR-XML profile in exactly the same form as a ProcessCV call.

Cette requête SOAP retourne un profil HR-XML dans la même forme qu'un appel ProcessCV.

This SOAP request returns an HR-XML profile exactly in the same form as ProcessCV call.

You can see sample SOAP calls in the PHP integration section.

You can see sample SOAP calls in the PHP integration section.

You can see sample SOAP calls in the PHP integration section.

Vous pouvez voir des exemples des appels SOAP dans la section d'intégration PHP.

You can see sample SOAP calls in the PHP integration section.

Example pseudocode:

Example pseudocode:

Example pseudocode:

Exemple en pseudocode:

Example pseudocode:

  daxtra_soap_client = CreateSoapClient("http://www.daxtra.com/cvx/CVXtractorService.wsdl");

  //-- first retrieve only personal data:  //-- first retrieve only personal data:  //-- first retrieve only personal data:  //-- d'abord ne récupérer que les données personnelles:  //-- first retrieve only personal data:
  process_cv_phase1_response = daxtra_soap_client->ProcessCVphase1(
                                    'document_url' =>  fileContents_base64, 
                                    'account' => service_account);
  hrxml_pers_only_string = process_cv_phase1_response->getXMLContent("hrxml"); 
  processing_token = process_cv_phase1_response->getXMLContent("phase2_token");

  //-- now retrieve full profile:  //-- now retrieve full profile:  //-- now retrieve full profile:  //-- maintenant récupérer le profil complet:  //-- now retrieve full profile/
  process_cv_phase2_response = daxtra_soap_client->ProcessCVphase1(
                                    'phase2_token' =>  processing_token, 
                                    'account' => service_account);
  hrxml_string = process_cv_phase2_response->getXMLContent("hrxml"); 

Sample integrations:

Sample integrations:

Sample integrations:

Exemples d'intégrations:

Sample integrations:

ProcessBatch SOAP API call

ProcessBatch SOAP API call

ProcessBatch SOAP API call

Appel d'API SOAP ProcessBatch

ProcessBatch SOAP API call

Sends a file (usually ZIP, RAR or tar) with multiple documents to a DaXtra server and gradually returns results of processing.

Sends a file (usually ZIP, RAR or tar) with multiple documents to a DaXtra server and gradually returns back results of processing.

Sends a file (usually ZIP, RAR or tar) with multiple documents to a DaXtra server and gradually returns results of processing.

Envoie un fichier (normalement ZIP, RAR ou tar) avec plusieurs documents à un serveur de DaXtra server, et retourne progressivement les résultats du traitement.

Sends a file (usually ZIP, RAR or tar) with multiple documents to a daxtra server and gradually returns results of processing.

Input: 
    ProcessBatch wrapper containing
      document_url - Base64-encoded string containing the URL of a file or full content of a file;
                     usually this will be a ZIP file with multiple files which require processing
      account - string with a unique name supplied to you by DaXtra

Input: 
    ProcessBatch wrapper containing
      document_url - Base64-encoded string containing the URL of a file or full content of a file;
                     usually this will be a ZIP file with multiple files which require processing
      account - string with a unique name supplied to you by DaXtra

Input: 
    ProcessBatch wrapper containing
      document_url - Base64-encoded string containing the URL of a file or full content of a file;
                     usually this will be a ZIP file with multiple files which require processing
      account - string with a unique name supplied to you by DaXtra

Entrée: 
    ProcessBatch wrapper qui contient
      document_url - chaîne encodée en Base64, qui contient ou l'URL d'un fichier ou le contenu complet
                     d'un fichier; normalement ce sera un fichier ZIP avec plusieurs documents à traiter
      account - chaîne avec nom unique, que DaXtra vous a donné

Eingabe:
    ProcessBatch wrapper containing
      document_url - Base64-encoded string containing the URL of a file or full content of a file;
                     usually this will be a ZIP file with multiple files which require processing
      account - string with a unique name supplied to you by DaXtra

Output:
    ProcessBatchResponse wrapper containing
      Results - Base64-encoded zipped content of the processing results currently available 
      process_token - unique token for identification of the current batch processing

Output:
    ProcessBatchResponse wrapper containing
      Results - Base64-encoded zipped content of the processing results currently available 
      process_token - unique token for identification of the current batch processing

Output:
    ProcessBatchResponse wrapper containing
      Results - Base64-encoded zipped content of the processing results currently available 
      process_token - unique token for identification of the current batch processing

Sortie:
    ProcessBatchResponse wrapper qui contient
      Results - contenu zippé encodé en Base64, qui contient les résultats disponibles en ce moment
      process_token - token unique qui identifie le traitement par lots actuel

Ausgabe:
    ProcessBatchResponse wrapper containing
      Results - Base64-encoded zipped content of the processing results currently available 
      process_token - unique token for identification of the current batch processing

Here is an example of a ProcessBatch request:

Here is an example of a ProcessBatch request:

Here is an example of a ProcessBatch request:

Voici un exemple d'une demande à ProcessBatch:

Here is an example of a ProcessBatch request:

<soapenv:Envelope>
<soapenv:Body>
 <ProcessBatch xmlns="CVXtractorService">
   <document_url>PGRpdiB4bWxuczp3PSJodHRwOi8........
      .............
   </document_url>
   < account>YOUR_ACCOUNT</account>
 </ProcessBatch>
</soapenv:Body>
</soapenv:Envelope>

Here is an example of a ProcessBatch response:

Here is an example of a ProcessBatch response:

Here is an example of a ProcessBatch response:

Voici un exemple d'une réponse de ProcessBatch:

Here is an example of a ProcessBatch response:

<soapenv:Envelope>
 <soapenv:Body>
  <ProcessBatchResponse xmlns="CVXtractorService">
    <Results>PGRpdiB4bWxuczp3PSJodHRwOi8........</Results>
    <process_token>^E>A^D@2A032E490_]`edceca`bh_eh`d</process_token>
  </ProcessBatchResponse>
 </soapenv:Body>
</soapenv:Envelope>

The first call to ProcessBatch will initialise on the DaXtra server and it will return a unique token which will identify this batch processing.

The first call to ProcessBatch will initialise on the DaXtra server and it will return a unique token which will identify this batch processing.

The first call to ProcessBatch will initialise on the DaXtra server and it will return a unique token which will identify this batch processing.

Le premier appel à ProcessBatch initialisera sur le serveur de DaXtra et renverra un token unique qui identifiera ce traitement par lots.

First call to ProcessBatch will initialise on DaXtra server and it will return a unique token which will identify this batch processing.

  daxtra_soap_client = CreateSoapClient("http://www.daxtra.com/cvx/CVXtractorService.wsdl");
  process_batch_response = daxtra_soap_client->ProcessBatch(
                                    'document_url' =>  fileContents_base64, 
                                    'account' => service_account);
  batch_token = process_batch_response->getXMLContent("process_token"); 

Then ProcessBatch can be called in a loop to retrieve the available processing results. It will also return process_token, which should be identical to the batch_token returned in step 1 above. If the token is different it signals that this batch processing has finished.

Then ProcessBatch can be called in a loop to retrieve the available processing results. It will also return process_token, which should be identical to the batch_token returned in step 1 above. If the token is different it signals that this batch processing has finished.

Then ProcessBatch can be called in a loop to retrieve the available processing results. It will also return process_token which should be identical to the batch_token returned in step 1 above. If the token is different it signals that this batch processing has finished.

Puis vous pouvez exécuter ProcessBatch en boucle pour récupérer les résultats du traitement. Cela retournera aussi process_token, qui devrait être identique au batch_token qui a été retourné par l'étape 1 ci-dessus. Si le token est différent, ça veut dire que le traitement par lots est fini.

Then ProcessBatch can be called in a loop to retrieve the available processing results. It will also return process_token which should be identical to the batch_token returned in step 1 above. If this token is different it signals that this batch processing has finished.

    for (x = 0; x <= 1000; x++) 
    {
//-- allow time to get some processing results://-- allow time to get some processing results://-- allow time to get some processing results://-- laisser du temps pour obtenir des résultats du traitement://-- allow time to get some processing results:      pause_for_N_secs(3) 
//-- call ProcessBatch again with the obtained batch_token to retrieve some results://-- call ProcessBatch again with the obtained batch_token to retrieve some results://-- call ProcessBatch again with the obtained batch_token to retrieve some results://-- appeler ProcessBatch de nouveau avec le batch_token pour récupérer des résultats://-- call ProcessBatch again with the obtained batch_token to retrieve some results:      process_batch_response = daxtra_soap_client->ProcessBatch(
                                      'document_url' => $batch_token, 
                                      'account' => $service_account);
//-- save results as ZIP file://-- save results as ZIP file://-- save results as ZIP file://-- sauver les résultats comme fichier ZIP://-- save results as ZIP file:      result = process_batch_response->getXMLContent("Results"); 
      if(non_empty(result)) {
          save_file(result, "bacth_result.zip");
      }
//-- check if processing has finished://-- check if processing has finished://-- check if processing has finished://-- vérifie si le traitement est fini://-- check if processing has finished:      current_batch_token = process_batch response->getXMLContent("process_token");  
      if(current_batch_token != batch_token)
      {
         print current_batch_token;
         exit
      }
    }

InstallLists SOAP API call

InstallLists SOAP API call

InstallLists SOAP API call

Appel d'API SOAP InstallLists

InstallLists SOAP API call

Install user-defined lists with screenout information and skills on a DaXtra Server to be used by ProcessCV.

Install user-defined lists with screenout information and skills on a DaXtra Server to be used by ProcessCV.

Install user-defined lists with screenout information and skills on a DaXtra Server to be used by ProcessCV.

Installe des listes définies par l'utilisateur avec des informations de screenout et des compétences sur un serveur Daxtra, pour être utilisées par ProcessCV.

Install user-defined lists with screenout information and skills on a DaXtra Server to be used by ProcessCV.

Inputs:
    The type of list to install (screenout or skills)
    The contents of the list to install
    An account for this webservice

Inputs:
    The type of list to install (screenout or skills)
    The contents of the list to install
    An account for this webservice

Inputs:
    The type of list to install (screenout or skills)
    The contents of the list to install
    An account for this webservice

Entrées:
    Le type de liste à installer (screenout ou compétences)
    Les contenus de la liste à installer
    Un compte pour ce webservice

Inputs:
    The type of list to install (screenout or skills)
    The contents of the list to install
    An account for this webservice

Output:
    A success message or a soap:Fault

Output:
    A success message or a soap:Fault

Output:
    A success message or a soap:Fault

Sortie:
    Message de succès ou soap:Fault

Ausgabe:
    A success message or a soap:Fault

Every account can install one screenout list and one skills list. Screenout lists are for ignoring certain content in extracted documents and are plain text files (example). Skills lists are for recognising things particular to a given account and are XML files (example). For further details, consult your DaXtra account manager.

Every account can install one screenout list and one skills list. Screenout lists are for ignoring certain content in extracted documents and are plain text files (example). Skills lists are for recognising things particular to a given account and are XML files (example). For further details, consult your DaXtra account manager.

Every account can install one screenout list and one skills list. Screenout lists are for ignoring certain content in extracted documents and are plain text files (example). Skills lists are for recognising things particular to a given account and are XML files (example). For further details, consult your DaXtra account manager.

Chaque compte peut installer une liste de screenout et une liste de compétences. Les listes de screenout sont utilisées pour ignorer du content défini dans les documents extraits, et elles sont des fichiers en texte brut (exemple). Les listes de compétences sont utilisées pour reconnaître des choses particulières à votre compte, et elles sont des documents en XML (exemple).

Every account can install one screenout list and one skills list. Screenout lists are for ignoring certain content in extracted documents and are plain text files (example). Skills lists are for recognising things particular to a given account and are XML files (example). For further details, consult your DaXtra account manager.

See RetrieveLists to view the lists already installed.

See RetrieveLists to view the lists already installed.

See RetrieveLists to view the lists already installed.

Visiter RetrieveLists pour voir les listes qui sont déjà installées.

See RetrieveLists view the lists already installed.

Here is an example of an InstallLists request:

Here is an example of an InstallLists request:

Here is an example of an InstallLists request:

Voici un exemple d'une demande à InstallLists:

Here is an example of an InstallLists request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cvx="CVXtractorService">
    <soapenv:Header/>
    <soapenv:Body>
        <cvx:InstallLists>
            <cvx:list_type><!-- list type, either screenout or skills --></cvx:list_type>
            <cvx:account><!-- account name --></cvx:account>            <cvx:list_type><!-- list type, either screenout or skills --></cvx:list_type>
            <cvx:account><!-- account name --></cvx:account>            <cvx:list_type><!-- list type, either screenout or skills --></cvx:list_type>
            <cvx:account><!-- account name --></cvx:account>            <cvx:list_type><!-- type de liste, ou screenout ou skills --></cvx:list_type>
            <cvx:account><!-- nom du compte --></cvx:account>            <cvx:list_type><!-- list type, either screenout or skills --></cvx:list_type>
            <cvx:account><!-- Kontoname --></cvx:account>            <cvx:list_content><![CDATA[<!-- list content -->]]></cvx:list_content>
        </cvx:InstallLists>
    </soapenv:Body>
</soapenv:Envelope>

Here is an example of an InstallLists response:

Here is an example of an InstallLists response:

Here is an example of an InstallLists response:

Voici un exemple d'une réponse de InstallLists:

Here is an example of an InstallLists response:

<soap:Envelope
    soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <InstallListsResponse xmlns="CVXtractorService">
            <return_message xsi:type="xsd:string"><!-- success message --></return_message>
        </InstallListsResponse>
    </soap:Body>
</soap:Envelope>

RetrieveLists SOAP API call

RetrieveLists SOAP API call

RetrieveLists SOAP API call

Appel d'API SOAP RetrieveLists

RetrieveLists SOAP API call

Retrieve user-defined lists with screenout information or skills from a DaXtra Server.

Retrieve user-defined lists with screenout information or skills from a DaXtra Server.

Retrieve user-defined lists with screenout information or skills from a DaXtra Server.

Récupère des listes définies par l'utilisateur avec des informations de screenout ou des compétences d'un serveur DaXtra.

Retrieve user-defined lists with screenout information or skills from a DaXtra Server.

Inputs:
    The type of list to retrieve (screenout or skills).
    An account for this webservice.

Inputs:
    The type of list to retrieve (screenout or skills).
    An account for this webservice.

Inputs:
    The type of list to retrieve (screenout or skills).
    An account for this webservice.

Entrées:
    Le type de liste à récupérer (screenout ou compétences)
    Un account pour ce webservice

Inputs:
    The type of list to retrieve (screenout or skills).
    An account for this webservice.

Output: 
    The contents of the list previously installed by InstallLists.

Output: 
    The contents of the list previously installed by InstallLists.

Output: 
    The contents of the list previously installed by InstallLists.

Sortie: 
    Le contenu de la liste qui a été installé par InstallLists

Ausgabe: 
    The contents of the list previously installed by InstallLists.

Here is an example of a RetrieveLists request:

Here is an example of a RetrieveLists request:

Here is an example of a RetrieveLists request:

Voici un exemple d'une demande à RetrieveLists:

Here is an example of a RetrieveLists request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cvx="CVXtractorService">
    <soapenv:Header/>
    <soapenv:Body>
        <cvx:RetrieveLists>
            <cvx:list_type><!-- list type, either screenout or skills --></cvx:list_type>
            <cvx:account><!-- account name --></cvx:account>            <cvx:list_type><!-- list type, either screenout or skills --></cvx:list_type>
            <cvx:account><!-- account name --></cvx:account>            <cvx:list_type><!-- list type, either screenout or skills --></cvx:list_type>
            <cvx:account><!-- account name --></cvx:account>            <cvx:list_type><!-- type de liste, ou screenout ou skills --></cvx:list_type>
            <cvx:account><!-- nom du compte --></cvx:account>            <cvx:list_type><!-- list type, either screenout or skills --></cvx:list_type>
            <cvx:account><!-- Kontoname --></cvx:account>        </cvx:RetrieveLists>
    </soapenv:Body>
</soapenv:Envelope>

Here is an example of a RetrieveLists response:

Here is an example of a RetrieveLists response:

Here is an example of a RetrieveLists response:

Voici un exemple d'une réponse de RetrieveLists:

Here is an example of a RetrieveLists response:

<soap:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <RetrieveListsResponse xmlns="CVXtractorService">
            <cvx:list_content><!-- list content (XML escaped) --></cvx:list_content>            <cvx:list_content><!-- list content (XML escaped) --></cvx:list_content>            <cvx:list_content><!-- list content (XML escaped) --></cvx:list_content>            <cvx:list_content><!-- contenu de la liste (XML échappé) --></cvx:list_content>            <cvx:list_content><!-- list content (XML escaped) --></cvx:list_content>        </RetrieveListsResponse>
    </soap:Body>
</soap:Envelope>

CreateAccount SOAP API call

CreateAccount SOAP API call

CreateAccount SOAP API call

Appel d'API SOAP CreateAccount

CreateAccount SOAP API call

Create new user account on a DaXtra Server.

Create new user account on a DaXtra Server.

Create new user account on a DaXtra Server.

Créer un nouveau compte d'utilisateur sur un serveur DaXtra.

Create new user account on a DaXtra Server.

Inputs:
    An account name
    Account credentials

Inputs:
    An account name
    Account credentials

Inputs:
    An account name
    Account credentials

Entrées:
    Un nom de compte
    Des informations d'identification pour le compte

Inputs:
    An account name
    Account credentials

Output:
    A success message or a soap:Fault.

Output:
    A success message or a soap:Fault.

Output:
    A success message or a soap:Fault.

Sortie:
    Message de succès ou soap:Fault.

Ausgabe:
    A success message or a soap:Fault.

The service checks whether the caller has permission to create named accounts (from the supplied credentials) and, if so, creates the account and returns a simple success message. This account name may then be used to authenticate other operations supported by this service. For further details, consult your DaXtra account manager.

The service checks whether the caller has permission to create named accounts (from the supplied credentials) and, if so, creates the account and returns a simple success message. This account name may then be used to authenticate other operations supported by this service. For further details, consult your DaXtra account manager.

The service checks whether the caller has permission to create named accounts (from the supplied credentials) and, if so, creates the account and returns a simple success message. This account name may then be used to authenticate other operations supported by this service. For further details, consult your DaXtra account manager.

Le service vérifie si l'appelant a l'autorisation pour créer des comptes nommés (utilisant les identifiants fournis) et, si oui, crée le compte et retourne un message de succès. Ce nom de compte peut donc être utilisé pour authentifier d'autres opérations supportées par ce service. Pour en savoir plus, contactez votre gestionnaire de compte à DaXtra.

The service checks whether the caller has permission to create named accounts (from the supplied credentials) and, if so, creates the account and returns a simple success message. This account name may then be used to authenticate other operations supported by this service. For further details, consult your DaXtra account manager.

Here is an example of a CreateAccount request:

Here is an example of a CreateAccount request:

Here is an example of a CreateAccount request:

Voici un exemple d'une demande à CreateAccount:

Here is an example of a CreateAccount request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cvx="CVXtractorService">
    <soapenv:Header/>
    <soapenv:Body>
        <cvx:CreateAccount>
            <cvx:account><!-- account name --></cvx:account>
            <!-- optional -->
            <cvx:credentials><!-- account credentials --></cvx:credentials>            <cvx:account><!-- account name --></cvx:account>
            <!-- optional -->
            <cvx:credentials><!-- account credentials --></cvx:credentials>            <cvx:account><!-- account name --></cvx:account>
            <!-- optional -->
            <cvx:credentials><!-- account credentials --></cvx:credentials>            <cvx:account><!-- nom du compte --></cvx:account>
            <!-- facultatif -->
            <cvx:credentials><!-- informations d'identification du compte --></cvx:credentials>            <cvx:account><!-- Kontoname --></cvx:account>
            <!-- optional -->
            <cvx:credentials><!-- account credentials --></cvx:credentials>        </cvx:CreateAccount>
    </soapenv:Body>
</soapenv:Envelope>

Here is an example of a CreateAccount response:

Here is an example of a CreateAccount response:

Here is an example of a CreateAccount response:

Voici un exemple d'une réponse de CreateAccount:

Here is an example of a CreateAccount response:

<soap:Envelope
    soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <CreateAccountResponse xmlns="CVXtractorService">
            <return_message xsi:type="xsd:string"><!-- success message --></return_message>            <return_message xsi:type="xsd:string"><!-- success message --></return_message>            <return_message xsi:type="xsd:string"><!-- success message --></return_message>            <return_message xsi:type="xsd:string"><!-- message de succès --></return_message>            <return_message xsi:type="xsd:string"><!-- success message --></return_message>        </CreateAccountResponse>
    </soap:Body>
</soap:Envelope>

ReformatCV SOAP API call

ReformatCV SOAP API call

ReformatCV SOAP API call

Appel d'API SOAP ReformatCV

ReformatCV SOAP API call

Process resume and create an in-house-style Word document.

Process resume and create an in-house-style Word document.

Process resume and create an in-house-style Word document.

Traiter un CV et créer un document Word en style maison.

Process resume and create an in-house-style Word document.

Inputs:
    A resume document in Word format (.doc or .rtf), Base64-encoded
    An account for this webservice
    A template name
   (Optional) the XML profile extracted from the document earlier

Inputs:
    A resume document in Word format (.doc or .rtf), Base64-encoded
    An account for this webservice
    A template name
   (Optional) the XML profile extracted from the document earlier

Inputs:
    A resume document in Word format (.doc or .rtf), Base64-encoded
    An account for this webservice
    A template name
    (Optional) the XML profile extracted from the document earlier

Entrées:
    Un fichier de CV en format Word (.doc ou .rtf), encodé en Base64
    Un compte pour ce webservice
    Un nom de modèle
    (Facultatif) le profil XML qui a été extrait plus tôt

Inputs:
    A resume document in Word format (.doc or .rtf), Base64-encoded
    An account for this webservice
    A template name
   (Optional) the XML profile extracted from the document earlier

Output:
    The reformatted document (Word format, Base64-encoded)

Output:
    The reformatted document (Word format, Base64-encoded)

Output:
    The reformatted document (Word format, Base64-encoded)

Sortie:
    Le fichier remanié (format Word, encodé en Base64)

Ausgabe:
    The reformatted document (Word format, Base64-encoded)

This operation produces a custom Word CV from an original Word (or RTF) CV using a template to control the output structure and style. Such templates are normally constructed by DaXtra engineers and given a name; it is this template name that is supplied in the request. Consult your account manager for details.

This operation produces a custom Word CV from an original Word (or RTF) CV using a template to control the output structure and style. Such templates are normally constructed by DaXtra engineers and given a name; it is this template name that is supplied in the request. Consult your account manager for details.

This operation produces a custom Word CV from an original Word (or RTF) CV using a template to control the output structure and style. Such templates are normally constructed by DaXtra engineers and given a name; it is this template name that is supplied in the request. Consult your account manager for details.

Cette opération prend un CV original en Word ou RTF et produit un CV personnalisé en format Word, utilisant un modèle pour contrôler la structure et le style de la sortie. Ces modèles sont normalement construits par les ingénieurs de DaXtra, et nommés; ce nom de modèle est fourni dans la demande. Adressez-vous à votre gestionnaire de compte pour les détails.

This operation produces a custom Word CV from an original Word (or RTF) CV using a template to control the output structure and style. Such templates are normally constructed by DaXtra engineers and given a name; it is this template name that is supplied in the request. Consult your account manager for details.

If the optional profile is not supplied (as an escaped XML string) in <cvx:hrxml>, the service will automatically extract it from the document. Supplying the profile, if available, avoids re-extraction and speeds up the service.

If the optional profile is not supplied (as an escaped XML string) in <cvx:hrxml>, the service will automatically extract it from the document. Supplying the profile, if available, avoids re-extraction and speeds up the service.

If the optional profile is not supplied (as an escaped XML string) in <cvx:hrxml>, the service will automatically extract it from the document. Supplying the profile, if available, avoids re-extraction and speeds up the service.

Si le profil facultatif n'est pas fourni (comme fil XML échappé) en <cvx:hrxml>, le service l'extraira automatiquement du fichier. Si vous fournissez le profil vous éviterez une nouvelle extraction, ce qui rend le service plus vite.

If the optional profile is not supplied (as an escaped XML string) in <cvx:hrxml>, the service will automatically extract it from the document. Supplying the profile, if available, avoids re-extraction and speeds up the service.

Here is an example of a ReformatCV request:

Here is an example of a ReformatCV request:

Here is an example of a ReformatCV request:

Voici un exemple d'une demande à ReformatCV:

Here is an example of a ReformatCV request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cvx="CVXtractorService">
    <soapenv:Header/>
    <soapenv:Body>
        <cvx:ReformatCV>
            <cvx:document_url><!-- Base64-encoded Word or RTF document --></cvx:document_url>
            <cvx:account><!-- account name --></cvx:account>
            <cvx:template><!-- name of reformatting template --></cvx:template>
            <!--Optional:-->
            <cvx:hrxml><![CDATA[<!-- XML profile -->]]></cvx:hrxml>            <cvx:document_url><!-- Base64-encoded Word or RTF document --></cvx:document_url>
            <cvx:account><!-- account name --></cvx:account>
            <cvx:template><!-- name of reformatting template --></cvx:template>
            <!--Optional:-->
            <cvx:hrxml><![CDATA[<!-- XML profile -->]]></cvx:hrxml>            <cvx:document_url><!-- Base64-encoded Word or RTF document --></cvx:document_url>
            <cvx:account><!-- account name --></cvx:account>
            <cvx:template><!-- name of reformatting template --></cvx:template>
            <!--Optional:-->
            <cvx:hrxml><![CDATA[<!-- XML profile -->]]></cvx:hrxml>            <cvx:document_url><!-- fichier Word ou RTF, encodé en Base64 --></cvx:document_url>
            <cvx:account><!-- nom du compte --></cvx:account>
            <cvx:template><!-- nom du modèle de remaniement --></cvx:template>
            <!--Facultatif:-->
            <cvx:hrxml><![CDATA[<!-- profil XML -->]]></cvx:hrxml>            <cvx:document_url><!-- Base64-encoded Word or RTF document --></cvx:document_url>
            <cvx:account><!-- Kontoname --></cvx:account>
            <cvx:template><!-- name of reformatting template --></cvx:template>
            <!--Optional:-->
            <cvx:hrxml><![CDATA[<!-- XML profile -->]]></cvx:hrxml>            <cvx:options><!-- keep_bold keep_italic keep_bold keep_underline keep_color keep_image keep_template_style/keep_cv_style --></cvx:options>
        </cvx:ReformatCV>
    </soapenv:Body>
</soapenv:Envelope>

Here is an example of a ReformatCV response:

Here is an example of a ReformatCV response:

Here is an example of a ReformatCV response:

Voici un exemple d'une réponse de ReformatCV:

Here is an example of a ReformatCV response:

<soap:Envelope
    soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <ReformatCVResponse xmlns="CVXtractorService">
            <doc xsi:type="xsd:base64Binary"><!-- Word document, Base64-encoded --></doc>            <doc xsi:type="xsd:base64Binary"><!-- Word document, Base64-encoded --></doc>            <doc xsi:type="xsd:base64Binary"><!-- Word document, Base64-encoded --></doc>            <doc xsi:type="xsd:base64Binary"><!-- fichier Word, encodé en Base64 --></doc>            <doc xsi:type="xsd:base64Binary"><!-- Word document, Base64-encoded --></doc>        </ReformatCVResponse>
    </soap:Body>
</soap:Envelope>

Convert SOAP API call

Convert SOAP API call

Convert SOAP API call

Appel d'API SOAP Convert

Convert SOAP API call

Inputs:
    document_url - Base64-encoded document in a supported format (Word, PDF, etc.), or its URL
    account - account for this webservice
    to - target format (HTML, DOCX, PDF, TXT)

Inputs:
    document_url - Base64-encoded document in a supported format (Word, PDF, etc.), or its URL
    account - account for this webservice
    to - target format (HTML, DOCX, PDF, TXT)

Inputs:
    document_url - Base64-encoded document in a supported format (Word, PDF, etc.), or its URL
    account - account for this webservice
    to - target format (HTML, DOCX, PDF, TXT)

Entrées:
    document_url - fichier encodé en Base64 dans un format supportée (Word, PDF, etc.), ou son URL
    account - compte pour ce webservice
    to - format cible (HTML, DOCX, PDF, TXT)

Inputs:
    document_url - Base64-encoded document in a supported format (Word, PDF, etc.) or its URL
    account - account for this webservice
    to - target format (HTML, DOCX, PDF, TXT)

Output:
    Base64-encoded doc element

Output:
    Base64-encoded doc element

Output:
    Base64-encoded doc element

Sortie:
    élément doc encodé en Base64

Ausgabe:
    Base64-encoded doc element

Here is an example of the type of escaped XML string returned:

Here is an example of the type of escaped XML string returned:

Here is an example of the type of escaped XML string returned:

Voici un exemple du type de chaîne XML échappée qui sera retourné:

Here is an example of the type of escaped XML string returned:

Here is an example of a Convert to html request:

Here is an example of a Convert to html request:

Here is an example of a Convert to html request:

Voici un exemple d'une demande à Convert à html:

Here is an example of a Convert to html request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cvx="CVXtractorService">
    <soapenv:Header/>
    <soapenv:Body>
        <cvx:Convert>
            <cvx:document_url><!-- Base64-encoded document --></cvx:document_url>
            <cvx:account><!-- account name --></cvx:account>            <cvx:document_url><!-- Base64-encoded document --></cvx:document_url>
            <cvx:account><!-- account name --></cvx:account>            <cvx:document_url><!-- Base64-encoded document --></cvx:document_url>
            <cvx:account><!-- account name --></cvx:account>            <cvx:document_url><!-- fichier encodé en Base64 --></cvx:document_url>
            <cvx:account><!-- nom du compte --></cvx:account>            <cvx:document_url><!-- Base64-codierte Datei --></cvx:document_url>
            <cvx:account><!-- Kontoname --></cvx:account>            <cvx:to>html</cvx:to>
        </cvx:Convert>
    </soapenv:Body>
</soapenv:Envelope>

Here is an example of a Convert response:

Here is an example of a Convert response:

Here is an example of a Convert response:

Voici un exemple d'une réponse de Convert:

Here is an example of a Convert response:

<soap:Envelope
    soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <ConvertResponse xmlns="CVXtractorService">
            <doc xsi:type="xsd:base64Binary"><!-- Base64-encoded content --></doc>            <doc xsi:type="xsd:base64Binary"><!-- Base64-encoded content --></doc>            <doc xsi:type="xsd:base64Binary"><!-- Base64-encoded content --></doc>            <doc xsi:type="xsd:base64Binary"><!-- contenu encodé en Base64 --></doc>            <doc xsi:type="xsd:base64Binary"><!-- Base64-encoded content --></doc>        </ConvertResponse>
    </soap:Body>
</soap:Envelope>

To convert with extra quality (but this can be slower) add the -qual option to the account field: "account; -qual".

To convert with extra quality (but this can be slower) add the -qual option to the account field: "account; -qual".

To convert with extra quality (but this can be slower) add the -qual option to the account field: "account; -qual".

Pour convertir avec meilleure qualité mais moins vite, ajouter l'option -qual dans le champ du compte: "account; -qual".

To convert with extra quality (but this can be slower) add the -qual option to the account field: "account; -qual".

PDF2Word SOAP API call

PDF2Word SOAP API call

PDF2Word SOAP API call

Appel d'API SOAP PDF2Word

PDF2Word SOAP API call

Inputs:
    Any PDF document (Base64-encoded)
    An account for this webservice

Inputs:
    Any PDF document (Base64-encoded)
    An account for this webservice

Inputs:
    Any PDF document (Base64-encoded)
    An account for this webservice

Entrées:
    Un fichier PDF (encodé en Base64)
    Un account pour ce webservice

Inputs:
    Any PDF document (Base64-encoded)
    An account for this webservice

Output:
    The same document reformatted as Word (.doc, Base64-encoded)

Output:
    The same document reformatted as Word (.doc, Base64-encoded)

Output:
    The same document reformatted as Word (.doc, Base64-encoded)

Sortie:
    Le même fichier remanié en Word (.doc, Base64-encoded)

Ausgabe:
    The same document reformatted as Word (.doc, Base64-encoded)

Here is an example of a PDF2Word request:

Here is an example of a PDF2Word request:

Here is an example of a PDF2Word request:

Voici un exemple d'une demande à PDF2Word:

Here is an example of a PDF2Word request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cvx="CVXtractorService">
    <soapenv:Header/>
    <soapenv:Body>
        <cvx:PDF2Word>
            <cvx:document_url><!-- Base64-encoded PDF document --></cvx:document_url>
            <cvx:account><!-- account name --></cvx:account>
        </cvx:PDF2Word>
    </soapenv:Body>
</soapenv:Envelope>

Here is an example of a PDF2Word response:

Here is an example of a PDF2Word response:

Here is an example of a PDF2Word response:

Voici un exemple d'une réponse de PDF2Word:

Here is an example of a PDF2Word response:

<soap:Envelope
    soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
        <PDF2WordResponse xmlns="CVXtractorService">
            <doc xsi:type="xsd:base64Binary"><!-- Base64-encoded Word document --></cvx:doc>
        </PDF2WordResponse>
    </soap:Body>
</soap:Envelope>

JS Widget

Here is a JavaScript example of the REST call POST /cvx/rest/api/v1/profile/full/json. We will be using the multipart/form-data POST style by using a FormData object.

Here is a JavaScript example of the REST call POST /cvx/rest/api/v1/profile/full/json. We will be using the multipart/form-data POST style by using a FormData object.

Here is a JavaScript example of the REST call POST /cvx/rest/api/v1/profile/full/json. We will be using the multipart/form-data POST style by using a FormData object.

Voici un exemple en JavaScript de l'appel REST POST /cvx/rest/api/v1/profile/full/json. Nous utiliserons le style multipart/form-data POST en utilisant un objet FormData.

Here is a JavaScript example of the REST call POST /cvx/rest/api/v1/profile/full/json. We will be using the multipart/form-data POST style by using a FormData object.

Since this script is visible to the general public, instead of an account name we will be using a Secure Token valid only for a single processing.

Since this script is visible to the general public, instead of an account name we will be using a Secure Token valid only for a single processing.

Since this script is visible to the general public instead of an account name we will be using a Secure Token valid only for a single processing.

Parce que ce script est visible par le public, au lieu d'un nom de compte nous utiliserons un Secure Token qui n'est valide que pour un seul processus.

Since this script is visible to the general public instead of an account name we will be using a Secure Token valid only for a single processing.

  <input type='file' id='my_file_upload_id'  /> 
  <input type='button' value='Send to CVX' 
        onclick='handle_file_upload_field("my_file_upload_id")'/>

<script type="text/javascript">

//-- or any other DaXtra server://-- or any other DaXtra server://-- or any other DaXtra server://-- ou n'importe quel serveur de DaXtra://-- or any other DaXtra server:var CVX_SERVER="http://cvx.daxtra.com";

//--  Secure Token provided by DaXtra://--  Secure Token provided by DaXtra://--  Secure Token provided by DaXtra://--  Secure Token que DaXtra vous a donné://--  Secure Token provided by DaXtra:var CVX_SECURE_TOKEN="XXXXXXX";

//-- function which is fired when button "Send to CVX" is clicked://-- function which is fired when button "Send to CVX" is clicked://-- function which is fired when button "Send to CVX" is clicked://-- fonction qui est activée quand on clique sur le bouton "Send to CVX"://-- function which is fired when button "Send to CVX" is clicked:function handle_file_upload_field(file_upload_id) 
{
  var fileInput = document.getElementById(file_upload_id)
  var file = fileInput.files[0];

  var formData = new FormData();
  formData.append("file", file);
//-- add turbo processing option://-- add turbo processing option://-- add turbo processing option://-- ajouter l'option du mode turbo://-- add turbo processing option:  formData.append("account", CVX_SECURE_TOKEN + "; -turbo"); 
  
  var xhr = prepare_xhr(my_cvx_return_handler);
  xhr.open("POST", CVX_SERVER +"/cvx/rest/api/v1/profile/full/json");
  xhr.send(formData);
}

function prepare_xhr(handler)
{
   var xhr = new XMLHttpRequest();
   xhr.onreadystatechange = function(e) {
     var resp_text; 
     if (xhr.readyState!=4) { return; }
     if (xhr.readyState==4 && xhr.status==200)
     {      
       handler(this.responseText);
     }
     else {
       var ret_string;
//-- errors generated by CVX://-- errors generated by CVX://-- errors generated by CVX://-- erreurs produites par CVX://-- errors generated by CVX:       if(this.responseText.match(/^{/)) {
           ret_string = this.responseText;
       }
       else {
//-- other errors are represented as JSON with status 999://-- other errors are represented as JSON with status 999://-- other errors are represented as JSON with status 999://-- d'autres erreurs se voient en JSON avec le statut 999://-- other errors are represented as JSON with status 999:          ret_string = '{"CSERRROR":{"message":"' + xhr.statusText + '", "code": 999}}';
       }
       handler(ret_string, xhr.status);
     }
   };

   return xhr;
}

function my_cvx_return_handler(json_response, error_code)
{
  var profile_json = JSON.parse(json_response)
  if(error_code || profile_json.CSERROR){
     //-- report error     //-- report error     //-- report error     //-- signaler l'erreur     //-- report error  }
  else if(profile_json.StructuredResume) {
     //-- do something with profile_json, which contains all extracted data      //-- do something with profile_json, which contains all extracted data     //-- do something with profile_json, which contains all extracted data     //-- faîtes quelque chose avec profile_json, qui contient toutes les données extraites     //-- do something with profile_json, which contains all extracted data  }
}

</script>

Here is a JavaScript example of the REST call POST /cvx/rest/api/v1/profile/personal/json, which takes less time than full profile extraction, so personal data can be put in a web form for a quicker response. Here we will be using the application/json POST style.

Here is a JavaScript example of the REST call POST /cvx/rest/api/v1/profile/personal/json, which takes less time than full profile extraction, so personal data can be put in a web form for quicker response. Here we will be using the application/json POST style.

Here is a JavaScript example of the REST call POST /cvx/rest/api/v1/profile/personal/json, which takes less time than full profile extraction, so personal data can be put in a web form for a quicker response. Here we will be using the application/json POST style.

Voici un exemple en JavaScript d'un appel de REST POST /cvx/rest/api/v1/profile/personal/json, qui prend moins de temps que l'extraction d'un profil complet, pour que les données personnelles peuvent se transférer à un formulaire web pour une réponse plus vite. Ici on utilisera le style POST application/json.

Here is a JavaScript example of REST call POST /cvx/rest/api/v1/profile/personal/json, which takes less time than full profile extraction, so personal data can be put in a web form for a quicker response. Here we will be using the application/json POST style.

Since this script is visible to the general public, instead of an account name we will be using a Secure Token valid only for a single processing.

Since this script is visible to the general public, instead of an account name we will be using a Secure Token valid only for a single processing.

Since this script is visible to the general public, instead of an account name we will be using a Secure Token valid only for single processing.

Parce que ce script est visible par le public, au lieu d'un nom de compte nous utiliserons un Secure Token qui n'est valide que pour un seul processus.

Since this script is visible to general public instead of account name we will be using a Secure Token valid only for single processing.

After receiving personal data we will follow with a GET /cvx/rest/api/v1/data API call which will bring back the full profile.

After receiving personal data we will follow with a GET /cvx/rest/api/v1/data API call which will bring back the full profile.

After receiving personal data we will follow with a GET /cvx/rest/api/v1/data API call which will bring back the full profile.

Après avoir reçu les données personnelles, nous transmettrons ensuite un appel d'API GET /cvx/rest/api/v1/data qui retournera le profil complet.

After receiving personal data we will follow with a GET /cvx/rest/api/v1/data API call which will bring back the full profile.

  <input type='file' id='my_file_upload_id'  /> 
  <input type='button' value='Send to CVX' 
        onclick='handle_file_upload_field("my_file_upload_id")'/>

<script type="text/javascript">
//-- or any other DaXtra server://-- or any other DaXtra server://-- or any other DaXtra server://-- ou n'importe quel serveur de DaXtra://-- or any other DaXtra server:var CVX_SERVER="http://cvx.daxtra.com"; 

//--  Secure Token provided by DaXtra://--  Secure Token provided by DaXtra://--  Secure Token provided by DaXtra://--  Secure Token que DaXtra vous a donné://--  Secure Token provided by DaXtra:var CVX_SECURE_TOKEN="XXXXXXX";   

function handle_file_upload_field(file_upload_id) 
{
  var fileInput = document.getElementById(file_upload_id)
  var file = fileInput.files[0];

  var reader  = new FileReader();
  reader.onload = function(e) {
    var content = reader.result;
//- delete header / leave only content://- delete header / leave only content://- delete header / leave only content://- effacer l'en-tête / ne laisser que le contenu://- delete header / leave only content:    content = content.replace(/^.*;base64,/, ""); 
//-- add turbo processing option://-- add turbo processing option://-- add turbo processing option://-- ajouter l'option du mode turbo://-- add turbo processing option:    var account_str = daxtra_cvx.account + '; -turbo'; 
    var jsonData = {account: account_str, file: content};
    var xhr = prepare_xhr(my_cvx_return_handler_phase1);
    xhr.open("POST", CVX_SERVER +"/cvx/rest/api/v1/profile/personal/json");
    xhr.setRequestHeader("Content-type", "application/json");
    xhr.send(JSON.stringify(jsonData));
    delete xhr;
  };
//-- Base64-encoded://-- Base64-encoded://-- Base64-encoded://-- encodé en Base64://-- Base64-codiert:  reader.readAsDataURL(file); 
}


function prepare_xhr(handler)
{
   var xhr = new XMLHttpRequest();
   xhr.onreadystatechange = function(e) {
     var resp_text; 
     if (xhr.readyState!=4) { return; }
     if (xhr.readyState==4 && xhr.status==200)
     {      
       handler(this.responseText);
     }
     else {
       var ret_string;
//-- errors generated by CVX://-- errors generated by CVX://-- errors generated by CVX://-- erreurs produites par CVX://-- errors generated by CVX:       if(this.responseText.match(/^{/)) { 
           ret_string = this.responseText;
       else {
//-- other errors are represented as JSON with status 999://-- other errors are represented as JSON with status 999://-- other errors are represented as JSON with status 999://-- d'autres erreurs se voient en JSON avec le statut 999://-- other errors are represented as JSON with status 999:          ret_string = '{"CSERRROR":{"message":"' + xhr.statusText + '", "code": 999}}';
       }
       handler(ret_string, xhr.status);
     }
   };

   return xhr;
}



function my_cvx_return_handler_phase1(json_response, error_code)
{
  var profile_json = JSON.parse(json_response)
  if(error_code || profile_json.CSERROR){
     //-- report error     //-- report error     //-- report error     //-- signaler l'erreur     //-- report error     return;
  }
  else if(profile_json.StructuredResume) {
     //-- do something with profile_json, which contains
     //-- only personal data: name and contact details     //-- do something with profile_json, which contains
     //-- only personal data: name and contact details     //-- do something with profile_json, which contains
     //-- only personal data: name and contact details     //-- faîtes quelque chose avec profile_json, qui ne contient que
     //-- les données personnelles: le nom et les coordonnées     //-- do something with profile_json, which contains
     //-- only personal data: name and contact details  }

//-- get full profile://-- get full profile://-- get full profile://-- récupérer le profil complet://-- get full profile:  if(profile_json.phase2_token)
  {
      var xhr = prepare_xhr(my_cvx_return_handler_phase2);
      xhr.open("GET", CVX_SERVER +"/cvx/rest/api/v1/data"
                    +  "?token=" + profile_json.phase2_token)
      xhr.send()
  }
}

function my_cvx_return_handler_phase2(json_response, error_code)
{
  var profile_json = JSON.parse(json_response)
  if(error_code || profile_json.CSERROR){
      //-- report error    //-- report error     //-- report error     //-- signaler une erreur     //-- report error  }
  else if(profile_json.StructuredResume) {
      //-- do something with profile_json, which contains all extracted data     //-- do something with profile_json, which contains all extracted data     //-- do something with profile_json, which contains all extracted data     //-- faîtes quelque chose avec profile_json, qui contient toutes les données extraites     //-- do something with profile_json, which contains all extracted data  }
}

Here is an example of a REST API call /profile/full/xml to the DaXtra Server from VB6 (ASP code is very similar). The data transfer mechanism is through posting an XML item.

Here is an example of a REST API call /profile/full/xml to the DaXtra Server from VB6 (ASP code is very similar). The data transfer mechanism is through posting an XML item.

Here is an example of a REST API call /profile/full/xml to the DaXtra Server from VB6 (ASP code is very similar). The data transfer mechanism is through posting an XML item.

Voici un exemple d'un appel d'API REST /profile/full/xml au DaXtra Server de VB6 (le code ASP est très similaire). Le mécanisme du transfert de données est par envoyer un élément XML.

Here is an example of a REST API call /profile/full/xml to the DaXtra Server from VB6 (ASP code is very similar). The data transfer mechanism is through posting an XML item.

Public Function processCV(ByVal service_url As String, _
                         ByVal service_account As String, _
                         ByVal file_to_process As String) As String
  On Error GoTo err_handler
  
  '--- read file into Base64 string -----------  '--- read file into Base64 string -----------  '--- read file into Base64 string -----------  '--- transformer le fichier en chaîne de Base64 -----------  '--- read file into Base64 string -----------  doc_content = ReadBinFileAsBase64(file_to_process)
   
  '---- prepare XML item for posting -------------------------  '---- prepare XML item for posting -------------------------  '---- prepare XML item for posting -------------------------  '---- préparer l'élément XML pour l'afficher -------------------------  '---- prepare XML item for posting -------------------------  http_request = "<Request><account>" & service_account & "</account>"
  http_request = http_request & "<file>" & doc_content & "</file></Request>"

  '----------- execute (POST) API call with data ------------------  '----------- execute (POST) API call with data ------------------  '----------- execute (POST) API call with data ------------------  '----------- exécuter l'appel d'API (POST) avec les données ------------------  '----------- execute (POST) API call with data ------------------  Dim xmlReq As Object
  Set xmlReq = CreateObject("Microsoft.XMLHTTP")
  xmlReq.Open   "POST", "http://" & service_url & "/cvx/rest/api/v1/profile/full/xml", False
  xmlReq.setRequestHeader "Content-Type", "text/xml"
  xmlReq.setRequestHeader "Connection", "close"
  xmlReq.send (http_request)

  '----- get the results ----------------------  '----- get the results ----------------------  '----- get the results ----------------------  '----- récupérer les résultats ----------------------  '----- get the results ----------------------  If (xmlReq.Status >= 200 And xmlReq.Status < 300) Then  ' -- SUCCESS
     txtResponseHeaders = xmlReq.getAllResponseHeaders
     processCV = xmlReq.responseText    
  Else
     processCV = "ERROR: Request Failed with status " & xmlReq.Status & vbCrLf
     processCV = processCV & xmlReq.responseText
  End If
  Exit Function
  
err_handler:
  If Err.Number <> 0 Then processCV = "Error " & Err.Number & ": " & Err.Description
End Function

 
Private Function ReadBinFileAsBase64(sFile As String) As String
  Dim binFileArray() As Byte
  binFileArray() = ReadBinFile(sFile)
  ReadBinFileAsBase64 = EncodeBase64(binFileArray)
End Function

Private Function ReadBinFile(sFile As String) As Byte()
  Dim nFile       As Integer

  nFile = FreeFile
  Open sFile For Binary Access Read As #nFile
  If LOF(nFile) > 0 Then
     ReDim ReadBinFile(0 To LOF(nFile) - 1)
     Get nFile, , ReadBinFile
  End If
  Close #nFile
End Function


Private Function EncodeBase64(ByRef arrData() As Byte) As String   
  Dim objXML As Object
  Set objXML = CreateObject("MSXML2.DOMDocument")
  Dim objNode As Object
      
  ' byte array to base64
  Set objNode = objXML.createElement("b64")
  objNode.dataType = "bin.base64"
  objNode.nodeTypedValue = arrData
  EncodeBase64 = objNode.Text
 
  Set objNode = Nothing
  Set objXML = Nothing
End Function

Here is a JavaScript example of a REST call POST /cvx/rest/api/v1/joborder/json. We will be using the multipart/form-data POST style by using a FormData object.

Here is a JavaScript example of a REST call POST /cvx/rest/api/v1/joborder/json. We will be using the multipart/form-data POST style by using a FormData object.

Here is a JavaScript example of a REST call POST /cvx/rest/api/v1/joborder/json. We will be using the multipart/form-data POST style by using a FormData object.

Voici un exemple en JavaScript d'un appel REST POST /cvx/rest/api/v1/joborder/json. Nous utiliserons le style multipart/form-data POST en utilisant un objet FormData.

Here is a JavaScript example of a REST call POST /cvx/rest/api/v1/joborder/json. We will be using the multipart/form-data POST style by using a FormData object.

<input type='file' id='my_file_upload_id'/>
<input type='button' value='Send to CVX' onclick='handle_file_upload_field("my_file_upload_id")'/>

<script type="text/javascript">

var CVX_SERVER="http://cvx.daxtra.com"; //- or any other DaXtra server
var account = "account_name";

//-- function which is fired when button "Send to CVX" is
function handle_file_upload_field(file_upload_id)
{
  var fileInput = document.getElementById(file_upload_id);
  var file = fileInput.files[0];

  var formData = new FormData();
  formData.append("file", file);
  formData.append("account", account);

  var xhr = prepare_xhr(my_cvx_return_handler);
  xhr.open("POST", CVX_SERVER +"/cvx/rest/api/v1/joborder/json");
  xhr.send(formData);
}

function prepare_xhr(handler)
{
   var xhr = new XMLHttpRequest();
   xhr.onreadystatechange = function(e) {
     var resp_text;
     if (xhr.readyState!=4) { return; }
     if (xhr.readyState==4 && xhr.status==200)
     {
       handler(this.responseText);
     }
     else {
       var ret_string;
       if(this.responseText.match(/^{/)) {  //-- errors generated by CVX
           ret_string = this.responseText;
       }
       else {
//-- other errors are represented as JSON with status 999://-- other errors are represented as JSON with status 999://-- other errors are represented as JSON with status 999://-- d'autres erreurs se voient en JSON avec le statut 999://-- other errors are represented as JSON with status 999:          ret_string = '{"CSERRROR":{"message":"' + xhr.statusText + '", "code": 999}}';
       }
       handler(ret_string, xhr.status);
     }
   };

   return xhr;
}

function my_cvx_return_handler(json_response, error_code)
{
  var profile_json = JSON.parse(json_response)
  if(error_code || profile_json.CSERROR){
     //-- report error     //-- report error     //-- report error     //-- signaler une erreur     //-- report error  }
  else if(profile_json.StructuredResume) {
     //-- do something with profile_json, which contains all extracted data     //-- do something with profile_json, which contains all extracted data     //-- do something with profile_json, which contains all extracted data     //-- faîtes quelque chose avec profile_json, qui contient toutes les données extraites     //-- do something with profile_json, which contains all extracted data  }
}

</script>

Account: <input type='text' id='screenout_account_name'/></br>
Screenout File: <input type='file' id='my_screenout_file_upload_id'  /></br>
<input type='button' value='install_screenout' 
 onclick='handle_file_upload_field_screenout("my_screenout_file_upload_id", "screenout_account_name")'/></br>

Account: <input type='text' id='skills_account_name'/></br>
Skills File: <input type='file' id='my_skills_file_upload_id'  /></br>
<input type='button' value='install_skills' 
 onclick='handle_file_upload_field_skills("my_skills_file_upload_id", "skills_account_name")'/>

<script type="text/javascript">

//-- or any other DaXtra server://-- or any other DaXtra server://-- or any other DaXtra server://-- ou n'importe quel serveur de DaXtra:or any other DaXtra server:var CVX_SERVER="http://cvx.daxtra.com"; 

//-- function which is fired when button "install_screenout" is
function handle_file_upload_field_screenout(file_upload_id, account_name)
{
  var fileInput = document.getElementById(file_upload_id)
  var file = fileInput.files[0];
  var account = document.getElementById(account_name).value;

  var formData = new FormData();
  formData.append("file", file);
  formData.append("account", account);

  var xhr = prepare_xhr(my_cvx_return_handler);
  xhr.open("POST", CVX_SERVER +"/cvx/rest/api/v1/list/screenout");
  xhr.send(formData);
}

//-- function which is fired when button "install_skills" is
function handle_file_upload_field_skills(file_upload_id, account_name)
{
  var fileInput = document.getElementById(file_upload_id)
  var file = fileInput.files[0];
  var account = document.getElementById(account_name).value;

  var formData = new FormData();
  formData.append("file", file);
  formData.append("account", account);

  var xhr = prepare_xhr(my_cvx_return_handler);
  xhr.open("POST", CVX_SERVER +"/cvx/rest/api/v1/list/skills");
  xhr.send(formData);
}
function my_cvx_return_handler(resp_text, error_code)
{
  if(error_code){
    //-- report error
  }
  else if(resp_text) {
    //-- do something with resp_text which contains screenout/skill list(s)
  }
}

function prepare_xhr(handler)
{
   var xhr = new XMLHttpRequest();
   xhr.onreadystatechange = function(e) {
     var resp_text;
     if (xhr.readyState!=4) { return; }
     if (xhr.readyState==4 && xhr.status==200)
     {
       handler(this.responseText);
     }
     else {
       var ret_string;
       //-- errors represent as json with status 999
       ret_string = '{"CSERRROR":{"message":"' + xhr.statusText + '", "code": 999}}';
       handler(ret_string, xhr.status);
     }
   };

   return xhr;
}


</script>

1. To get an account-specific token:

1. To get an account-specific token:

1. To get an account-specific token:

1. Pour recevoir un token spécifique au compte:

1. To get an account-specific token:

my $cookie_jar = HTTP::Cookies->new(
    file           => "/tmp/cookies",
    autosave       => 1,
    ignore_discard => 1,
);
$ua->cookie_jar( $cookie_jar );

$req = HTTP::Request->new(
    "GET",
    "https://v2.daxtra.io/login/yubi/ccccccdhgbjfltenvblubekufkjirfgdendrvlrkvbvl",
);
$resp = $ua->request($req);

$req = HTTP::Request->new(
    "GET",
    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/token",
);
$resp = $ua->request($req);

{"ok":"90706a23-0183-4345-b977-e1d68d1f8b74"}

my $cookie_jar = HTTP::Cookies->new(
    file           => "/tmp/cookies",
    autosave       => 1,
    ignore_discard => 1,
);
$ua->cookie_jar( $cookie_jar );

$req = HTTP::Request->new(
    "GET",
    "https://v2.daxtra.io/login/account/$MYCUSTOMER/$token",
);
$resp = $ua->request($req);

$req = HTTP::Request->new(
    "POST",
    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # ou "/screenout" pour screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout);
$req->content($MYSKILLS);
$resp = $ua->request($req);

$req = HTTP::Request->new(
    "DELETE",
    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # ou "/screenout" pour screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout);
$resp = $ua->request($req);

<input type='text' id='screenout_account_name'/>
<input type='button' value='get_screenout' onclick='retrieve_screenout("screenout_account_name")'/></br>

<input type='text' id='skills_account_name'/>
<input type='button' value='get_skills' onclick='retrieve_skills("skills_account_name")'/>

<script type="text/javascript">

var CVX_SERVER="http://cvx.daxtra.com"; //- or any other DaXtra server

//-- function which is fired when button "get_screenout" is
function retrieve_screenout(account_name){
    var account = document.getElementById(account_name).value;
    var url = CVX_SERVER + "/cvx/rest/api/v1/list/screenout&account=" + account;
    document.write(url + "</br>");

    var xhr = prepare_xhr(my_return_handler);
    xhr.open("GET", url, false);
    xhr.send( null );
}

//-- function which is fired when button "get_skills" is
function retrieve_skills(account_name){
    var account = document.getElementById(account_name).value;
    var url = CVX_SERVER + "/cvx/rest/api/v1/list/skills&account=" + account;
    document.write(url + "</br>");

    var xhr = prepare_xhr(my_return_handler);
    xhr.open("GET", url, false);
    xhr.send( null );
}

function my_return_handler(resp_text, error_code)
{  
  if(error_code){
    //-- report error
  }
  else if(resp_text) {
    //-- do something with resp_text which contains screenout/skill list(s)
  }
}

function prepare_xhr(handler)
{
   var xhr = new XMLHttpRequest();
   xhr.onreadystatechange = function(e) {
     var resp_text;
     if (xhr.readyState!=4) { return; }
     if (xhr.readyState==4 && xhr.status==200)
     {
       handler(this.responseText);
     }
     else {
       var ret_string;
       //-- errors represent as json with status 999
       ret_string = '{"CSERRROR":{"message":"' + xhr.statusText + '", "code": 999}}';
       handler(ret_string, xhr.status);
     }
   };

   return xhr;
}


</script>

1. To get an account-specific token:

1. To get an account-specific token:

1. To get an account-specific token:

1. Pour recevoir un token spécifique au compte:

1. To get an account-specific token:

my $cookie_jar = HTTP::Cookies->new(
    file           => "/tmp/cookies",
    autosave       => 1,
    ignore_discard => 1,
);
$ua->cookie_jar( $cookie_jar );

$req = HTTP::Request->new(
    "GET",
    "https://v2.daxtra.io/login/yubi/ccccccdhgbjfltenvblubekufkjirfgdendrvlrkvbvl",
);
$resp = $ua->request($req);

$req = HTTP::Request->new(
    "GET",
    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/token",
);
$resp = $ua->request($req);

{"ok":"90706a23-0183-4345-b977-e1d68d1f8b74"}

my $cookie_jar = HTTP::Cookies->new(
    file           => "/tmp/cookies",
    autosave       => 1,
    ignore_discard => 1,
);
$ua->cookie_jar( $cookie_jar );

$req = HTTP::Request->new(
    "GET",
    "https://v2.daxtra.io/login/account/$MYCUSTOMER/$token",
);
$resp = $ua->request($req);

$req = HTTP::Request->new(
    "GET",
    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # ou "/screenout" pour screenout    "https://v2.daxtra.io/cvx/accounts/$MYCUSTOMER/skills",  # or "/screenout" for screenout);
$resp = $ua->request($req);
print STDERR $resp->content();  
# do something with response content, which contains screenout/skill list(s)# do something with response content, which contains screenout/skill list(s)# do something with response content, which contains screenout/skill list(s)# faîtes quelque chose avec le contenu de la réponse, qui contient une liste de screenout/compétences# do something with response content, which contains screenout/skill list(s)

Account: <input type='text' id='account_name'/></br>
Template: <input type='text' id='template'/></br>
File: <input type='file' id='my_file_upload_id'/></br>
HRXML: <input type='file' id='my_hrxml_file_upload_id'/></br>
<input type='button' value='ReformatCV' 
 onclick='handle_file_upload_styler("my_file_upload_id", "account_name", "template", "my_hrxml_file_upload_id")'/>

<script type="text/javascript">

var CVX_SERVER="http://cvx.daxtra.com"; //- or any other DaXtra server

//-- function which is fired when button "ReformatCV" is
function handle_file_upload_styler(file_upload_id, account_name, template, hrxml_file_upload_id)
{
  var fileInput = document.getElementById(file_upload_id)
  var file = fileInput.files[0];
  var account = document.getElementById(account_name).value;
  var template = document.getElementById(template).value;
  var hrxml_fileInput = document.getElementById(hrxml_file_upload_id)
  var hrxml_file = hrxml_fileInput.files[0];

  var formData = new FormData();
  formData.append("file", file);
  formData.append("account", account);
  formData.append("template", template);
  if (hrxml_file_upload_id) {
    formData.append("hrxml", hrxml_file);
  }

  var xhr = prepare_xhr(my_return_handler);
  xhr.open("POST", CVX_SERVER +"/cvx/rest/api/v1/styler");
  xhr.send(formData);
}

function prepare_xhr(handler)
{
   var xhr = new XMLHttpRequest();
   xhr.onreadystatechange = function(e) {
     var resp_text;
     if (xhr.readyState!=4) { return; }
     if (xhr.readyState==4 && xhr.status==200)
     {
       handler(this.responseText);
     }
     else {
       var ret_string;
       //-- errors represent as json with status 999
       ret_string = '{"CSERRROR":{"message":"' + xhr.statusText + '", "code": 999}}';
       handler(ret_string, xhr.status);
     }
   };

   return xhr;
}

function my_return_handler(resp_doc, error_code)
{
  if(error_code){
    //-- report error
  }
  else if(resp_doc) {
    //-- do something with reformatted resp_doc
  }
}

</script>

Below is an example of a SOAP call from Python:

Below is an example of a SOAP call from Python:

如下为在Python中的SOAP调用示例：

Ci-dessous se trouve un exemple d'un appel SOAP de Python:

Below is an example of a SOAP call from Python:

from suds.client import Client
from base64 import b64encode

def daxtra_process_cv(service_url, service_account, file_to_process):
   f = open(file_to_process,'rb')
   filecontent = f.read()
   daxtra_soap_client = Client(service_url + '/cvx/CVXtractorService.wsdl')
   hrxml_profile  = daxtra_soap_client.service.ProcessCV(document_url=b64encode(filecontent), 
                                                         account=service_account)
   return hrxml_profile

where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- string containing XML/JSON with structured fields or error
where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- string containing XML/JSON with structured fields or errorwhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- string containing XML/JSON with structured fields or erroroù
  service_url     -- chaîne -- URL d'un serveur DaXtra (pas le chemin complet à wsdl, seulement le nom du serveur ou IP)
  service_account -- chaîne -- votre nom d'utilisateur, que DaXtra vous a donné
  file_to_process -- chaîne -- chemin d'accès complet d'un dossier que vous voulez traiter

  hrxml_profile -- chaîne qui contient des champs structurées en format JSON ou XML, ou erreurwhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- string containing XML/JSON with structured fields or error

Perl Integration using SOAP

Perl Integration using SOAP

通过SOAP实现的Perl集成

Intégration de Perl utilisant SOAP

Perl Integration using SOAP

use SOAP::Lite; 
use XML::LibXML;

sub processCV{
  my $service_url = shift @_;
  my $account = shift @_;
  my $file_name = shift @_;

  my $process_file = read_bin_file($file_name);
  my $client = createSOAPclient($service_url);   
  my $result = $client->ProcessCV($process_file, $account);
  my $output;
#-- valid XML return#-- valid XML return#-- valid XML return#-- retour d'XML valide#-- valid XML return  if($result =~ %^<%) 
  {
     my $xml_parser = XML::LibXML->new;
     my $envelope_dom =  $xml_parser->parse_string($result);
     for my $hrxml_node ( $envelope_dom->findnodes("//s0:hrxml") )
     {
        return $hrxml_node->textContent;
     }
  }
  else { 
#-- HTTP error#-- HTTP error#-- HTTP error#-- erreur d'HTTP#-- HTTP error     return $result;
  }
 
  return;
}

sub createSOAPclient {
  my $service_url = shift @_;

  my $client = SOAP::Lite
    ->service("http://$service_url/cvx/CVXtractorService_compatibility.wsdl")

  return $client;
}

use Fcntl;
sub read_bin_file 
{
  my $filename = shift @_;

  my $sstring;
  my $ed_length = -s $filename;
  sysopen(BINDAT, $filename, O_RDONLY | O_BINARY);
  sysread(BINDAT, $sstring, $ed_length); #+1024);
  close(BINDAT);

  return $sstring;   
}

REST Response data - Error Handling
• 400 - [application/json text/xml] - bad request arguments; with additional CSERROR error message in JSON or XML format (codes: 1,2,3,4)
• 403 - [application/json text/xml] - authorization failed; with additional CSERROR error message in JSON or XML format (codes: 10,11,12,14)
• 404 - [application/json text/xml] - Not Found; with additional CSERROR error message in JSON or XML format (codes: 23)
• 422 - [application/json text/xml] - Error at Request Execution; with additional CSERROR error message in JSON or XML format (codes: 20,22,31,602,603,604)
• 500 - [application/json text/xml] - Internal Server Error; with additional CSERROR error message in JSON or XML format (codes: 16)

REST Response data - Error Handling
• 400 - [application/json text/xml] - bad request arguments; with additional CSERROR error message in JSON or XML format (codes: 1,2,3,4)
• 403 - [application/json text/xml] - authorization failed; with additional CSERROR error message in JSON or XML format (codes: 10,11,12,14)
• 404 - [application/json text/xml] - Not Found; with additional CSERROR error message in JSON or XML format (codes: 23)
• 422 - [application/json text/xml] - Error at Request Execution; with additional CSERROR error message in JSON or XML format (codes: 20,22,31,602,603,604)
• 500 - [application/json text/xml] - Internal Server Error; with additional CSERROR error message in JSON or XML format (codes: 16)

响应数据 - 错误处理

• 400 - [application/json text/xml] - 错误请求变量；并和CSERROR错误信息一起以JSON或XML格式返回。（错误代码：1,2,3,4）
• 403 - [application/json text/xml] - 授权失败；并和CSERROR错误信息一起以JSON或XML格式返回。（错误代码：10,11,12,14）
• 404 - [application/json text/xml] - 未找到服务器；并和CSERROR错误信息一起以JSON或XML格式返回。（错误代码：23）
• 422 - [application/json text/xml] - 请求执行错误；并和CSERROR错误信息一起以JSON或XML格式返回。（错误代码：20,22,31,602,603,604）
• 500 - [application/json text/xml] - 内部服务器错误；并和CSERROR错误信息一起以JSON或XML格式返回。（错误代码：16）

Données de réponse REST - Traitement d'erreurs
• 400 - [application/json text/xml] - mauvais arguments de demande; avec CSERROR message d'erreur supplémentaire en format JSON ou XML (codes: 1,2,3,4)
• 403 - [application/json text/xml] - autorisation ratée; avec CSERROR message d'erreur supplémentaire en format JSON ou XML (codes: 10,11,12,14)
• 404 - [application/json text/xml] - pas trouvé; avec CSERROR message d'erreur supplémentaire en format JSON ou XML (codes: 23)
• 422 - [application/json text/xml] - erreur à l'exécution de la demande; avec CSERROR message d'erreur supplémentaire en format JSON ou XML (codes: 20,22,31,602,603,604)
• 500 - [application/json text/xml] - erreur interne du serveur; avec CSERROR message d'erreur supplémentaire en format JSON ou XML (codes: 16)

REST Antwortdata - Fehlerbehandlung
• 400 - [application/json text/xml] - bad request arguments; with additional CSERROR error message in JSON or XML format (codes: 1,2,3,4)
• 403 - [application/json text/xml] - authorization failed; with additional CSERROR error message in JSON or XML format (codes: 10,11,12,14)
• 404 - [application/json text/xml] - Not Found; with additional CSERROR error message in JSON or XML format (codes: 23)
• 422 - [application/json text/xml] - Error at Request Execution; with additional CSERROR error message in JSON or XML format (codes: 20,22,31,602,603,604)
• 500 - [application/json text/xml] - Internal Server Error; with additional CSERROR error message in JSON or XML format (codes: 16)

Ruby on Rails Integration using SOAP

Ruby on Rails Integration using SOAP

通过SOAP实现的Ruby on Rails集成

Intégration avec Ruby on Rails utilisant SOAP

Ruby on Rails Integration using SOAP

Integration with Ruby on Rails can be implemented through calls to the CVX SOAP server. One of the best Ruby SOAP clients is Savon. Savon version 2 is available from RubyGems and can be installed using:

Integration with Ruby on Rails can be implemented through calls to the CVX SOAP server. One of the best Ruby SOAP clients is Savon. Savon version 2 is available from RubyGems and can be installed using:

Ruby on Rails的集成可以通过对CVX SOAP服务器的调用实现。Savon是最好的Ruby SOAP客户端之一。 Savon 2 可以用以下命令通过RubyGems安装：

Intégration avec Ruby on Rails peut être implémentée à travers des appels au serveur de CVX SOAP. Un des meilleurs clients de Ruby SOAP est Savon. Vous pouvez obtenir la version 2 de Savon auprès de RubyGems, et vous pouvez l'installer avec:

Integration with Ruby on Rails can be implemented through calls to CVX SOAP server. One of the best Ruby SOAP clients is Savon. Savon version 2 is available from RubyGems and can be installed using:

$ gem install savon

After Savon is installed you will need to create a DaxtraParser class as below. For web applications you will normally put it into an "app/models/daxtra_parser.rb" file.

After Savon is installed you will need to create a DaxtraParser class as below. For web applications you will normally put it into an "app/models/daxtra_parser.rb" file.

在成功安装Savon之后，你需要创建如下的DaxtraParser类。对于web应用你通常需要把他放在“app/models/daxtra_parser.rb”文件中

Après avoir installé Savon, vous devrez créer une classe de DaxtraParser comme ci-dessous. Pour des applications web vous la mettrez normalement dans un ficher "app/models/daxtra_parser.rb"

After Savon is installed you will need to create DaxtraParser class as below. For web applications you will normally put it into an "app/models/daxtra_parser.rb" file.

require 'base64'
require 'savon' 

class  DaxtraParser
  def initialize(service_url, service_account) 
    @ACCOUNT = service_account
    @client = Savon::Client.new(wsdl: service_url + "/cvx/CVXtractorService.wsdl")
  end

  def parse_file(file_to_process)
    content = File.binread(file_to_process)
    encoded = Base64.encode64(content)
    response = @client.call(:process_cv, message: { "document_url" => encoded, "account" => @ACCOUNT })
    response.body[:process_cv_response][:hrxml]
  end
 
end 

Now you can use DaxtraParser objects in your Ruby programs:

Now you can use DaxtraParser objects in your Ruby programs:

之后你就可以在你的ruby程序中使用DaxtraParser对象。

Maintenant vous pouvez utiliser des objets de DaxtraParser dans vos programmes Ruby:

Now you can use DaxtraParser objects in your Ruby programs:

 parser  = DaxtraParser.new(service_url, service_account);
 hrxml_profile = parser.parse_file(file_to_process)

where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- string containing XML/JSON with structured fields or error

 parser  = DaxtraParser.new(service_url, service_account);
 hrxml_profile = parser.parse_file(file_to_process)

where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- string containing XML/JSON with structured fields or error

 parser  = DaxtraParser.new(service_url, service_account);
 hrxml_profile = parser.parse_file(file_to_process)

where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- string containing XML/JSON with structured fields or error

 parser  = DaxtraParser.new(service_url, service_account);
 hrxml_profile = parser.parse_file(file_to_process)

où
  service_url     -- chaîne -- URL d'un serveur DaXtra (pas le chemin complet à wsdl, seulement le nom du serveur ou IP)
  service_account -- chaîne -- votre nom d'utilisateur, que DaXtra vous a donné
  file_to_process -- chaîne -- chemin d'accès complet d'un dossier que vous voulez traiter

  hrxml_profile -- chaîne qui contient des champs structurées en format JSON ou XML, ou erreur

 parser  = DaxtraParser.new(service_url, service_account);
 hrxml_profile = parser.parse_file(file_to_process)

where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- string containing XML/JSON with structured fields or error

PHP Integration using SOAP

PHP Integration using SOAP

通过SOAP实现的PHP集成

Intégration de PHP utilisant SOAP

PHP Integration using SOAP

PHP v5 and above has a SoapClient class. Below is an example of a SOAP call from PHP:

PHP v5 and above has a SoapClient class. Below is an example of a SOAP call from PHP:

PHP v5 和之后的版本包含SoapClient类。如下为在PHP中的SOAP调用示例：

PHP v5 et au dessus a une classe SoapClient. Ci-dessous se trouve un exemple d'un appel SOAP de PHP:

PHP v5 and above has a SoapClient class. Below is an example of a SOAP call from PHP:

<?php
function processCV($service_url, $service_account, $file_to_process )
{
  $client = new SoapClient("$service_url/cvx/CVXtractorService.wsdl");
  $handle = fopen($file_to_process , "r");
  $fileContents = fread($handle, filesize($file_to_process));
  fclose($handle);
  $response = $client->ProcessCV(array('document_url' =>  base64_encode($fileContents), 
                                            'account' => $service_account));
  $hrxml_profile = simplexml_load_string($response->hrxml);
  return $hrxml_profile;
?>

where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- XML/JSON object with structured fields or error
where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- XML/JSON object with structured fields or errorwhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- XML/JSON object with structured fields or erroroù
  service_url     -- chaîne -- URL d'un serveur DaXtra (pas le chemin complet à wsdl, seulement le nom du serveur ou IP)
  service_account -- chaîne -- votre nom d'utilisateur, que DaXtra vous a donné
  file_to_process -- chaîne -- chemin d'accès complet d'un dossier que vous voulez traiter

  hrxml_profile -- objet XML/JSON avec une représentation structurée ou erreurwhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- XML/JSON object with structured fields or error

For more details see the SOAP section.

For more details see the SOAP section.

更多信息详见SOAP集成页面

Pour plus de détails voir la section de SOAP.

For more details see the SOAP section.

To speed up delivery of information to the user you also can process a resume in two phases. In the first phase the ProcessCVphase1 SOAP call extracts only personal and contact data which is in general 50% faster than extraction of the full profile. Together with the HR-XML profile it returns a phase2_token which can be used by immediately calling ProcessCVphase2 to fetch the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

To speed up delivery of information to the user you also can process a resume in two phases. In the first phase the ProcessCVphase1 SOAP call extracts only personal and contact data which is in general 50% faster than extraction of the full profile. Together with the HR-XML profile it returns a phase2_token which can be used by immediately calling ProcessCVphase2 to fetch the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

你可以通过两个步骤处理简历的方式提高获取信息的速度。在第一步解析中ProcessCVphase1调用只获取个人信息和联系方式，单独执行此步骤通常比完整解析快50%。再通过第一步返回的phase2_token调用ProcessCVphase2获取完整解析的简历。"ProcessCVphase2"应该在"ProcessCVphase1"之后马上被执行。

Pour accélérer la livraison d'informations à l'utilisateur, vous pouvez également exécuter un appel en deux phases. Dans la première étape, l'appel SOAP ProcessCVphase1 n'extrait que les données personnelles et les coordonnées, qui est normalement 50% plus rapide que l'extraction du profil complet. Conjointement avec le profil HR-XML cela retourne un phase2_token, qui peut être utilisé pour appeler immédiatement ProcessCVphase2 pour récupérer le profil en entier. L'appel ProcessCVphase2 doit être entré aussi vite que possible après l'appel ProcessCVphase1.

To speed up delivery of information to the user You also can process a resume in two phases. In the first phase the ProcessCVphase1 SOAP call extracts only personal and contact data which is in general 50% faster than extraction of the full profile. Together with the HR-XML profile it returns a phase2_token which can be used by immediately calling ProcessCVphase2 to fetch the full profile. The ProcessCVphase2 call should be made as soon as possible after the ProcessCVphase1 call.

<?php
function processCV2($service_url, $service_account, $file_to_process )
{
  $client = new SoapClient("$service_url/cvx/CVXtractorService.wsdl");
  $handle = fopen($file_to_process , "r");
  $fileContents = fread($handle, filesize($file_to_process));
  fclose($handle);
  $response = $client->ProcessCVphase1(array('document_url' =>  base64_encode($fileContents), 
                                            'account' => $service_account));
  $hrxml_profile_pers_only = simplexml_load_string($response->hrxml);
  #-- !!! do something useful with $hrxml_profile_pers_only!!!  #-- !!! do something useful with $hrxml_profile_pers_only!!!  #-- !!! do something useful with $hrxml_profile_pers_only!!!  #-- !!! faîtes quelque chose d'utile avec $hrxml_profile_pers_only!!!  #-- !!! do something useful with $hrxml_profile_pers_only!!!  $response = $client->ProcessCVphase2(array('phase2_token'  => $response->phase2_token),
                                             'account' => $service_account));
  $hrxml_profile = simplexml_load_string($response->hrxml);
  return $hrxml_profile;
?>

where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- XML/JSON object with structured fields or error
where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- XML/JSON object with structured fields or errorwhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- XML/JSON object with structured fields or erroroù
  service_url     -- chaîne -- URL d'un serveur DaXtra (pas le chemin complet à wsdl, seulement le nom du serveur ou IP)
  service_account -- chaîne -- votre nom d'utilisateur, que DaXtra vous a donné
  file_to_process -- chaîne -- chemin d'accès complet d'un dossier que vous voulez traiter

  hrxml_profile -- objet XML/JSON avec une représentation structurée ou erreurwhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process

  hrxml_profile -- XML/JSON object with structured fields or error

To process a number of files in batch mode you can use a ProcessBatch call:

To process a number of files in batch mode you can use a ProcessBatch call:

你可以通过ProcessBatch调用以批处理模式处理多个文件。

Pour traiter plusieurs fichiers en mode batch vous pouvez utiliser un appel ProcessBatch:

To process a number of files in batch mode you can use a ProcessBatch call:

<?php
function processBatch($service_url, $service_account, $file_to_process )
{
  $client = new SoapClient("$service_url/cvx/CVXtractorService.wsdl");
  $handle = fopen($file_to_process , "r");
  $fileContents = fread($handle, filesize($file_to_process));
  fclose($handle);
  $response = $client->ProcessBatch(array('document_url' =>  base64_encode($fileContents), 
                                            'account' => $service_account));
//-- token for this batch processing://-- token for this batch processing://-- token for this batch processing://-- token de ce traitement par lots://-- token for this batch processing:  $batch_token = $response->process_token;
  $ret_array = array();
  for ($x = 0; $x <= 1000; $x++) {
//-- wait some time for processing to continue://-- wait some time for processing to continue://-- wait some time for processing to continue://-- attendre quelque temps pour que le traitement soit fini://-- wait some time for processing to continue:      sleep(3); 
//-- call on the process to retrieve available results://-- call on the process to retrieve available results://-- call on the process to retrieve available results://-- appel au traitement pour récupérer les résultats disponibles://-- call on the process to retrieve available results:      $response = $client->ProcessBatch(array('document_url' => $batch_token, 
                                              'account' => $service_account));
//-- save Base64-encoded ZIP of results if it was returned in this call://-- save Base64-encoded ZIP of results if it was returned in this call://-- save Base64-encoded ZIP of results if it was returned in this call://-- enregistrer le ZIP encodé en Base64 de résultats si cet appel l'a retourné://-- save Base64-encoded ZIP of results if it was returned in this call:      $result = $response->Results; 
      if(!empty($result)) {
         $result_file = $file_to_process . "_" . $x . ".zip";
         $res_handle = fopen($result_file , "w");
         fwrite($res_handle, base64_decode($result));
         fclose($res_handle);
         array_push($ret_array, $result_file);
      }
//-- check whether processing is still going on (if so, the returned token is the same as the original)://-- check whether processing is still going on (if so, the returned token is the same as the original)://-- check whether processing is still going on (if so, the returned token is the same as the original)://-- vérifie si le traitement est toujours en cours (si oui, le token retourné est le même que l'original)://-- check whether processing is still going on (if so, the returned token is the same as the original):      $this_token =  $response->process_token;
      if($this_token <> $batch_token) { 
         $x = 1000;
         $fh_stderr = fopen('php://stderr','a');
         fwrite($fh_stderr, "Processing finished with message: " . $this_token);
         fclose($fh_stderr);
      }
  }
  return $ret_array;
}
?>

where 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process (usually an archive of files - ZIP, RAR, tar)

  ret_array  -- array of filenames of ZIP files with resultswhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process (usually an archive of files - ZIP, RAR, tar)

  ret_array  -- array of filenames of ZIP files with resultswhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process (usually an archive of files - ZIP, RAR, tar)

  ret_array  -- array of filenames of ZIP files with resultsoù
  service_url     -- chaîne -- URL d'un serveur DaXtra (pas le chemin complet à wsdl, seulement le nom du serveur ou IP)
  service_account -- chaîne -- votre nom d'utilisateur, que DaXtra vous a donné
  file_to_process -- chaîne -- chemin d'accès complet d'un dossier que vous voulez traiter (d'habitude une archive de documents - ZIP, RAR, tar)

  ret_array  -- tableau de noms de fichiers ZIP avec résultatswhere 
  service_url     -- string -- URL of a DaXtra Server (not the full path to wsdl - just server name or IP) 
  service_account -- string -- your user name allocated to you by DaXtra
  file_to_process -- string -- full path to a file you want to process (usually an archive of files - ZIP, RAR, tar)

  ret_array  -- array of filenames of ZIP files with results

For more details see the SOAP section.

For more details see the SOAP section.

更多信息详见SOAP集成页面

Pour plus de détails voir la section de SOAP.

For more details see the SOAP section.

When an error occurs then instead of a string containing a "Resume" element DaXtra Parser returns a CSERROR element:

When an error occurs then instead of a string containing a "Resume" element DaXtra Parser returns a CSERROR element:

When an error occurs then instead of a string containing a "Resume" element DaXtra Parser returns a CSERROR element:

S'il y a une erreur, au lieu d'une chaîne qui contient un élément «CV», le DaXtra Parser retourne un élément CSERROR:

When an error occurs then instead of a string containing a "Resume" element DaXtra Parser returns a CSERROR element:

{nnn
  CSERROR: {
    messsage: "error description",
    code: error_code
  }
}

or

or

or

ou

oder

<CSERROR code='error_code'>error description</CSERROR>

Error codes

Error codes

Error codes

Codes d'erreur

Error codes

• 1 - account has no permission to use this server [ALL CALLS]
• 1 - account has no permission to use this server [ALL CALLS]
• 1 - account has no permission to use this server [ALL CALLS]
• 1 - le compte n'est pas autorisé à utiliser ce serveur [ALL CALLS]
• 1 - account has no permission to use this server [ALL CALLS]
• 2 - account has expired on this server [ALL CALLS]
• 2 - account has expired on this server [ALL CALLS]
• 2 - account has expired on this server [ALL CALLS]
• 2 - le compte a expiré sur ce serveur [ALL CALLS]
• 2 - account has expired on this server [ALL CALLS]
• 3 - account does not have credentials for the requested operation [ALL CALLS]
• 3 - account does not have credentials for the requested operation [ALL CALLS]
• 3 - account does not have credentials for the requested operation [ALL CALLS]
• 3 - le compte n'a pas les informations d'identification pour l'opération demandée [ALL CALLS]
• 3 - account does not have credentials for the requested operation [ALL CALLS]
• 4 - credentials for the account are not set on the server [ALL CALLS]
• 4 - credentials for the account are not set on the server [ALL CALLS]
• 4 - credentials for the account are not set on the server [ALL CALLS]
• 4 - les informations d'identification pour ce compte ne sont pas définies sur ce serveur [ALL CALLS]
• 4 - credentials for the account are not set on the server [ALL CALLS]
• 10 - incorrect call arguments: account needs to be specified / document needs to be specified [ALL CALLS]
• 10 - incorrect call arguments: account needs to be specified / document needs to be specified [ALL CALLS]
• 10 - incorrect call arguments: account needs to be specified / document needs to be specified [ALL CALLS]
• 10 - arguments d'appel incorrects: il faut préciser le compte / il faut préciser le fichier [ALL CALLS]
• 10 - incorrect call arguments: account needs to be specified / document needs to be specified [ALL CALLS]
• 11 - corrupted access token [ALL CALLS]
• 11 - corrupted access token [ALL CALLS]
• 11 - corrupted access token [ALL CALLS]
• 11 - jeton d'accès endommagé [ALL CALLS]
• 11 - corrupted access token [ALL CALLS]
• 12 - could not read transferred document [ALL CALLS]
• 12 - could not read transferred document [ALL CALLS]
• 12 - could not read transferred document [ALL CALLS]
• 12 - ne pouvait pas lire le fichier transféré [ALL CALLS]
• 12 - could not read transferred document [ALL CALLS]
• 14 - incorrect structure of passed argument [ALL CALLS]
• 14 - incorrect structure of passed argument [ALL CALLS]
• 14 - incorrect structure of passed argument [ALL CALLS]
• 14 - structure incorrect d'argument passé [ALL CALLS]
• 14 - incorrect structure of passed argument [ALL CALLS]
• 16 - could not load required modules [ALL CALLS]
• 16 - could not load required modules [ALL CALLS]
• 16 - could not load required modules [ALL CALLS]
• 16 - ne pouvait pas charger les modules nécessaires [ALL CALLS]
• 16 - could not load required modules [ALL CALLS]
• 20 - error at document extraction [ALL CALLS]
• 20 - error at document extraction [ALL CALLS]
• 20 - error at document extraction [ALL CALLS]
• 20 - erreur en extrayant le fichier [ALL CALLS]
• 20 - error at document extraction [ALL CALLS]
• 21 - failed to generate secure access token [ALL CALLS]
• 21 - failed to generate secure access token [ALL CALLS]
• 21 - failed to generate secure access token [ALL CALLS]
• 21 - ne pouvait pas créer un jeton d'accès sécurisé [ALL CALLS]
• 21 - failed to generate secure access token [ALL CALLS]
• 22 - no result produced by ProcessCVphase2 [ProcessCVphase2]
• 22 - no result produced by ProcessCVphase2 [ProcessCVphase2]
• 22 - no result produced by ProcessCVphase2 [ProcessCVphase2]
• 22 - pas de résultat produit par ProcessCVphase2 [ProcessCVphase2]
• 22 - no result produced by ProcessCVphase2 [ProcessCVphase2]
• 31 - error at document format conversion [PDF2Word, ReformatCV]
• 31 - error at document format conversion [PDF2Word, ReformatCV]
• 31 - error at document format conversion [PDF2Word, ReformatCV]
• 31 - erreur de conversion de format du fichier [PDF2Word, ReformatCV]
• 31 - error at document format conversion [PDF2Word, ReformatCV]
• 429 - too many requests. Server is too busy [ALL CALLS]
• 429 - too many requests. Server is too busy [ALL CALLS]
• 429 - too many requests. Server is too busy [ALL CALLS]
• 429 - trop de demandes. Le serveur est occupé [ALL CALLS]
• 429 - too many requests. Server is too busy [ALL CALLS]
• 602 - account already exists [CreateAccount]
• 602 - account already exists [CreateAccount]
• 602 - account already exists [CreateAccount]
• 602 - le compte existe déjà [CreateAccount]
• 602 - account already exists [CreateAccount]
• 603 - could not create directory for new account [CreateAccount]
• 603 - could not create directory for new account [CreateAccount]
• 603 - could not create directory for new account [CreateAccount]
• 603 - ne pouvait pas créer un répertoire pour le nouveau compte [CreateAccount]
• 603 - could not create directory for new account [CreateAccount]
• 604 - could not create required account files [CreateAccount]
• 604 - could not create required account files [CreateAccount]
• 604 - could not create required account files [CreateAccount]
• 604 - ne pouvait pas créer les fichiers nécessaires pour le compte [CreateAccount]
• 604 - could not create required account files [CreateAccount]
• 777 - misc error
• 777 - misc error
• 777 - misc error
• 777 - erreur divers
• 777 - misc error

Account ID and Secure Token

Account ID and Secure Token

用户账号和安全口令

ID de Compte et Secure Token

Konto-ID und Secure Token

The Account ID is allocated to you by DaXtra. You will need to pass it with every call to your DaXtra Server.

The Account ID is allocated to you by DaXtra. You will need to pass it with every call to your DaXtra Server.

用户账号（Account ID）是德士达给用户分配的账号，你需要在每次向德士达服务器的调用中传递这个变量

L'ID de Compte vous est donné par DaXtra. Vous devrez le passer avec tout appel au serveur de DaXtra.

The Account ID is allocated to you by DaXtra. You will need to pass it with every call to your DaXtra Server.

In a public environment when you do not want to expose your Account ID you can use a Secure Token instead. You can either obtain a Secure Token from your DaXtra server or you can generate a Secure Token yourself using the password provided by DaXtra.

In a public environment when you do not want to expose your Account ID you can use a Secure Token instead. You can either obtain a Secure Token from your DaXtra server or you can generate a Secure Token yourself using the password provided by DaXtra.

在公用环境中，可以通过使用安全口令（Secure Token）来代替用户账号避免用户账号直接显示。

Dans un environnement public où vous ne voulez pas exposer votre ID de compte, vous pouvez plutôt utiliser un Secure Token. Ou vous pouvez obtenir un Secure Token de votre serveur de DaXtra, ou vous pouvez générer un Secure Token vous-même, en utilisant le mot de passe que DaXtra vous a donné.

In a public environment when you do not want to expose your Account ID you can use a Secure Token instead. You can either obtain a Secure Token from your DaXtra server or you can generate a Secure Token yourself using password provided by DaXtra.

To obtain a Secure Token from your DaXtra server you will need to issue an HTTP (we recommend using https) GET request /cvx/rest/auth/v1/access_token and pass through your Account ID in the account parameter. For instance:

To obtain a Secure Token from your DaXtra server you will need to issue an HTTP (we recommend to use https) GET request /cvx/rest/auth/v1/access_token and pass through your Account ID in the account parameter. For instance:

在向德士达服务器申请安全口令时，你需要向服务器发送HTTP（建议使用https）GET请求/cvx/rest/auth/v1/access_token 并在account变量中提交你的Account ID。示例如下：

Pour obtenir un Secure Token de votre serveur de DaXtra server vous devrez effectuer une demande de GET /cvx/rest/auth/v1/access_token en HTTP (nous vous recommandons https) et le passer votre ID de compte dans le paramètre account. Par exemple:

To obtain a Secure Token from your DaXtra server you will need to issue an HTTP (we recommend to use https) GET request /cvx/rest/auth/v1/access_token and pass through your Account ID in the account parameter. For instance:

curl --request GET "https://DAXTRA_SERVER/cvx/rest/auth/v1/access_token?account=ACCOUNT_ID"

where 
  DAXTRA_SERVER - URL (name or IP) of your DaXtra Server
  ACCOUNT_ID - as described above. Please note that ACCOUNT_ID might need to be URL-escaped if it contains white-space, punctuation or non-ASCII characters.

response
  secure_token - an encrypted and Base64-encoded string which you can use instead of your ACCOUNT_ID for one single request to DaXtra Parser

curl --request GET "https://DAXTRA_SERVER/cvx/rest/auth/v1/access_token?account=ACCOUNT_ID"

where 
  DAXTRA_SERVER - URL (name or IP) of your DaXtra Server
  ACCOUNT_ID - as described above. Please note that ACCOUNT_ID might need to be URL-escaped if it contains white-space, punctuation or non-ASCII characters.

response
  secure_token - an encrypted and Base64-encoded string which you can use instead of your ACCOUNT_ID for one single request to DaXtra Parser

curl --request GET "https://DAXTRA_SERVER/cvx/rest/auth/v1/access_token?account=ACCOUNT_ID"

where 
  DAXTRA_SERVER - URL (name or IP) of your DaXtra Server
  ACCOUNT_ID - as described above. Please note that ACCOUNT_ID might need to be URL-escaped if it contains white-space, punctuation or non-ASCII characters.

response
  secure_token - an encrypted and Base64-encoded string which you can use instead of your ACCOUNT_ID for one single request to DaXtra Parser

curl --request GET "https://DAXTRA_SERVER/cvx/rest/auth/v1/access_token?account=ACCOUNT_ID"

où
  DAXTRA_SERVER - URL (nom ou IP) de votre serveur de DaXtra
  ACCOUNT_ID - comme décrit ci-dessus. Veuillez noter qu'il faudra faire un échappement d'URL d'ACCOUNT_ID s'il contient de l'espace blanc, de la ponctuation ou des caractères non-ASCII

réponse
  secure_token - une chaîne encodée en Base64, que vous pouvez utiliser au lieu de votre ACCOUNT_ID pour une seule demande à DaXtra Parser

curl --request GET "https://DAXTRA_SERVER/cvx/rest/auth/v1/access_token?account=ACCOUNT_ID"

where 
  DAXTRA_SERVER - URL (name or IP) of your DaXtra Server
  ACCOUNT_ID - as described above. Please note that ACCOUNT_ID might need to be URL-escaped if it contains white-space, punctuation or non-ASCII characters.

response
  secure_token - an encrypted and Base64-encoded string which you can use instead of your ACCOUNT_ID for one single request to DaXtra Parser

You can also generate a Secure Token yourself without doing an extra call to a DaXtra Server.

You can also generate a Secure Token yourself without doing an extra call to a DaXtra Server.

你也可以自己生成安全口令而不向德士达服务器发送安全口令申请的调用

Vous pouvez également créer un Secure Token vous-même sans faire un appel supplémentaire à un DaXtra Server.

You can also generate a Secure Token yourself without doing an extra call to a DaXtra Server.

1. First you will need to create a processing certificate in XML or JSON as follows:

1. First you will need to create a processing certificate in XML or JSON as follows:

1. 首先你需要创建如下XML或json格式的处理证书

1. D'abord vous devrez créer un certificat de processus en XML ou JSON comme ci-dessous:

1. First you will need to create a processing certificate in XML or JSON as follows:

<DXCert><account>ACCOUNT_ID</account><granted>TIMESTAMP</granted><period>SECONDS</period></DXCert>
or
{"account":"ACCOUNT_ID", "granted":"TIMESTAMP", "period":"SECONDS" }

where
  ACCOUNT_ID - your Account ID
  TIMESTAMP - timestamp of the creation of your certificate in GMT time,
                  either a UNIX Epoch (POSIX) timestamp e.g. 1457006570,
                  or in ISO-8601 format: YYYY-MM-DDTHH:MM:SS e.g. 2016-03-03T12:02:50
  SECONDS - number of seconds for which your certificate is valid

<DXCert><account>ACCOUNT_ID</account><granted>TIMESTAMP</granted><period>SECONDS</period></DXCert>
or
{"account":"ACCOUNT_ID", "granted":"TIMESTAMP", "period":"SECONDS" }

where
  ACCOUNT_ID - your Account ID
  TIMESTAMP - timestamp of the creation of your certificate in GMT time, either a
                  UNIX Epoch (POSIX) timestamp e.g. 1457006570,
                  or in ISO-8601 format: YYYY-MM-DDTHH:MM:SS p. ex. 2016-03-03T12:02:50
  SECONDS - number of seconds for which your certificate is valid

<DXCert><account>ACCOUNT_ID</account><granted>TIMESTAMP</granted><period>SECONDS</period></DXCert>
or
{"account":"ACCOUNT_ID", "granted":"TIMESTAMP", "period":"SECONDS" }

where
  ACCOUNT_ID - your Account ID
  TIMESTAMP - timestamp of the creation of your certificate in GMT time,
                  either a UNIX Epoch (POSIX) timestamp, e.g. 1457006570,
                  or in ISO-8601 format: YYYY-MM-DDTHH:MM:SS e.g. 2016-03-03T12:02:50
  SECONDS - number of seconds for which your certificate is valid

<DXCert><account>ACCOUNT_ID</account><granted>TIMESTAMP</granted><period>SECONDS</period></DXCert>
ou
{"account":"ACCOUNT_ID", "granted":"TIMESTAMP", "period":"SECONDS" }

où
  ACCOUNT_ID - votre ID de Compte
  TIMESTAMP - horodatage de votre création du certificat en heure GMT,
                  ou en heure POSIX p. ex. 1457006570,
                  ou en format ISO-8601: YYYY-MM-DDTHH:MM:SS e.g. 2016-03-03T12:02:50
  SECONDS - nombre de secondes pour lesquelles votre certificat est valide

<DXCert><account>ACCOUNT_ID</account><granted>TIMESTAMP</granted><period>SECONDS</period></DXCert>
or
{"account":"ACCOUNT_ID", "granted":"TIMESTAMP", "period":"SECONDS" }

where
  ACCOUNT_ID - your Account ID
  TIMESTAMP - timestamp of the creation of your certificate in GMT time, either a
                  UNIX Epoch (POSIX) timestamp, e.g. 1457006570,
                  or in ISO-8601 format: YYYY-MM-DDTHH:MM:SS e.g. 2016-03-03T12:02:50
  SECONDS - number of seconds for which your certificate is valid

2. Then you will need to create HMAC for your certificate (hmac_certificate) (as described here) using an SHA256 hash function (blocksize=64) and your password (provided by DaXtra):

2. Then you will need to create HMAC for your certificate (hmac_certificate) (as described here) using an SHA256 hash function (blocksize=64) and your password (provided by DaXtra):

2. 然后你需要使用SHA256哈希函数（blocksize=64）（相关描述）和你的密码（由德士达提供）为你的证书（hmac_certificate）创建一个HMAC。

2. Puis vous devrez créer HMAC pour votre certificat (hmac_certificate) (comme décrit ici) en utilisant une fonction de hachage SHA256 (blocksize=64) et votre mot de passe (que DaXtra vous a donné):

2. then you will need to create HMAC for your certificate (hmac_certificate) (as described here) using an SHA256 hash function (blocksize=64) and your password (provided by DaXtra):

function hmac (password, certificate)
    blocksize=64
    // zero-padd password to the size of blocksize (64)    // zero-padd password to the size of blocksize (64)    // zero-padd password to the size of blocksize (64)    // zero-padd le mot de passe à la taille du bloc (64)    // zero-padd password to the size of blocksize (64)    if (length(password) < blocksize) then
        password = password « [0x00 * (blocksize - length(key))] 
    end if
   
    o_key_pad = [0x5c * blocksize] XOR  password 
    i_key_pad = [0x36 * blocksize] XOR  password
   
    return SHA256(o_key_pad « SHA256(i_key_pad « certificate)) 
end function

where
  « means concatenationwhere
  « means concatenation  « means concatenationoù
  « veut dire concaténationwhere
  « means concatenation

3. Your Secure Token then can be composed as a Base64-encoded certificate and a Base64-encoded HMAC of your certificate separated by a dot (.). (Make sure that there are no newlines in the Base64 encoding).

3. Your Secure Token then can be composed as a Base64-encoded certificate and a Base64-encoded HMAC of your certificate separated by a dot (.). (Make sure that there are no newlines in the Base64 encoding).

3. 在之后的调用中，安全口令就可以写作以点（.）分隔的base64编码的证书和base64编码的证书的hmac。（请确保在base64编码的序列中没有换行符）

3. Votre Secure Token peut donc être composé comme un certificat encodé en Base64, et un HMAC de votre certificat encodé en Base64, séparés par un point(.). (Vérifiez qu'il n'y a pas de nouvelles lignes dans l'encodage Base64).

3. Your Secure Token then can be composed as Base64-encoded certificate and Base64-encoded hmac of your certificate separated by a dot (.). (Make sure that there are no newlines in the Base64 encoding).

BASE64(certificate)  « . « BASE64(hmac_certificate)

for the certificate:
  <DXCert><granted>2016-4-14T19:49:58</granted><period>60</period><account>MY_ACCOUNT</account></DXCert>

the BASE64(certificate) is:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+

the actual BASE64(hmac_certificate) generated with password "MY_PASSWORD" is:
  LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

full secure token:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+.LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

BASE64(certificate)  « . « BASE64(hmac_certificate)

for the certificate:
  <DXCert><granted>2016-4-14T19:49:58</granted><period>60</period><account>MY_ACCOUNT</account></DXCert>

the BASE64(certificate) is:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+

the actual BASE64(hmac_certificate) generated with password "MY_PASSWORD" is:
  LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

full secure token:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+.LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

the BASE64(certificate)  « . « BASE64(hmac_certificate):

for the certificate:
  <DXCert><granted>2016-4-14T19:49:58</granted><period>60</period><account>MY_ACCOUNT</account></DXCert>

the BASE64(certificate) is:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+

the actual BASE64(hmac_certificate) generated with password "MY_PASSWORD" is:
  LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

full secure token:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+.LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

BASE64(certificate)  « . « BASE64(hmac_certificate)

pour le certificat:
  <DXCert><granted>2016-4-14T19:49:58</granted><period>60</period><account>MY_ACCOUNT</account></DXCert>

le BASE64(certificate) est:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+

le BASE64(hmac_certificate) créé avec le mot de passe "MY_PASSWORD" est:
  LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

Secure Token complet:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+.LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

the BASE64(certificate)  « . « BASE64(hmac_certificate):

for Certificate:
  <DXCert><granted>2016-4-14T19:49:58</granted><period>60</period><account>MY_ACCOUNT</account></DXCert>

the BASE164(certificate) is:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+

the actual BASE64(hmac_certificate) generated with password "MY_PASSWORD" is:
  LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

full secure token:
  PERYQ2VydD48Z3JhbnRlZD4yMDE2LTQtMTRUMTk6NDk6NTg8L2dyYW50ZWQ+PHBlcmlvZD42MDwvcGVyaW9kPjxhY2NvdW50Pk1ZX0FDQ09VTlQ8L2FjY291bnQ+PC9EWENlcnQ+.LwxjR2neLanintE+d992Qig2crKl7vRSxyhdZUeqx58=

Processing can be customised through the use of configuration options. Normally they are set in a configuration file associated with your account.

Processing can be customised through the use of configuration options. Normally they are set in a configuration file associated with your account.

解析处理可以通过使用设置选项. 来进行配置，通常这些设置在一个与用户账号相关的配置文件中。

C'est possible de personnaliser le processus en utilisant des options de configurations, qui sont généralement dans un fichier de configuration qui est lié à votre compte.

Processing can be customised through the use of configuration options. Normally they are set in a configuration file associated with your account.

You can also pass configuration options together with your Account ID (or Secure Token) using a ";" delimiter. For example:

You can also pass configuration options together with your Account ID (or Secure Token) using a ";" delimiter. For example:

你也可以在调用服务时将配置选项与用户账号一起提交并用“；”隔开。示例如下：

Vous pouvez aussi passer des options de configurations en même temps que votre ID de compte (ou Secure Token) en utilisant le délimiteur «;». Par exemple:

You can also pass configuration options together with your Account ID (or Secure Token) using ";" delimiter. For example:

ACCOUNT_ID; -turbo -maxlen 10000 -accept_langs "EN,CN" -local CN

Options

Options

配置选项

Options

Optionen

Processing can be customised through the use of configuration options. Normally they are set in a configuration file associated with your account.

Processing can be customised through the use of configuration options. Normally they are set in a configuration file associated with your account.

简历解析可以通过添加配置选项从而获得定制化的结果. 一般情况下这些解析配置选项会在与您的帐户相关的配置文件中设置.

C'est possible de personnaliser le processus en utilisant des options de configurations, qui sont généralement dans un fichier de configuration qui est lié à votre compte.

Processing can be customised through the use of configuration options. Normally they are set in a configuration file associated with your account.

You can also pass configuration options together with your Account ID (or Secure Token) using a ";" delimiter. For example:

You can also pass configuration options together with your Account ID (or Secure Token) using a ";" delimiter. For example:

你也可以通过在用户账号/安全口令中添加配置字符的方式(以";"为分隔符)实现设置. 例如:

Vous pouvez aussi passer des options de configurations en même temps que votre ID de compte (ou Secure Token) en utilisant le délimiteur «;». Par exemple:

You can also pass configuration options together with your Account ID (or Secure Token) using ";" delimiter. For example:

ACCOUNT_ID; -turbo -maxlen 10000 -accept_langs "EN,CN" -local CN