Create a brand

Creates a brand: the top-level object in the Social API. A brand owns the social accounts you connect to it and every post published from them. Nothing else in the Social API can be called until at least one brand exists, so this is the first request in any Social integration.

Use case: onboarding a client into social publishing. When a customer signs up in your product, create one brand per business they want to publish for. Store the returned socialProfile.id against your own record of that business: it is the brandId path token in POST /social/brands/{brandId}/connections/link and GET /social/brands/{brandId}/posts, and the socialProfileId body field on every post you create. Then send the user through the hosted connection link for each platform they want to publish to.

Notes.

• The request body must be wrapped in an input object. Every write in the Social API is wrapped this way, with one exception: the connection link takes a flat body.
• Check success, not the HTTP status. A validation failure — a missing profileName or an unknown timezone.tzCode — comes back as HTTP 200 with success: false and the reason in error. Only treat the call as successful when success is true.
• Only profileName and timezone are required. businessIntent and categories default to general and an empty list, so an integration that has no equivalent of those fields can leave them out entirely.
• timezone.tzCode is not decoration. A post scheduled with scheduleDate + scheduleTime is interpreted in the brand's zone, not the caller's and not UTC. Changing it later does not re-time posts already scheduled.
• The brand always belongs to the account behind the API key. There is no way to create a brand in another account: any account identifier in the body is ignored.
• Brand IDs are plain UUIDs. They are not the Base64 relay IDs used by Locations and location Posts, so do not encode or decode them. The same ID appears as the brandId path token and as the socialProfileId body field: brandId is only ever a URL token, never a body field.
• There is no brand limit on an API plan. Brands are unlimited and unmetered, so this call is never refused for a cap and you do not need to check headroom before creating one. What is metered is connections — one social account linked to one brand on one network. See Plans and add-ons for the connection tiers and the price of a connection pack, and GET /social/limits to read your connection headroom before you send a user through a connection link.

Write operation: not executed against the live account. The request and response shown are built from the API schema.