Integrations

Identity Providers

Connect an external identity provider so your bidders are backed by a real identity system, while Basta handles the auction mechanics.

Basta does not manage end-user accounts for you. Instead, you bring your own users — and you can connect an external Identity Provider (IDP) to your Basta account so that bidders are backed by a real identity system.

This gives you a single source of truth for who your bidders are, while Basta handles the auction mechanics.

How it works

When an IDP is connected to your account:

Each bidder is represented by a user in Basta, linked to their identity in your IDP
A user can be referenced either by their Basta user ID or by their identity-provider ID
Profile details (such as display name and email) are sourced from the connected IDP
Credentials live in the IDP — Basta never stores end-user passwords

You then issue bidder tokens for these users so they can act on the Client API.

Supported identity providers

Provider	Status
Ory	Supported
More	On the way

Want to connect a specific identity provider? Get in touch— we're expanding support.

Referencing users

Many Management API operations accept a user ID together with an ID type, so you can address users by whichever identifier is convenient:

ID Type	Meaning
`USER_ID`	The user's Basta user ID
`IDENTITY_PROVIDER_ID`	The user's ID in your connected identity provider

GraphQL

query GetUser {
  user(
    accountId: "ACCOUNT_ID"
    userId: "IDP_USER_ID"
    idType: IDENTITY_PROVIDER_ID
  ) {
    id
    # profile fields are sourced from the connected IDP
  }
}

Without a connected IDP

You don't have to connect an IDP. If you manage users entirely on your own side, you can still issue bidder tokens with your own user identifiers — see Client API → Bidder Tokens. Connecting an IDP simply lets Basta resolve richer profile information and keep identities in sync.

How it works

Supported identity providers

Referencing users

Without a connected IDP

Related documentation