Buyer Intent API Documentation
The SourceForge Buyer Intent API enables you to access Buyer Intent Data from SourceForge via API, and integrate it with your other software and systems.
The data provided by the API will be updated once on a daily basis. The most recent data will be from the previous day.
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
To request an access token you must first register a new application in your SourceForge account
Navigate to 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
For example:
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 using POST method
The following is an example of request body that can be posted to request an access token
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:
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/
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:
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.
There are 6 different variants of page "types":
- comparison - these are comparison pages, with URLs that look like this:
- product_page - these are product pages with URLs that look like this:
- category_page - these are category pages with URLs that look like this:
- integrations - these are integration pages with URLs that look like this:
- alternatives - these are alternatives pages with URLs that look like this:
- case_studies - these are case studies pages with URLs that look like this:
There are 3 different variants of page "targets":
- category - these are category pages with URLs that look like this:
- product - these are product pages with URLs that look like this:
- competitor - these are competitor pages with URLs that look like this:
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.