---
url: /kb/show-self-service/integrations/sso-registration.md
---

# SSO registration

Your server registers a participant with a form POST and can log them straight into the webcast. This is not OpenID Connect. There is no redirect to an identity provider. Your system already knows who the person is.

The same endpoint covers two modes. Email is the unique key for a person on the event, so calling again for the same email is normal.

## Registration and login

Use this when the person should enter the webcast now. Leave `password` out.

1. The person is already signed in on your system.
2. Your server POSTs their email, name, and the event id.
3. The response is a one-time login URL.
4. Send the browser to that URL. They are logged in.

Call it at the moment they should watch. You do not need an earlier registration call. Call it again on the next visit.

## Registration only

Use this when your system can create the account, but cannot send the person to the login URL when the webcast starts. They sign in later on the event login page.

Include `password`. The response is still a login URL. Do not send the person there. They sign in with that email and password.

Send the request when they register, so the account exists before they try to log in. Without `password`, the account is created and they cannot sign in on the login page.

## Credentials

MEETYOO issues a **Client ID** and a **Client secret**. In the form body those fields are named `registrar` and `registrarpw`.

The credential must be turned on for that event. A credential that works on one event is rejected on another until it is activated there.

[Webhook registration](/integrations/webhook-registration) creates users with the same kind of credential. It does not return a login link. People then sign in with a password.

## Request

`POST https://webcast.meetyoo.de/myubi/v1/register`

`Content-Type: application/x-www-form-urlencoded`

Send form fields, not JSON.

| Field | Required | Notes |
|---|---|---|
| `registrar` | yes | Client ID |
| `registrarpw` | yes | Client secret |
| `email` | yes | Unique key for this person on the event |
| `event` | yes | Webcast event id |
| `firstname` | one of the two names | Stored only when this email is new |
| `lastname` | one of the two names | Stored only when this email is new |
| `password` | registration only | Omit for registration and login |
| custom fields | no | Field names must be enabled by MEETYOO first |

Send a first name, a last name, or both, on every call, including later logins. If both are empty the request is rejected. Name, password, and custom properties are written only the first time that email is seen. A later call does not change them.

Custom properties (for example company, country, or job title) are optional. Ask MEETYOO to allow each field name, then send it as its own form field. If the person already exists, you can still send the fields; they are ignored.

```bash
curl --location 'https://webcast.meetyoo.de/myubi/v1/register' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'registrar=YOUR_CLIENT_ID' \
  --data-urlencode 'registrarpw=YOUR_CLIENT_SECRET' \
  --data-urlencode 'email=participant@example.com' \
  --data-urlencode 'event=YOUR_EVENT_ID' \
  --data-urlencode 'firstname=Tim' \
  --data-urlencode 'lastname=Adelmann'
```

Registration only adds `--data-urlencode 'password=THE_PASSWORD'`.

A custom field that MEETYOO has allowed, for example `company`, is another `--data-urlencode 'company=ACME'`.

## Response

`200` and a plain-text URL, not JSON:

`https://webcast.meetyoo.de/index.html?e=YOUR_EVENT_ID&lt=ONE_TIME_TOKEN`

Open it immediately. It logs that person in once. Request a new URL for the next visit. For registration only, ignore this URL.

| Status | Meaning |
|---|---|
| 200 | Login URL in the body |
| 403 | Client ID or secret rejected, both names empty, or password too long |
| 404 | Unknown event id |
| 500 | `email` or `event` missing |

## Configure in ContentHub Admin

Credentials live on the hub. Turn them on per event.

## Request credentials

1. Open **Settings** → **Integrations**.
2. On the **SSO** card, choose **Request SSO credentials** (Starter and above; Free shows an upgrade prompt).
3. When they are issued, copy **Client ID** and **Client secret**.

A request emails ops. It is not instant.

## Activate on the event

1. Open the event. Under **Event Configuration** → **General**, open the **Access** tab.
2. Set access to **Registration**. The **Webhook and SSO registration** block is hidden otherwise.
3. Turn on the credential you will send as `registrar`.
4. Choose **Save**.

For registration only, you can select **Disable registration page**. People are not offered the public form. They still sign in on the event login page with the password you sent.

The **SSO login link** on an SSO credential is OpenID Connect. Do not use it for this form POST. Webhook URLs on a webhook credential are a different path: they do not return a login link.

## See also

* [Webhook registration](/integrations/webhook-registration)
