Forums » New User Questions

Back To Topics

Picks sent by POST are not appearing in the source history

  • dherrerab
    • 2 posts
    March 20, 2025 9:15 PM GMT

    I've sent some picks by POST, and it always is returning a pickid.

    But the pick is not appearing in the source, and it's really difficult to know the reason why. The pick status returns this:

        "processing_status": "PROCESSED",
        "processing_result_short": "Successful pick submission",
        "execution_result": "NO ORDER EXECUTION DATA"

    But the reason why the result is no order???

    After some time retrying with different alternatives, or even with a completely new bet, the picks sent are returning always this status:

    {
        "execution_result": "PICK NOT FOUND OR INVALID KEY",
        "processing_result_long": "PICK NOT FOUND OR INVALID KEY",
        "processing_result_short": "PICK NOT FOUND OR INVALID KEY",
        "processing_status": "PICK NOT FOUND OR INVALID KEY"
    }
     
    How could I get more details about what is happening?
    Thanks!
  • tango
    • 54 posts
    March 27, 2025 4:57 PM GMT

    Hello,

    Note that the pick ID you receive after submitting data only confirms that your request was received and processed. It does not guarantee that the processing was successful.

    To check the outcome of a pick, you need to use the pickstatus endpoint. This requires two pieces of information:

    • The pick ID that was returned by the postpick endpoint.
    • The bot ID that was used to authorize the original pick request.

    If you encounter the error message "PICK NOT FOUND OR INVALID KEY" when using the pickstatus endpoint, it indicates one of two possibilities:

    • You have entered an incorrect pick ID.
    • You have entered an incorrect bot ID.

    A common reason for this error is providing an incorrect bot ID during the initial postpick request. If the bot ID is wrong at that stage, the system will be unable to locate your pick when you subsequently call the pickstatus endpoint.

    Therefore, ensure you are using the correct bot ID both when making the initial postpick request and when checking the status with the pickstatus endpoint.

  • dherrerab
    • 2 posts
    March 30, 2025 4:53 PM BST

    Thanks, everything is correct, the botID is correct, and the pickID is correct. So the pick was not successfully placed, but the reason is unkown.

  • tango
    • 54 posts
    March 31, 2025 11:40 PM BST

    Just to clarify: PICK NOT FOUND OR INVALID KEY is an error message that is returned by the pickstatus endpoint. To call this function you need to pass the ID of the pick that you are enquiring for and the bot ID that you used when submiting the pick. So, when you receive this error message it means that this pair of pick ID + bot ID was not found in our database. This can happen for two reasons: (1) The bot ID used and the pick ID returned by postpick do not match the values used in pickstatus or (2) Your postpick request was missing a valid bot ID. In this particular case it was (2) as your posted picks were missing critical fields including a valid bot ID.