1. Kayako Download customers: we will continue to develop and support Kayako Download beyond July 2017, alongside the new Kayako for existing customers.

    Find out more.

  2. The forum you are viewing relates to Kayako Classic. If you signed up or upgraded to the new Kayako (after the 4th July 2016), the information in this thread may not apply to you. You can visit the forums for the new Kayako here.

Making requests

Discussion in 'Developing, APIs and extending' started by Jimmy Dev, Sep 15, 2016.

  1. Jimmy Dev

    Jimmy Dev New Member

    Hi, sorry if these are terrible questions, but I am a bit stumped trying to integrate with Kayako's API.

    I am reading through the docs and trying to build in an integration for one of our clients. They want general info about tickets and such.

    I have followed the generate signature steps listed in the API docs. But there doesn't seem to be a very good example of how a request is to be constructed and sent.

    For example, I want to get a list of Tickets.

    On the API docs page, I see a couple of "sample" requests. One spot looks like this:

    What a request looks like
    https://example.domain.com/api/index.php
    ?e=/App/Controller/Action
    &parameterA=valueA
    &parameterB=valueB
    &parameterC=valueC
    &apikey=d75a00ef-08b6-5b04-5d29-d3b7ca46138a
    &salt=itobgt701t5nat7oor9z4t813edc5t8d
    &signature=MzNiNjk4ZmUyY2FlNjQ5YmRkNjA0YjkyYTQ0NmY5OTQ4MGVkYTIwMzZjMzFkYmJjMzk4MzgzNjNiMzZjYTE4NQ==

    the other looks like this:

    Request URL type
    Some customers on certain types of web server run into problems using one, but not the other (often relating to rewrite rules, or security packages).

    There is no explanation or context for what the App/Controller/Action is in the documentation, so I guess it refers to the endpoint?

    Either way, reading the docs, it appears that the pattern for constructing a uri is to append the apikey, salt, and (presumably url encoded) signature to the end of the query string.

    So, to get a list of tickets, my understanding is that I will need to make a GET request to the following URI:

    https://{client's domain}.kayako.com/api/tickets/ticket/listall?apikey={client's api key}&salt={generated salt}=&signature={url encoded signature}.

    Of course, you probably already know that this does not work.

    I get a 401: NO SALT PROVIDED!

    But I have poured over the docs, forums, and stack overflow and nobody else seems to have this question. Can you please help me understand what I'm doing wrong?

    NOTE:
    Both example requests on the api documentation show the endpoint as "/api/index.php..." which is not something I often see in REST apis. Also, it just returns a 404 Page not found.
     

Share This Page