Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

r

If you are developing a Lequinox® enabled application towards our REST API and run into problems, please check these potential sources of error before you get in touch with support.

The integration API key is specified on the application information page in the Lequinox console (requires console administrator access).

 Contents

Application registration

Verify that you or your platform manager has

  • added a user group, server account and application in the Lequinox console.

  • connected the correct user group and server account to your application in the Lequinox console.

Verify that you have

  • included the base path in every request to the CDI REST API. (You can find the correct base path here.)

  • added the application integration API key to every request to the CDI REST API.

  • stated the Content-type as application/json in the object header when you are sending data to the API.

Transactions

Verify that the intended participants (creator and recipients) are correct.

Suggested procedure:

  • Save the transaction to a file and open it in an texteditor.

  • Find the ID of the creator and the recipients.
    (Look for the following sections in the XML file:

<creator>
         <dtsId>lq01.GVRwLLr8.0lkxS4Yw</dtsId>
     [...]
     <recipients>
         <recipient>
             <dtsId>lq01.V8im8sNU.us11ReqW</dtsId>

These IDs should match the creator and recipients specified.)

If any of the IDs is a server account and you, for example, want to open the transaction for that ID,
make sure you are using the correct integration API key and that it is connected to that specific server account.

  • No labels