List credentials
Lists the apps this org has sealed.
GET /v1/social/credentials
| Address | https://api.hanzo.ai/v1/social/credentials |
| Method | GET |
| Operation | get_social_credentials |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Lists the apps this org has sealed. The secret is not included.
Request
GET /v1/social/credentials takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | social.orgApps | ok |
default | problem-details | refused |
200 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
apps | body | social.orgApp[] | — | Apps is the org's sealed developer apps. |
apps[].clientId | body | string | — | ClientID is the public app id, in the clear. |
apps[].provider | body | string | — | Provider is the network: x, facebook, instagram, linkedin, tiktok, youtube or threads. |
apps[].secretSet | body | boolean | — | SecretSet is whether a secret is sealed for this app. |
data | body | social.orgApp[] | — | Data is Apps again, so a client that reads either envelope sees the list. |
data[].clientId | body | string | — | ClientID is the public app id, in the clear. |
data[].provider | body | string | — | Provider is the network: x, facebook, instagram, linkedin, tiktok, youtube or threads. |
data[].secretSet | body | boolean | — | SecretSet is whether a secret is sealed for this app. |
Failure carries the platform error shape — see Errors.
Examples
hanzo social credentials getimport { Configuration, SocialApi } from 'hanzoai';
const api = new SocialApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getSocialCredentials();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_credentials()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.SocialAPI.GetSocialCredentials(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_credentials(&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).getSocialCredentials();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/social/credentials \
-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"
}
}
}'