Scheme and host (and port), e.g. https://app.example.com; at most 20.
Requires the write scope. Owner key or session only: a profile key gets 403 owner_key_required.
bearerAuthorizationBearer <token>An API key (tb_live_...) from the dashboard, or an OAuth access token.
application/json- body
origin*string1 <= length <= 300Already allowed.
application/json- response
id*stringuuidorigin*stringcreated_at*stringdate-timecurl -X POST 'https://api.mulaichat.com/v1/connect/redirect-origins' \ -H 'Content-Type: application/json' \ -d '{ "origin": "string"}'{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "origin": "string", "created_at": "2019-08-24T14:15:22Z"}Set the reply status PATCH
Requires the write scope.
Create a connect link POST
A page where your client connects their accounts into the profile ({id} may be its external_id). redirect_url's origin must be allowed in /v1/connect/redirect-origins (422 redirect_origin_not_allowed); state comes back unchanged. headless: true (for accounts Mulaichat approved, else 403 headless_not_approved; redirect_url required, else 400 redirect_url_required) answers start_urls for the platforms that can connect now (none: 422 platform_not_supported): the client goes straight to the platform's login and back to redirect_url without a Mulaichat page, and a Facebook login connects every Page it grants. Tell your clients their account connects through Mulaichat: the platform's consent screen names Mulaichat. Requires the write scope. Owner key or session only: a profile key gets 403 owner_key_required.