How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hootsuite Authentication API

Hootsuite uses OAuth2 to authenticate end users. Members authenticated with the Hootsuite API are subject to the same permissions configured as when using the Hootsuite Web Dashboard. Learn more about managing permissions at the [Hootsuite Help Center](https://help.hootsuite.com/hc/en-us/articles/204598170-About-organizations-teams-and-permissions).

Hootsuite Authentication API is one of 21 APIs that Hootsuite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://platform.hootsuite.com.

2 operations 2 paths 2 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://platform.hootsuite.com/v1
Authentication
OAuth 2.0, HTTP Basic
Resource Areas
1

Authentication & Security 2

Hootsuite Authentication API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 2 scopes. It accepts HTTP basic authentication (Basic_Auth). By default, every request must be authenticated.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Authentication 2

Hootsuite uses OAuth2 to authenticate end users. Members authenticated with the Hootsuite API are subject to the same permissions configured as when using the Hootsuite Web Dashbo…

GET
/oauth2/auth
OAuth2 Authorize
oauth2Authorize 5 params → 200
POST
/oauth2/token
OAuth2 Token
oauth2Token 1 param body → 200400401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are OAuth2BearerToken (5 properties), OAuthError (4 properties). Each schema is shown below with its type and property counts.

OAuth2BearerToken
object
5 properties
OAuthError
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hootsuite-authentication-api-openapi.yml Raw ↑

Other APIs Hootsuite publishes across the network.

Hootsuite Developer Documentation MCP
Hootsuite Analytics API
Hootsuite Comments API
Hootsuite CRM Rest API
Hootsuite CRM Webhooks API
Hootsuite Me API
Hootsuite Media API
Hootsuite Members API
Hootsuite Messages API
Hootsuite Organizations API
Hootsuite Proactive Messaging Rest API
Hootsuite Queue Rest API
Where this information came from

This is an independent, third-party profile of Hootsuite Authentication API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.