Per-network publication limits
Every limit a publication is validated against, indexed by limit and then by network.
Read it before building a composer. A few traps worth knowing:
• characters is not always the only text limit. Bluesky counts 300 graphemes and 3.000 bytes; the second one travels in max_post_bytes, where 0 means "this network does not measure text in bytes". A family emoji is one grapheme and eleven UTF-16 units, so counting with String.length is wrong in both directions. • 0 in title_characters means the network has no title field, not a title of zero length. • comment_characters is a different limit from characters. Facebook takes 63.206 in a post and 8.000 in a comment. • characters is not one number per network either. Telegram takes 4.096 in a text post and 1.024 in the caption of a photo or a video, and it is the same composer field: the second number is the key telegram_media. Over the limit the publication is created in state withErrors with publication_errors[].code = 967, which carries characters, max_characters and has_media. • Every network in /social_networks appears in every map. A missing key is a bug, and the backend's conformance suite fails on it.
Request
- Base URL: https://api.planvortex.com/v1.0.0
- URL: https://api.planvortex.com/v1.0.0/social_limits
- Auth: one of:
- HTTP bearer
- OAuth 2 (client credentials, token URL https://api.planvortex.com/v1.0.0/oauth/token)
Response
Limits per network
Changes
No recorded changes to this operation across all 1 revision of this API.