late 0.0.1113

API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal. Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema). Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

# ConnectDiscordChannelRequest

## Properties

Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**guild_id** | **String** | Discord server (guild) the channel belongs to | 
**channel_id** | Option<**String**> | Text, announcement or forum channel to publish to. Send this or channelIds, not both. | [optional]
**channel_ids** | Option<**Vec<String>**> | Several channels of the server to connect, each as its own account. With two or more distinct ids the response lists `accounts` and `failed` instead of `account`. A single id behaves exactly like channelId. | [optional]
**profile_id** | **String** | Profile to connect the channel to | 
**redirect_url** | Option<**String**> | channelIds only: a URL to return in `redirect_url`, with `connected`, `profileId`, `accountId` and `accountIds` appended. | [optional]

[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)