List providers

Reports each supported network's publish-readiness: whether this deployment holds the OAuth application credentials for it and, when it does not, exactly which environment variables are missing.

GET /v1/social/providers

Social → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/social/providers`
Method	`GET`
Operation	`get_social_providers`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Reports each supported network's publish-readiness: whether this deployment holds the OAuth application credentials for it and, when it does not, exactly which environment variables are missing.

This is a live read of the deployment's own configuration, not a static list of networks — it answers "can I connect this today", which is what a connect affordance and a pre-cutover checklist both need. It says nothing about whether the caller has connected an account; that is the accounts listing.

Request

GET /v1/social/providers takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	social.socialProviders	ok
`default`	problem-details	refused

200 body — 4 fields.

Field	In	Type	Always	Description
`data`	body	social.socialProvider[]	—	Data is one row per supported network, in the product's fixed order: x, facebook, instagram, linkedin, tiktok, youtube, threads.
`data[].credentialsConfigured`	body	boolean	—	CredentialsConfigured is whether this deployment holds every OAuth application credential the network needs.
`data[].missingCredentials`	body	string[]	—	MissingCredentials names the environment variables still unset for this network, so the answer is an installation instruction rather than a refusal.
`data[].provider`	body	string	—	Provider is the network: x, facebook, instagram, linkedin, tiktok, youtube or threads.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo social providers

.ts

.py

.go

.rs

.java

import { Configuration, SocialApi } from 'hanzoai';

const api = new SocialApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getSocialProviders();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import SocialApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = SocialApi(client).get_social_providers()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.SocialAPI.GetSocialProviders(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, social_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = social_api::get_social_providers(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.SocialApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new SocialApi(client).getSocialProviders();

curl https://api.hanzo.ai/v1/social/providers \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches social through the social tool, which names its 13 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_social_accounts"
         }
       }
     }'

Social API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList posts NextList summary