Hootsuite

Hootsuite is a comprehensive social media management platform that enables businesses to schedule posts, monitor conversations, analyze performance, and manage multiple social media accounts from a single dashboard, helping organizations build and maintain their social media presence effectively.

Power end-to-end data operations for your Hootsuite API with Nexla. Our bi-directional Hootsuite connector is purpose-built for Hootsuite, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Hootsuite or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Hootsuite workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Hootsuite credential, you need to have a Hootsuite account and create an OAuth2 application in your Hootsuite account settings to obtain OAuth2 credentials (Client ID and Client Secret). The OAuth2 credentials are required to authenticate with the Hootsuite API.

To obtain OAuth2 credentials, you need to create an OAuth2 application in your Hootsuite account settings. Once the application is created, you can obtain the Client ID and Client Secret. The OAuth2 credentials include a Client ID and Client Secret that are used to authenticate API requests. You can also configure access scopes to control what permissions the application has. For detailed information about setting up OAuth2 credentials and creating OAuth2 applications, refer to the Hootsuite API OAuth2 documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	Yes	Hootsuite Client ID
Access Scope	No	No	Hootsuite Access Scope
Client Secret	No	Yes	Hootsuite Client Secret for Token URL

Create a credential in Nexla

1. To create a new Hootsuite credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Hootsuite

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

OAuth2 Authentication

Hootsuite uses OAuth2 authentication to securely access the Hootsuite API. OAuth2 is an industry-standard authorization protocol that allows applications to access user data without requiring users to share their passwords.

3. Enter your Hootsuite Client ID in the Client ID field. This is the Client ID you obtained from your Hootsuite OAuth2 application settings.

4. Optionally, enter the access scope for your Hootsuite credential in the Access Scope field. The access scope determines what permissions the application has when accessing your Hootsuite account. If not specified, the default scope will be used.

5. Enter your Hootsuite Client Secret in the Client Secret field. This is the Client Secret you obtained from your Hootsuite OAuth2 application settings.

6. Click the Authorize button to begin the OAuth2 authorization flow. This will redirect you to Hootsuite's authorization page where you will be asked to sign in with your Hootsuite account and grant permissions to Nexla to access your Hootsuite data.

   During the OAuth2 authorization flow, you will be redirected to Hootsuite's authorization page. You must sign in with a Hootsuite account that has access to the Hootsuite organization you want to connect. After signing in, you will be asked to grant permissions to Nexla to access your Hootsuite data. The access scope you configured determines what permissions are requested. Once you grant permissions, you will be redirected back to Nexla, and the authorization will be completed automatically.

7. After completing the OAuth2 authorization flow, Nexla will automatically obtain and store the access token and refresh token needed to authenticate API requests. The access token is used to authenticate each API request, and the refresh token is used to obtain new access tokens when the current access token expires.

   OAuth2 access tokens expire after a certain period for security reasons. Nexla automatically refreshes expired access tokens using the refresh token, so you typically do not need to re-authorize unless you revoke access or the refresh token expires. The access token is sent in the Authorization header with the Bearer prefix for all API requests to the Hootsuite API. For detailed information about OAuth2 authentication and token management, see the Hootsuite API documentation.

8. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Hootsuite connector tile, then select the credential that will be used to connect to the Hootsuite account, and click Next; or, create a new Hootsuite credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Hootsuite endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Get Interactions

Retrieves the interactions between two users of a particular social network type such as direct messages, comments, and posts. This API is only available to Enterprise users.

• Select the social network type from the Social Network Type dropdown menu. Valid options are facebook and twitter. The default value is facebook if not specified. The social network type determines which social network platform's interactions will be retrieved.
• Enter the social network ID of the user owned by the calling member or organization in the Social Network ID field. This should be the ID from the social network itself (e.g., Facebook Page ID or Twitter User ID), not the Hootsuite social profile ID.
• Enter the social network ID of the target user whose interactions with your social profile you are interested in in the Target Social Network Id field. This should be the ID from the social network itself (e.g., Facebook User ID or Twitter User ID), not the Hootsuite social profile ID.
• The endpoint uses GET requests to https://platform.hootsuite.com/v1/interactions/{social_network_type}?socialNetworkId={social_network_id}&targetSocialNetworkId={target_social_network_id} where {social_network_type} is the Social Network Type you select, {social_network_id} is the Social Network ID you provide, and {target_social_network_id} is the Target Social Network Id you provide. The endpoint URL is automatically constructed based on the Hootsuite API base URL and all the parameters.
• The endpoint uses token-based pagination (iteration.type: paging.next.token) through the cursor mechanism. The response data path is $.data.interactions[*], which extracts all items from the interactions array in the API response. Additional metadata is also included from $.data.metadata.
• When a response includes a cursor.next value in the metadata, Nexla automatically uses it as the cursor parameter for the subsequent request to fetch the next page of results until all interactions have been retrieved.

This endpoint retrieves interactions between two users on a specific social network platform. The endpoint supports Facebook and Twitter social networks. This API is only available to Enterprise users, so you must have an Enterprise Hootsuite account to use this endpoint. The endpoint supports pagination through the cursor mechanism, which allows you to retrieve large lists of interactions efficiently. The response includes metadata that indicates the current cursor and next cursor available. For detailed information about the API response format and available fields, see the Hootsuite API documentation.

Retrieve outbound messages

Outbound messages are messages that are scheduled or were previously sent. This endpoint returns outbound messages sorted by increasing scheduled send time.

• Enter the start date range of messages to be returned in the startTime field. This should be in ISO-8601 format (e.g., 2024-01-01T00:00:00Z). The start time determines the beginning of the date range for retrieving messages.
• Optionally, enter the end date range of messages to be returned in the endTime field. This should be in ISO-8601 format (e.g., 2024-01-31T23:59:59Z). The end time must not be later than 4 weeks from the start time. If not specified, messages up to 4 weeks from the start time will be retrieved.
• Optionally, select or enter the state filter for messages in the state field. Available options include PENDING_APPROVAL, REJECTED, SENT, SCHEDULED, and SEND_FAILED_PERMANENTLY. You can also add custom state values if needed. The default value is SCHEDULED if not specified. The state filter determines which message states will be included in the results.
• The endpoint uses GET requests to https://platform.hootsuite.com/v1/messages?startTime={start_time}&endTime={end_time}&state={state} where {start_time} is the startTime you provide, {end_time} is the endTime you provide, and {state} is the state you provide. The endpoint URL is automatically constructed based on the Hootsuite API base URL and all the query parameters.
• The endpoint uses token-based pagination (iteration.type: paging.next.token) through the cursor mechanism. The response data path is $.data.interactions[*], which extracts all items from the interactions array in the API response. Additional metadata is also included from $.data.metadata.
• When a response includes a cursor value in the metadata, Nexla automatically uses it as the cursor parameter for the subsequent request to fetch the next page of results until all messages have been retrieved.

This endpoint retrieves outbound messages (messages that are scheduled or were previously sent) from your Hootsuite account. Messages are returned sorted by increasing scheduled send time. The endpoint supports filtering by date range (start time and end time) and message state. The end time must not be later than 4 weeks from the start time. The endpoint supports pagination through the cursor mechanism, which allows you to retrieve large lists of messages efficiently. The response includes metadata that indicates the current cursor and next cursor available. For detailed information about the API response format and available fields, see the Hootsuite API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Hootsuite data sources can also be manually configured to ingest data from any valid Hootsuite API endpoint not covered by the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method and endpoint URL. Hootsuite API endpoints typically follow the pattern https://platform.hootsuite.com/v1/{endpoint_path}.

The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about Hootsuite API endpoints and available APIs, see the Hootsuite API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Hootsuite data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Hootsuite destination, and select the Send to Destination option from the menu. Select the Hootsuite connector from the list of available destination connectors, then select the credential that will be used to connect to the Hootsuite organization, and click Next; or, create a new Hootsuite credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Hootsuite endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Member

Creates a member in a Hootsuite organization. Requires organization manage members permission.

• This endpoint automatically creates a new member in your Hootsuite organization using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses POST requests to https://platform.hootsuite.com/v1/members. The endpoint URL is automatically constructed based on the Hootsuite API base URL.
• The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the member data to create.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a member. If you need to create multiple members, you can send multiple records, but each will be processed as a separate request.
• This endpoint automatically creates a data source to track the responses received from the Hootsuite API after each call.

The request body must be properly formatted JSON that matches the Hootsuite API specification for creating members. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. This endpoint requires organization manage members permission, so your OAuth2 credentials must have the appropriate permissions. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. This endpoint automatically creates a data source to track creation responses. For detailed information about creating members, including required fields, field names, and request formats, see the Hootsuite API documentation.

Add member to team

Adds a member to a team.

• Enter the organization ID in the organizationId field. This should be the unique identifier for the Hootsuite organization that contains the team you want to add the member to.
• Enter the team ID in the teamId field. This should be the unique identifier for the team you want to add the member to.
• Enter the member ID in the memberId field. This should be the unique identifier for the member you want to add to the team.
• The endpoint uses POST requests to https://platform.hootsuite.com/v1/organizations/{organization_id}/teams/{team_id}/members/{member_id} where {organization_id} is the organizationId you provide, {team_id} is the teamId you provide, and {member_id} is the memberId you provide. The endpoint URL is automatically constructed based on the Hootsuite API base URL and all the path parameters.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to add a member to a team. If you need to add multiple members to teams, you can send multiple records, but each will be processed as a separate request.
• This endpoint does not automatically create a data source to track the responses received from the Hootsuite API after each call.

The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. You must provide the organization ID, team ID, and member ID to add a member to a team. The member must already exist in the organization before they can be added to a team. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about adding members to teams, including required fields and request formats, see the Hootsuite API documentation.

Manual configuration

Hootsuite destinations can also be manually configured to send data to any valid Hootsuite API endpoint not covered by the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, and request headers. Hootsuite API endpoints typically follow the pattern https://platform.hootsuite.com/v1/{endpoint_path}.

The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Hootsuite API typically uses JSON format for request bodies. For detailed information about Hootsuite API endpoints and available APIs, see the Hootsuite API documentation.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Hootsuite endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Hootsuite endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.