Since FeedPress’ wee early years, it’s had a fairly robust and easy to use POST or GET method API, with answers formatted in JSON (YAY). This has given developers access to many parts of the web app. As we’ve been working on things, I realized we’ve never talked about it much on this blog, so this serves as an official announcement as well as update on the latest additions to the FeedPress API (up to July 2018).

I’m pleased to announce today that we’ve added numerous methods that bring the API closer to parity with the web app. Some of the most requested features you’ve asked of us are methods to access our podcast hosting service, such as uploading and deleting media files (MP3s).

Our most recent addition this summer is adding access to Custom Hostnames. For the uninitiated, Custom Hostnames allow you to fully whitelabel your RSS feeds by utilizing your own domain name with FeedPress, providing the ultimate in flexibility over the structure of your feed as well as complete ownership of your intellectual property.

With our new API method, you can register your hostname and path, which previously you could only do via the web app. Adding one hostname and path for an RSS feed isn’t a big deal, but if you need to add a lot in bulk, our API makes it very convenient and efficient. We’ve already had customers utilize this functionality when creating 50+ RSS feeds in one fell swoop via their Content Management System.

Our API documentation with full details are available for free. In order to utilize the API, you must have a FeedPress account.

Here’s an overview of the things you can do with the API

GET /login.json

Redirects the user to the FeedPress authentication page. See Authentication for more details.

GET /logout.json

Deletes the authenticated user’s token.

Articles found elsewhere on the Web!