Zapier API - Internal
Authentication
SourceForge APIs are authenticated with OAuth 2
PKCE is supported
Authorization URL is https://sourceforge.net/auth/oauth2/authorize
Token grant & refresh URL is https://sourceforge.net/rest/oauth2/token
API Requests must use "Authorization: Bearer <token>" header to provide the token.
API Endpoints
/rest/p/sfapi/zapier/auth
Check if authentication is good, and returns user's own name & email address.
/rest/p/sfapi/zapier/list_bsls
Provide a list of BSLs (Business Software Listings) that the user is authorized for. The "group_id" number is the internal number to be used in subsequent API calls.
/rest/p/sfapi/zapier/hook_action?action=visitor_data&group_id=<id>
Provides sample Buyer Insight Visitor data, for the specified BSL/group_id.
/rest/p/sfapi/zapier/hook_unsubscribe
Unsubscribes the Zap
"hookUrl" parameter is expected
/rest/p/sfapi/zapier/hook_subscribe
Subscribes the Zap.
"hookUrl" parameter is expected
/rest/p/sfapi/zapier/get_segments?group_id=<id>
For a future version - will allow users to choose from their saved segments (filters) previously created on SourceForge.
Push
A daily scheduled job will push new Visitor data to every subscribed Zap URL. This data is only available on a daily basis, so this is the soonest it can be sent.
Any 410 Gone statues will cause the zap to be unsubscribed in the SourceForge database.