Subscriber API Options

  1. Manual Method (one-by-one)

What is it: Manually adding in a subscribers’ details via an online form on YUDU Publisher, one at a time.

Pros: Great for one-off access (say you need to add yourself so you can access your publications).

Cons: Only does one at once, not suitable for large batches.

Cost: Free, form is available via and can be used at any time.


  1. Manual Method (bulk upload) 

What is it: Uploading a csv list of multiple subscribers to YUDU Publisher.

Pros: Upload once and leave YUDU to process them. (Can take around 10-15 minutes for larger csv lists with many thousands in… this is because all records are encrypted)

Cons: Requires someone to upload the list, and ensure it’s in the correct format.

Cost: Free to use, from a time standpoint however long it takes for someone to format the list.


  1. Automated Method (YUDU API implementation)

What is it: Our ‘standard’ offering when it comes to automating the creation, reading, updating, and deleting of subscribers. It’s a script you are required to write which takes the data the subscriber enters when they purchase something from your site, and passes it over to YUDU automatically. It’s fully documented here:

Pros: Once it’s set up properly, you can leave it operational with peace of mind knowing it will continue to do its thing. We also constantly improve this API, and is fully documented. We’ve help many clients in the past achieve this. When we make updates to our API, we don’t roll out changes that will break our customers code. If there is anything we need to inform you of (rare) we will do so.

Cons: Requires a dedicated professional web developer to set up.

Cost: As a ballpark figure, the hiring of a web developer to do this can cost around £1500, based on past client projects. We can offer support, but won’t write the code needed to do this for you.


  1. Automated Method (Woocommerce Integration)

What is it: A more specialized approach, where we expand on the YUDU source code to ‘talk’ to your database. Woocommerce/Wordpress both will interact with a database of customer purchases and records that will already be in existence. We need one of our Developers to configure YUDU to correctly communicate with your database.

Pros: Like the YUDU API implementation, once it’s set up it cuts down on the overhead required to get the subscribers access to their purchases. This could improve customer satisfactions because they aren’t waiting days/hours for their log in become active.

Cons: Is a lot of work upfront, it will require contracting one of our developers to work with your web team to expand on the functionality of YUDU.

Cost: This is more costly than option #3 as we need to allocate one of our developers to the task, and the price varies on how long they think it will take.


  1. Automated Method (FTP CSV upload)

What is it: A hybrid of option #2 and #3. It’s getting a script to pull data from your database and populate that into a .csv file. This csv file is then uploaded to a separate account on our FTP server where it is then processed in a batch.

Pros: A little bit cheaper and quicker to get going than #3. In the past a client has accomplished this on a Woocommerce site with PHP pulling information from the MySQL database, and using a chron job to send that to our FTP server.

Cons: Doesn’t offer all the features the main API route does (option #3). For example it can only grant subscribers access to subscriptions (via a start and end date). It can’t grant access to single-edition purchases. It also requires the csv to be created in the right format. Finally you cannot query data that is sent over. So you can’t check what subscriptions a particular subscriber already has.

Cost: Requires a web developer to be contracted by yourself to ensure your database sends over the correct information to YUDU. These usually charge by hour, and the time it takes one good developer to do this is similar to option #3.

Have more questions? Submit a request Print Friendly and PDF


Powered by Zendesk