API Connections

Two pages under Organization Settings → Other Integrations control programmatic access to your account. They work in opposite directions, which is the main thing to keep straight:

Page	Direction
API Accounts	Another system acts on your behalf — registering participants for you
OAuth Connections	Another service has been granted read access to your data

Both hand out access to your account

Anything listed on either page can act against your data until you remove it. Review them when a vendor relationship ends or a staff member who set one up leaves.

API Accounts (Basic Auth)

Add an API Account to enable external systems to register participants on your behalf.

This is the credential you hand to a third-party system — an association website, a registration portal, a custom integration — so it can register people into your courses directly.

Creating one

Click Add an API Account.

• Account Nickname

  What this credential is for. Name it after the system that will use it, so the list stays readable when there are several.

• Used By

  The membership account these credentials operate as. This ties API-created registrations to the right membership connection.

Save, then use Copy Token to get the token to give to the other system.

Treat the token like a password

It registers participants into your account and consumes your participant bank. Send it over something private, never in a shared document or a ticket. If a token may have leaked, delete that API Account and issue a new one — deleting immediately stops it working.

One account per integration

Give each system its own API Account rather than sharing one. Then revoking access to a single vendor doesn't break everything else.

OAuth Connections

OAuth connections allow external services to interact with your LecturePanda Account.

This page lists services you granted access to, showing each one's name, logo, and the exact permissions it was given.

There is no Add button here — entries appear when you go through an external service's connection flow and approve the consent screen. This page is where you review and revoke afterwards.

To revoke, delete the connection. The service's access stops immediately, and it would need you to approve a fresh consent screen to return.

Building an integration?

This page is the administrator's side of the OAuth flow. For the developer-facing reference — scopes, endpoints, token exchange — see the OAuth API.