---
title: Configuring an adapter instance
description: Configure the Twitter IdP Adapter to determine how PingFederate communicates with Twitter.
component: twitter
page_id: twitter:setup:pf_twitter_cic_configuring_an_adapter_instance
canonical_url: https://docs.pingidentity.com/integrations/twitter/setup/pf_twitter_cic_configuring_an_adapter_instance.html
revdate: January 21, 2026
section_ids:
  steps: Steps
---

# Configuring an adapter instance

Configure the Twitter IdP Adapter to determine how PingFederate communicates with Twitter.

## Steps

1. In the PingFederate admin console, go to **Authentication > Integration > IdP Adapters**. Click **Create New Instance**.

2. On the **Type** tab, set the basic adapter instance attributes:

   1. In the **Instance Name** field, enter a name for the adapter instance.

   2. In the **Instance ID** field, enter a unique identifier for the adapter instance.

   3. In the **Type** list, select **Twitter IdP Adapter**. Click **Next**.

3. (Optional) On the **IdP Adapter** tab, in the **Attribute Selector** section, select or define attributes to request from Twitter.

   You can find a list of available attributes in [User Object](https://developer.twitter.com/en/docs/twitter-api/v1/data-dictionary/overview/user-object) in the Twitter documentation.

   1. Click **Add a new row to 'Attribute Selector'**.

   2. Select an attribute from the **Twitter Attribute** list or enter an attribute in the **Additional Twitter Attribute** field.

      |   |                                                                                                                                                                                                                                                                                                     |
      | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
      |   | You must use the correct syntax for manual entries. You can find an example of the data structure in [GET account/verify\_credentials](https://developer.twitter.com/en/docs/accounts-and-users/manage-account-settings/api-reference/get-account-verify_credentials) in the Twitter documentation. |

   3. In the **Action** column, click **Update**.

   4. To add more attributes, repeat steps a - c.

4. On the **IdP Adapter** tab, configure the adapter instance by referring to [Twitter IdP Adapter settings reference](pf_twitter_cic_twitter_idp_adapter_settings_reference.html). Click **Next**.

5. On the **Extended Contract** tab, add any attributes you want to include in the contract. Click **Next**.

6. On the **Adapter Attributes** tab, set pseudonym and masking options as shown in [Set pseudonym and masking options](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_setting_pseudonym_masking_options.html) in the PingFederate documentation. Click **Next**.

7. On the **Adapter Contract Mapping** tab, configure the contract fulfillment details for the adapter as shown in [Define the IdP adapter contract](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_authnadapterinstancetasklet_plugincontractstate.html) in the PingFederate documentation. Click **Next**.

8. On the **Summary** tab, check your configuration, then click **Save**.