Create your own Flickr OAuth application to Connect to Filestack:

By default, you do not need to configure anything to start uploading files from Flickr, Filestack is ready to go out of the box. When a user logs into their Flickr account from your site, the Filestack company application will show up. You can configure it so that your application shows up instead in order to make a more seamless experience for your customers. So let's get started.

Now go to the developer portal and click on Auth Keys on the left hand side. Scroll down to Flickr and cut and paste the API Key into Flickr App Key and Secret into Flickr App Secret and then hit save.

Next test your app to make sure it works.

Agree to the authorization request.

Success!!!

Congratulations! You have successfully connected Filestack with Flickr using oauth.

Flickr Webhooks for Your Application

Flickr Webhooks serve the purpose of notifying users about events that occur in relation to their Filestack account. In your developer portal, you can set one or many urls whose purpose is to receive the messages triggered by specific Filestack events.

These are the three event types that will send messages to your webhook url(s) concerning Flickr:

Flickr File Uploads

Flickr File Exports

Flickr File Conversions

Configuring Flickr Webhooks

Filestack Webhooks are configured in the developer portal under Credentials > Webhooks. If you enter your url and select "All", then one entry will be made for each type of Filestack Webhook Event, including the ones for Flickr. To learn more about configuring and receiving webhooks please visit our main webhooks documentation page.

Receiving a Flickr Webhook Notification

Configuring your server to receive a new webhook is the same as creating any page on your website. If you are using Sinatra, add a new route with the desired URL. In PHP you could create a new .php file on your server. It doesn't need to be complicated. With webhooks, your server is the server receiving the request. You can even use an external service such as RequestBin as shown in the screenshot above.

Webhook data is sent as JSON in the request's body. The full event details are included and can be used directly. The "action" in the JSON is the type of Filestack event that happened, be it a file being uploaded, or simply the Filestack dialog opening.

Filestack will retry sending a webhook 3 times if the first attempt fails. The second attempt to deliver a webhook happens 5 minutes after the first attempt, the third attempt happens after 1 hour, and the final attempt to deliver a webhook happens 12 hours after the first attempt.

Note that for file uploads, both symlinks and files copied with pickAndStore, the "client" field shows the service used.

For conversions, the "provider" shows where the file resides. If the file was stored to Filestack's storage, the provider will be "internal", otherwise it could be "amazon" if the original was stored to S3, or one of the cloud drives Filestack connects to, such as "Flickr" if the link to the file was a symlink.

The following are examples of what the Flickr specific webhook messages include and look like: