1

What's the current status of the API following the update to tags? For searching, can ony see: http://www.daniweb.com/api/articles/search?query=blah which gives the same results regardless of the query text (and the 'members' equivalent, which seems to work). Was there not a tags endpoint before? Can't remember. Anyhow, was thinking of a side project with the API, but I don't want to start if it's not working as expected. For example, as the PHP forum no longer exists, I was trying to get articles with 'PHP' in them, but got a lot of junk. Thanks.

3
Contributors
13
Replies
98
Views
1 Year
Discussion Span
Last Post by diafol
Featured Replies
  • 1
    Dani 1,665   1 Year Ago

    Unfortunately, there was never a tags endpoint, and the API has not been updated since switching to the tag-based system. While there is currently no way to filter results by tags (only forums) but this will be handled *very soon*. I'll try to get to it tonight or tomorrow the … Read More

  • 1
    Dani 1,665   1 Year Ago

    You can now use the https://www.daniweb.com/api/articles/{:TAGS} endpoint, where {:TAGS} is a semi-colon delimited list of tags. They use OR instead of intersect. Additionally, I've discovered tonight that you might be getting NULL back because you are using an older version of cURL, and your cURL request cannot connect over SSL. … Read More

  • 1
    Dani 1,665   1 Year Ago

    Yes, reverted back to the way things were yesterday morning (but I still don't understand why they weren't working for you yesterday morning but they are working for you now.) Read More

0

Been trying to get this to work:

$client_id = xx;
$client_secret = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx';
$current_url = 'http://'.$_SERVER['HTTP_HOST'].$_SERVER['PHP_SELF'];

if (!isset($_REQUEST['code']))
    header("Location: https://www.daniweb.com/api/oauth?response_type=code&client_id=$client_id&redirect_uri=".urlencode($current_url));

$ch = curl_init('https://www.daniweb.com/api/access_token');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, array(
    'code' => $_REQUEST['code'],
    'redirect_uri' => $current_url,
    'client_id' => $client_id,
    'client_secret' => $client_secret,
    'grant_type' => 'authorization_code'
));
$response = json_decode(curl_exec($ch));
curl_close($ch);
var_dump($response);

I'm getting null for $response. The redirect is fine. The id and secret are OK - triple checked under "manage my applications". Any ideas? I'm getting return code. Client Side Auth working fine.

Edited by diafol

1

Unfortunately, there was never a tags endpoint, and the API has not been updated since switching to the tag-based system. While there is currently no way to filter results by tags (only forums) but this will be handled very soon. I'll try to get to it tonight or tomorrow the latest.

Diafol, in looking at the database, it seems that we are receiving your OAuth request and are generating an access token for you, but you are not exchanging the code for the access token.

I can't imagine why you are getting NULL for response. You should be getting, at least, a friendly error message :(

I copied and pasted your exact code with my client_id and client_secret and it printed out a JSON object that was correct. I then tried using a bad secret, and I received the following:

object(stdClass)#59 (2) {
  ["error"]=>
  string(90) "There was an error fetching an access token. The client_id and client_secret do not match."
  ["request_data"]=>
  object(stdClass)#60 (5) {
    ["code"]=>
    string(1496) "YDiMZDkP75tlj46f3I0XoaBNIgidfiYot8NwClbXNjPx1iw5VvzSy+yB5d+xOWjkvruRK8CDp2jZBvvJyxbzV7MGdBYGPFe9WsB53Bdcy4ko+OaRmUuTGB1+nyGRHBJR4V4A7aXpzfU3sJUt9eBDcMYpRcOzOkkqH+0VGgz5KBRyY3l/ShoxFm5VAYACM+OdyMXklwvEHn+HBIQ7RUzwjCHBRpIoQkMsJwOQ/paohVwXk7y+jOd2UyfyGmH+/NPphnPH271/UCylQ1lolRxmrvMMUyWvtB8OPrExLk3gPWHWMlopAlFrI9sOvP6YniA0uAXvDrXOvQQAqU/VgPaHSUszr1YEhSWFhPHkC0rqxb2leh9HyrKLksuUPnGlFfoy6rJYV3GPewk2Bg6aOlKIU4XKaL3jJYWXPxHdVZTaBFXUIhLQyInlpA4Uctf7TmkPBfnx3/dneDNVHsURCSYcS0D//a9X0rePC9ffgkdId4yiKHPsw5K9dry5Z3d0dO7g3Iwbn24Hg0WjARzRiS77EtfNfNmQjFbNUIlAfhvUGXwQfuRuMW09Kt1pnXY/jVOEg+ntIEBQ5xIx3zIzhKl38rxIBgf8ZVmjv+cMMxSDjbvmqoP6IQQvjZv5hZu1NR6I0HmFLNcMro+poZgro8e58US8oTZWWkr/2w+XACKuY/M6d9xqec5f1OzHSTUHe+wczcieGinOOxVAZDEDG7bJPjySgMQVtnlVpxT0w3lQdOacwWGBC0MqASDbjnHHGARe112r8+jxeC6PhAwwHeR5qiRj8vuTYdqLl+w7MOMCLTN1haub/gBISs0ZUqJ1ukfFEJXLyNe0ZmdRKW12DFdXAgfCuwkw5X2/PGjTSw4HTZheLC6yh0sAsjvRrk5Q20fzAAbzPivBpb7UA9C57+Xhy9/n8Ri9taME9nIQQ5pHwZcjfhmNl6hKDkdJFDDSSyD6TqT1EBsYeoCRL/h+SNZcELh+r9nVHxOXshjAeVAmjmOwLlOAvPDa5nGb/mtgsl9F8zkImJkwR2xOvFq/cws43mQ18u2ITQUXsrq/DfPtZMZA+2G5yZrSg49+c8oiRw0dpQOp6DtSNwO+q8JjSAGfmVstVagjj9HdTcneRp0g0HdqzViO5iEZ0oI9LCCKUY8n29VlffoW6nsnyigmB9/UnT6hZMdYmXR3z+gRlBxzxNajdlAXxJG4uhBl27iycqu3j8VdyjRNj9gEBeLNUVFbqgHZv3LufbTQJcobyZnwGmpi0pVgRSqv+cmkXbwcLortByHtG5dGrBj58fX93mvjwV3HSU0SsjjRfe41kkeybTdGhTuhzNhQCPsAzMnwZNciWawmdof7jyPNZj/lS1GTgIA55YK0258ItYHWg1SCmDDv593CK0mRtwo6tuMZTP/0RpNfemr2UgTebqmc5NGqKjm/fBkhoHfpe3b61/Dr3XW50UHjtd5Z9h386cYkCx+R/SJTGNiog7PLzYGhUPvL7w=="
    ["redirect_uri"]=>
    string(43) "http://www.daniweb.com/index.php/api/diafol"
    ["client_id"]=>
    string(1) "1"
    ["client_secret"]=>
    string(3) "abc"
    ["grant_type"]=>
    string(18) "authorization_code"
  }
}

I'm not sure why you are getting NULL but I can't reproduce it.

0

Heh heh, who knows? The client-side oauth works fine though. Maybe because I'm using localhost? But I'm getting the redirect, so not sure. No worries Dani. No rush. It's an academic project just for me - just want to try out a few things.

1

You can now use the https://www.daniweb.com/api/articles/{:TAGS} endpoint, where {:TAGS} is a semi-colon delimited list of tags. They use OR instead of intersect.

Additionally, I've discovered tonight that you might be getting NULL back because you are using an older version of cURL, and your cURL request cannot connect over SSL. Try using http:// instead of https:// in the cURL request. Yes, it's insecure, but I'm currently looking for a workaround.

0

Hi Dani just an update. Got curl to work using http instead of https. However, file_get_contents() being very tempramental. Can't use https so using http. BUT, when I try this I get SSL error:

$output = json_decode(file_get_contents('http://www.daniweb.com/api/forums/2'));
var_dump($output);

Whereas this works:

$output = json_decode(file_get_contents('http://www.daniweb.com/api/forums'));
var_dump($output);

The direct url in browser works fine for both. I noticed a redirect to the https version on the forums with :IDS.

BTW:
I'm using cURL 7.39.0 (enabled) on Win8/ PHP 5.6.3. All SSL options enabled. OpenSSL/1.0.1i. Registered transports: tcp, udp, ssl, sslv3, sslv2, tls, tlsv1.0, tlsv1.1, tlsv1.2

0

You're getting inconsistent results retrieving forums because they are sometimes cached.

When using file_get_contents, always use https (it will work).

It's just cURL requests with POST data that are not working with https right now.

0

DId you change anything? Seems https api calls now working for me. Thanks Dani. :)

1

Yes, reverted back to the way things were yesterday morning (but I still don't understand why they weren't working for you yesterday morning but they are working for you now.)

0

Yes, reverted back to the way things were yesterday morning

That must be why Firefox was alerting me to an insecure SSL cipher and now it's back to normal.

0

Sorry for reviving this zombie, but is the DW API still live or is it incorporated with Dazah API? I looked at the Dazah API and its all around conversations and Dazah-like stuff I will probably never use. Is there still a way of creating a webapp using DW data?

0

Not at this very moment, but it will be coming back shortly, mostly in the form of custom aliases to various Dazah API endpoints. Dazah's API is super duper robust in that it's capable of doing everything that the DaniWeb API did when it comes to searching/filtering/profiling members, plus much more. It's just a matter of perhaps creating a "simplified" wrapper for it that revolves around DaniWeb use cases. Outside of that, the only additional DaniWeb API endpoints that are not Dazah related are retrieving articles and posts via JSON, which will also be making a comeback.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.