Buyer Intent API Documentation

data update schedule the data provided by the api will be updated once on a daily basis the most recent data will be from the previous day authentication to use and interact with the api endpoints, users must authenticate by providing an access token with each call there are two ways of creating an access token registering and authorizing a new application generating a custom bearer token registering and authorizing a new application to request an access token you must first register a new application in your sourceforge account navigate to https //sourceforge net/auth/oauth/ https //sourceforge net/auth/oauth/ and fill out the form to register a new application copy the generated client id and put it as parameter in the url https //sourceforge net/rest/oauth2/authorize https //sourceforge net/rest/oauth2/authorize for example https //sourceforge net/rest/oauth2/authorize?client id=1234567\&response type=code https //sourceforge net/rest/oauth2/authorize?client id=1234567\&response type=code you will be redirected to the url set in your redirect uri parameter, which includes a parameter called authorization code copy that value and send it to the url https //sourceforge net/rest/oauth2/token https //sourceforge net/rest/oauth2/token using post method the following is an example of request body that can be posted to request an access token { "client id" "6b0256feeb8f45e98663", "client secret" "149824e0151f192faaa4a23c0a2b63db7a080695eebf92de82279252a35c0b8dd2d3bc85a8c71bd4", "redirect uri" "https //sourceforge net/software/", "code" "aazxhd4l7u6ufyypkcfjgc3hftwvfs", "grant type" "authorization code" } you'll get a response with the generated token, copy it and you can sent it in an api request through the authorization header, for example get https //sourceforge net/rest/p/sfapi/v1/bsls authorization bearer 5gtw2cpt6e7elfmlleqcesaaa3ukfd generate a custom bearer token custom bearer tokens provide an easier way to generate access tokens to authenticate the sourceforge apis to create one navigate to the oauth setup page https //sourceforge net/auth/oauth/ https //sourceforge net/auth/oauth/ after registering a new application you will see that there's a button generate bearer token click it and a new entry in the authorized applications section will be created your custom bearer token will be located in the bearer token field copy it and you can sent it in an api request through the authorization header, for example get https //sourceforge net/rest/p/sfapi/v1/bsls authorization bearer 5gtw2cpt6e7elfmlleqcesaaa3ukfd request rate limits to ensure fair usage and maintain optimal performance for all users, this api might limit the amount of requests a user can send in addition, the maximum date range for querying data from the buyer intent activity endpoint is 30 days more information there are 6 different variants of page " types " comparison these are comparison pages, with urls that look like this https //sourceforge net/software/compare/dynamics 365 vs salesforce/ https //sourceforge net/software/compare/dynamics 365 vs salesforce/ https //sourceforge net/software/compare/dynamics 365 vs hubspot crm vs salesforce/ https //sourceforge net/software/compare/dynamics 365 vs hubspot crm vs salesforce/ product page these are product pages with urls that look like this https //sourceforge net/software/product/salesforce/ https //sourceforge net/software/product/salesforce/ https //sourceforge net/software/product/dynamics 365/ https //sourceforge net/software/product/dynamics 365/ category page these are category pages with urls that look like this https //sourceforge net/software/crm/ https //sourceforge net/software/crm/ https //sourceforge net/software/accounting/ https //sourceforge net/software/accounting/ integrations these are integration pages with urls that look like this https //sourceforge net/software/product/salesforce/integrations/ https //sourceforge net/software/product/salesforce/integrations/ https //sourceforge net/software/product/pipedrive/integrations/ https //sourceforge net/software/product/pipedrive/integrations/ alternatives these are alternatives pages with urls that look like this https //sourceforge net/software/product/salesforce/alternatives https //sourceforge net/software/product/salesforce/alternatives https //sourceforge net/software/product/pipedrive/alternatives https //sourceforge net/software/product/pipedrive/alternatives case studies these are case studies pages with urls that look like this https //sourceforge net/software/product/sysaid/case studies/ https //sourceforge net/software/product/sysaid/case studies/ https //sourceforge net/software/product/sysaid/case studies/how sysaid is empowering itsm efficiencies in a large global/ https //sourceforge net/software/product/sysaid/case studies/how sysaid is empowering itsm efficiencies in a large global/ there are 3 different variants of page " targets " category these are category pages with urls that look like this https //sourceforge net/software/crm/ https //sourceforge net/software/crm/ https //sourceforge net/software/accounting/ https //sourceforge net/software/accounting/ product these are product pages with urls that look like this https //sourceforge net/software/product/salesforce/ https //sourceforge net/software/product/salesforce/ https //sourceforge net/software/product/dynamics 365/ https //sourceforge net/software/product/dynamics 365/ competitor these are competitor pages with urls that look like this https //sourceforge net/software/product/salesforce/ https //sourceforge net/software/product/hubspot crm/ https //sourceforge net/software/product/hubspot crm/ you can use these in your filters to segment by type of page the urls on sourceforge also follow a formulaic pattern, so you segment based on urls as well