Idukki
Skip to content
Developers + API

Authenticate with OAuth

When to use OAuth instead of an API key, and how the authorisation flow connects an account to your app.

4 min read · last updated 2026-05

API keys are right for server-to-server access you control. OAuth is right when a user grants your app access to their workspace, so you act on their behalf without holding their credentials.

Run the OAuth flow

  1. Register your app. Create an app in Settings → Developers and note your client ID and secret.
  2. Redirect to authorise. Send the user to the authorisation URL with your client ID and redirect URI.
  3. Exchange the code. After the user approves, exchange the returned code for an access token.
  4. Call the API. Use the access token as a bearer token, and refresh it when it expires.
Was this page helpful?

Still stuck?

Email us at support@idukki.io or open the in-app chat. We answer within one working day.

Talk to a human

Related guides

4-min setupDTC + B2B brands37 KB runtimeReal G2 reviews

Stuck?

A real human is faster than a search box.

In-app chat replies under 5 minutes during EU + US business hours. Status of a ticket? Email support@idukki.io and we’ll surface it.

  • No credit card
  • Cancel anytime
  • SOC 2 + GDPR

Where Idukki ships

Same data model. Every surface a shopper meets.

We use cookies

We use essential cookies to run this site and optional analytics cookies to understand how it’s used. You can change your choice anytime in our privacy policy.

Authenticate with OAuth. Help — Idukki