Sign inGet started
Docs
Get started

Inoreader API Authentication

How to authenticate Inoreader API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes Inoreader tokens for you.

Every Inoreader API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Inoreader account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

  1. Create a MindCloud account at app.mindcloud.co if you do not already have one.
  2. Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
  3. Create a Inoreader connection in Connections. Inoreader uses OAuth. When you create the connection, you are redirected to sign in to Inoreader and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
  4. Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Inoreader account that should run the action. MindCloud stores and refreshes the Inoreader credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling Get User Information with an Inoreader connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/inoreader/actions/get-user-information/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "arguments": {}
}'

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Inoreader account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect your Inoreader account

You need an Inoreader account and a registered Inoreader application before MindCloud can open the OAuth consent screen.

  1. Register an Inoreader application

    Open the Inoreader developer portal registration guide and follow the Create new application flow from your Inoreader preferences.

  2. Copy your OAuth client credentials

    From your application registration settings, copy the Client ID and Client Secret that Inoreader says are required for OAuth 2.0.

  3. Confirm your redirect URI

    Make sure the redirect URI configured in your Inoreader app matches the one used during the OAuth connection flow. Inoreader requires the redirect URI to match exactly.

  4. Connect from MindCloud

    Back in MindCloud, enter the Client ID and Client Secret, then continue through the Inoreader consent screen.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.