Signatures
Save sign-offs once and add them to every post when it goes out.
A signature is a saved sign-off, such as "Team Acme · acme.com". When a post goes out, SociaHive adds the signature after a blank line. Set a default for all accounts or for some accounts, and pick another one (or none) on any post.
Signatures are on every plan.
How a post gets its signature
For each platform of a post, platform_overrides[platform].signature_id decides:
| Value | Signature |
|---|---|
| absent | The default for the account. A default for that account wins over a default for all accounts. |
| a signature id | That signature. If it was deleted, none. |
"none" | None. |
The signature goes at the end of the post text, or at the end of the last thread part when the post is a thread. It never goes on the first comment, an X Article, a story, or a TikTok "remind me" post.
The signature counts toward the platform's character limit. A post that fits without it but not with it is refused when it is scheduled ("Text is 287 characters; X allows 280."), so it never fails at publish. A retried publish sends the same text, with the signature once.
Limits: 20 signatures per user, 500 characters each, names up to 60 characters.
REST API
All under /api/v1/signatures, posts:read to list and posts:write to change:
| Method | Path | Body |
|---|---|---|
GET | /signatures | |
POST | /signatures | { name, text, account_ids?: "all" | string[], is_default?: boolean } |
PATCH | /signatures/{id} | any of the create fields |
DELETE | /signatures/{id} |
Saving a default turns off the default it replaces: one default for all accounts, and one per account.
Pick one on a post with signature_id in platform_overrides when you create or update it.
Agent tools
| Tool | What it does |
|---|---|
list_signatures | The user's signatures, which accounts each applies to, and which is the default. |
create_signature | Saves a signature. Nothing is posted. |
create_scheduled_post and update_scheduled_post take signatureId (an id, or "none").