Provider – X (formerly Twitter)

Table of contents

• How to enable the provider
• Settings
• Sync data
• Frequently Asked Questions
• Common error messages

How to enable X login in WordPress

App creation steps if you selected the v1.1 API version:

To be able to log in via X you must create an X app first.

1. Navigate to https://developer.twitter.com/en/portal/projects-and-apps
2. Log in with your X credentials if you are not logged in.
3. If you don’t have a developer account yet, please apply one by filling all the required details! This is required for the next steps!
4. Once your developer account is complete, navigate back to https://developer.twitter.com/en/portal/projects-and-apps if you aren’t already there!
5. Click on “+ Add Project”!
6. Name your project, and go through the basic setup. You’ll need to select your use case, give a description then click the “Next” button.
7. Choose the “Production” option for “App environment”, then press “Next”!
8. Into the “App name” field, enter a name for your App, then press “Next” again!
9. You’ll find your API key and secret on this page. Copy and paste the “API Key” and the “API Key Secret” to the corresponding fields at Nextend Social Login > X > Settings and press “Save Changes”.
10. Go back to your X project and on the left side, under the “Projects & Apps” section click on the name of your App.
11. Scroll down and click on the “Set up” button at “User authentication settings”.
12. Choose the “Read” option at “App permission”.
13. If you want to get the email address as well, then don’t forget to enable the “Request email from users” option. In this case you also need to fill the “Terms of service” and the “Privacy policy” fields with the corresponding URLs!
14. Select the “Web App, Automated App or Bot” option for “Type of App”.
15. Into the “Callback URI / Redirect URL” field you should add the URL that Nextend Social Login suggests at the backend.
16. Enter your site’s URL to the “Website URL” field.
17. Click on “Save”.
18. Go back to Nextend Social Login then verify and enable the X provider!

App creation steps if you selected the v2 API version:

To be able to log in via X you must create an X app first.

1. Navigate to https://developer.twitter.com/en/portal/projects-and-apps
2. Log in with your X credentials if you are not logged in.
3. If you don’t have a developer account yet, please apply one by filling all the required details! This is required for the next steps!
4. Once your developer account is complete, navigate back to https://developer.twitter.com/en/portal/projects-and-apps if you aren’t already there!
5. Name your project, and go through the basic setup. You’ll need to select your use case, give a description then click the “Next” button.
6. Choose the “Production” option for “App environment”, then press “Next”!
7. Into the “App name” field, enter a name for your App, then press “Next” again!
8. Click on the the App settings button on the bottom right corner.
9. Scroll down and click on the “Set up” button at “User authentication settings”.
10. Choose the “Read” option at “App permission”.
11. Select the “Web App, Automated App or Bot” option for “Type of App”.
12. Into the “Callback URI / Redirect URL” field you should add the URL that Nextend Social Login suggests at the backend.
13. Enter your site’s URL to the “Website URL” field.
14. Click on “Save”.
15. Find your “Client ID” and “Client Secret”. Copy and paste the credentials to the corresponding fields at “Nextend Social Login > X > Settings” and press “Save Changes”.
16. Verify the settings and enable the X provider!

Required Nextend Social Login settings for X App

Once your X app is ready you’ll need to copy and paste the API Key and API Key Secret or the Client ID and Client Secret ( depending on the selected API version ) to the X provider’s Settings tab.

Verify the settings

Once your API Key and API Key Secret or the Client ID and Client Secret ( depending on the selected API version ) have been added you need to verify the setup first. This verification helps you identify possible problems with the app.

Settings

API version

The OAuth and API version that Nextend Social Login should use. Either v1.1 or v2

API Key ( v1.1 )

The API Key of your X app. You can find it at your App → Keys and Tokens tab → Consumer Keys section.

API Key Secret ( v1.1 )

The API Key Secret of your X app. You can find it at your App → Keys and Tokens tab → Consumer Keys section.

Client ID ( v2 )

The Client ID of your X app. You can find it at your App → Keys and Tokens tab → OAuth 2.0 Client ID and Client Secret section.

Client Secret ( v2 )

The Client Secret of your X app. You can find it at your App → Keys and Tokens tab → OAuth 2.0 Client ID and Client Secret section.

Username prefix on Register

Whenever a new user registers with their X account they can get a custom prefix so you can easily identify them.

Fallback username prefix on register

Whenever a new user registers with their X account and we can not generate a valid username from the first name or last name, a random username will be generated. With this option they can get a custom prefix so you can easily identify them.

Terms and conditions

This option can only be seen, if Terms and conditions is set to Show in Global Settings → Privacy tab. Here you can set custom Terms and Conditions for users who register with X. For more information please read our GDPR documentation.

Profile image size

The avatar will be stored with the selected size.

Sync data

By default Nextend Social Login stores the first name, last name, email, avatar url and access token if it is possible, however some additional information can also be retrieved and stored.
When an option is checked, that field will be stored in a meta key with the specified name.

Sync fields

It determines when the synchronization shall happen.

• Register: whenever a new user registers with a provider, their data will be retrieved and stored.
• Login: whenever user logs in with a provider, their data will be retrieved and stored.
• Link: whenever user links and existing WordPress account with a provider, their data will be retrieved and stored.

Bio

Stores the user’s bio.

Language

Stores the user’s language.

Location

Stores the user’s location.

Register date

Stores the date, when the X account registration happened.

Profile URL

Stores the user’s X profile URL.

Screen name

Stores the user’s screen name without the @ tag.

Owned website

Stores the user’s website.

Frequently Asked Questions

1. How can I get the email address from the X users when using the v1.1 API version?

If your app is already set up, go to the Projects & Apps Overview page, find your App and click on the App settings icon ( the one that looks like a gear). Then click on the “Edit” button at the “Authentication settings” section and switch on the “Request email address from users” setting.
Important: If you ask the email address, you also need to fill the “Terms of service” and the “Privacy policy” fields with the corresponding URLs of your site!

2. How can I get the email address from the X users when using the v2 API version?

Currently it is not possible to get the user’s email address when using the v2 API version, as X doesn’t offer a scope that requests access to this resources, and by default the email address is not returned, unfortunately.

Common error messages returned by X during verification

Callback url has been locked

The problem is that the value that was entered into the “Callback URI / Redirect URL” field is not correct for your app. Check the 15th step of the App setup to fix the problem.

oauth_callback value ‘oob’

The problem is that the value that was entered into the “Callback URI / Redirect URL” field is not correct for your app. Check the 15th step of the App setup to fix the problem.

Not a valid callback URL format

The problem is that the value that was entered into the “Callback URI / Redirect URL” field is not correct for your app or it may contain whitespace character. Check the 15th step of the App setup to fix the problem.

Could not authenticate you

The entered API Key is not correct. Maybe the app with the entered ID was deleted. Go to the X provider → Settings and make sure that an existing App’s API Key and API Key Secret was entered.