Have you tried the comment in the ost-api-example.php?# NOTE: some people have reported having to use "http://your.domain.tld/api/http.php/tickets.json" instead.

yes have tried using http.php   

9 days later

I have not installed 1.9.1 yet, so nope.  Have you actually tried: http://your.domain.tld/api/http.php/tickets.json?Because your answer said http.php. Are you using mod_rewrite or mod_redirect etc?

I apologise I'm not a coder but have a very basic knowledge that has enabled me to manage ost thus far, so if you are able to help with padding out a bit more info that would be much appreciated. (eg I'm not familiar with reference to .tld and what is or where is tickets.json  plus your reference to mod_rewrite or mod_redirect??, so I dare say this must be my missing link???) Here's an extract from the code I used (replacing my domain with mydomain.com):// You must configure the url and key in the array below.

$config = array(

'url'=>'http://support.mydomain.com/api/http.php/tickets.json', // URL to site.tld/api/tickets.json

'key'=>'264ED201BD4E06B5D1D459078F5CAA87' // API Key goes here

);

Thanks for any further details you can provide...

.tld is an abbreviate for top level domain.  i.e. .org, .com, .net etc. Your snippet appears to be correct.mod_rewrite or mod_redirect are web server tools (modules) that allow people to redirect from A to B, or re-write the URL in the broswer from domain.tld/osticket to tickets.domain.tld (which really I would think people would use DNS to do.. but... /shrug)  If you don't know then chances are you're not.Have you also tried:http://your.domain.tld/api/tickets.json

Yes I have tried http://your.domain.tld/api/tickets.json

No ideas.  You should consult your PHP error logs and see if there is anything there. You should check and make sure that your API key is correct.  And make sure that the traffic is actually coming from where you think it is.

- no errors in php error log- api in ost API key is same as entered in test script  (mydomain.com/test2.php) - as above- IP address of API Key is same as results from "ping mydomain.com" Has anyone else been able to successfully use the API?

9 days later

Has anyone been able to successfully use the API or had similar problems?

I have been able to successfully do the API integration of OSTicket with Yii.If anyone is interested I will prepare a solution for you.

Geo99M6Z, I've come to a dead end so I'd certainly appreciate a solution if you could please. 

ntozier, does this give any clues...  the domain of my ost is support.mydomain.com  (mydomain of course replacing my actual domain)so in the code I use http://support.mydomain.com/api/tickets.jsonif I put that address in a browser it responds with "URL not supported" If I use http://mydomain.com/api/tickets.json it goes to my domain web site (tho page not found)So is this an issue because its a subdomain? 

a year later

infotec, i have the same problem like you now.i use 1.9.8.1followed all advice given above, API key is generated using the correct IP address.browser (IE/Chrome) result is always "Unable to create ticket: Valid API key required"any solution to share please?

infotec, i'm NOT using subdomain, i use v1.9.8.1 in a sub-folder.I tried both:api/tickets.jsonapi/http.php/tickets.jsonI still get browser error "URL not supported". So i don't think subdomain is the issue.my browser (IE/Chrome) result is always "Unable to create ticket: Valid API key required"

If you are getting "Unable to create ticket: Valid API key required" then the system doesn't appear to like the API key that you are using.

i followed the steps to create API Keys under Admin > Manage > API Keysi've tried create 2 different API keys but still the script failed.i've also added below 3 lines to check. all values are correct and OK.echo $_SERVER . "<br>";echo $config . "<br>";echo $config . "<br>";i have no idea why it fails in our installation.

API-keys.png

I dont know, but this thread is for a different version then you are running so if you are having an issue you really should have started your own thread instead of zombie-ing one from 2014.Whats the IP of where the request is being originated from?Is that the IP that you used to make your key?

oh noted.yes. the IP address used to create API Keys is the IP address of my laptop broadband connection which initiate the HTTP request.They are same as $_SERVER

4 months later

Did you ever solve this? If so, how?