Frequently Asked Questions

General questions

Should I register?

Only if you plan to create an application that will use the API. There's no registration required just to use the demo on this website.

I'm conducting research, can I use the API for my project?

Yes, this service is primarily meant for academics and research. Please sign up and tell us more about your project.

I've registered, where do I log in?

You don't. The purpose of the registration is to get a Customer ID and API key to authenticate calls made from your application. If you haven't saved your access credentials when you registered you can use Account Information Reminder to see them again.

I've signed up, but the API key does not work...

There's approval process involved before your API key is activated. Please note that this is a free service without dedicated staff to handle the process, so please allow some time for the process to be completed.

Demo prediction on this website

When will the Facebook prediction work?

We don't know. Please note that the API is unaffected by this and you can still make Facebook predictions with your own Facebook app.

I would like to disconnect my Facebook or Twitter account after using demo prediction

Any access granted to social media accounts is temporary and within the scope of permissions granted.

That means we read your data, but it doesn't give us ability to access whole social media account or make any changes to it. Moreover, our read-only access is valid only for a period of time. We currently automatically remove any access tokens after 5 minutes. After that time we're technically prevented from any further access without the user re-connecting.

You can also expire any existing tokens by doing it yourself. This can be accomplished by:

Please remove all of my personal information associated with me, such as email or my name

We currently don’t store user's profile information, names nor any emails.

Please use My Data @ Apply Magic Sauce Tool in order to learn what is stored and for what purpose, view all the data collected by us and if you wish - delete it.

Those predictions are inaccurate, it says I'm [...], while in fact I know I'm [...]

Like any psychometric test, the results may not always correspond with estimation of own personality or abilities. Our tool is intended to help people understand what a digital self might look like to other people and also what that might tell you about who you really are.

In other words, we hope that enabling to better understand the psychological significance of own behaviour on social media makes people better equipped to interpret the potential impact of this behaviour on oneselves and others.


Can I send you user's Facebook ID or Twitter handle, or maybe email address to get a prediction?

No. Our predictions take Facebook like ids and text written by the user as an input. It's your responsibility to obtain the digital footprint of the user in a manner that is in line with our ethical guidelines, especially the part regarding the need to obtain the informed consent of individuals about whom predictions are made.

Getting empty response (status code 204) from API method

This is a normal response, indicating that digital footprint provided as an input is insufficient to make accurate prediction.

For /like_ids method we currently need at least 10 from which at least 5 should be recognised as 'predictive'. The solution to this is to send us more like ids to increase the likelihood of success. Though of course some Facebook users can have unpopular, not predictive, or just not enough likes altogether.

For testing purposes you can try the following like ids that are know to yield prediction:


Getting 429 response from API method

This is indicating that your monthly usage limit was exceeded for your Prediction API account. Consider contacting us to talk about increasing it.

How can I know how much API calls I have left?

While we don't currently offer a dedicated customer panel, they are returned every time from /auth method of the API. Please see the relevant part in Technical Documentation

I cannot connect to the API from my client-side JavaScript application

This is because browsers prevent making request across different domains for security reasons.

If we'd allow for these requests anyways, i.e. by setting Cross-Origin Resource Sharing (CORS) policy, we would encourage leaking api keys to the public. It's in your best interest to keep it secret from anyone else.

How I'm supposed to know my application gets 'good' predictions?

Just try the demo on this website and compare the results. If they significantly differ, it means something is wrong with your application.

The most common cause for it was customers not getting all of the user's likes from Facebook, because Facebook returns them in pages, 25 per page. Even with likes per page limit increased it takes multiple calls to get all of them. Please refer to Facebook Graph API documentation for details.

The demo here is just an ordinary client application and it's not treated differently, except it has all available permissions to use sensitive or experimental traits.