Error when placing appkey into their code

Options

Customer successfully makes the key from APPKEY and places into their code, but getting below errors. Reference the attached email/screenshots from customer. What could be the issue here?

Status code 400: Bad request on handshake url http://localhost:9005/api/handshake {"code" :400, "message" : "application key is not valid.", "stack" : "error"

Error on handshake url http://localhost:9005/api/handshake

Tagged:

Answers

  • Hi @dave.obrien ,

    The error message indicates that app key used in the code is invalid. However, with the application key provided, I can open session and retrieve the data properly. Could you please ask the customer to try restart their machine and Workspace application and try running the code again. Then please let me know if the issue still persists.

    image.png

    Plus, please let me add that the library recommended to be used is the LSEG Data Library, which is the latest version of the Data Library. More info can be found in article Essential Guide to the Data Libraries - Generations of Python library (EDAPI, RDP, RD, LD) | Devportal

  • Customer came back and said this did not work. (Reference screenshot too)

    The code your dev shared worked when I tested it in a separate file. However, when I run the actual program, I’m still getting the same error:

    “Session is not opened. Can’t send any request.”

    I’ve attached a screenshot for reference.

    image.png
  • Jirapongse
    Jirapongse ✭✭✭✭✭

    @dave.obrien

    Please enable the debug log in the library by using the following code before opening a session.

    config = ld.get_config()
    config.set_param("logs.transports.file.enabled", True)
    config.set_param("logs.transports.file.name", "lseg-data-lib.log")
    config.set_param("logs.level", "debug")
    ld.open_session(app_key = ''<app_key>") …

    This code will generate the lseg-data-lib.log file. Before sharing it, please ensure any private information is removed. Once shared, we can analyze the log to help identify the issue.