Get API key

Papers and Tallies are public and don’t require an API key. All other Scite endpoints require an API key. You must create at least one API key to use Scite through code.

Looking for SAML, SSO, IP-based access, or OpenAthens? See Enterprise access and SSO. This page covers credentials for the Scite API.

Choose an authentication option

API key

Create a key in the API Console and send it directly with each request. No token exchange is required.

Enterprise credentials

Exchange a Scite-issued client_id and client_secret for a short-lived access token.

Option	Best for	How it works
API key	Individual users and lower-volume integrations	Create a key in the API Console and send it directly with each request.
Enterprise credentials	Organizations with high-volume or managed server-to-server integrations	Exchange a Scite-issued `client_id` and `client_secret` for a two-hour access token.

If you’re an individual developer, start with a API key. Enterprise access is intended primarily for organizations that need higher usage limits or managed credentials.

API keys

Create and manage keys in the API Console. Self-service API keys require a Pro plan.

Create and copy a key

Choose the scopes your integration needs, then copy the key when it appears. Scite only shows the full key once.

Send the key

Add the key to the Authorization header:

export SCITE_API_KEY='<YOUR_API_KEY>'

curl -G 'https://api.scite.ai/api_partner/search' \
  -H "Authorization: Bearer $SCITE_API_KEY" \
  --data-urlencode 'term=CRISPR' \
  --data-urlencode 'limit=1'

The API Console only shows scopes available to your account. Creating a key does not grant access to additional features. Use the narrowest scopes your integration needs.

Enterprise credentials

Enterprise authentication is for organizations that need higher usage limits or managed server-to-server credentials. Contact sales to get a client_id and client_secret.

Request an access token

Exchange your credentials at the token endpoint:

curl -X POST 'https://api.scite.ai/auth_token_users/token' \
  -H 'Content-Type: application/json' \
  -d '{
    "client_id": "<YOUR_CLIENT_ID>",
    "client_secret": "<YOUR_CLIENT_SECRET>",
    "grant_type": "client_credentials"
  }'

The response includes an access_token. It expires after two hours.

Send the access token

Add the token to the same Authorization header:

curl -G 'https://api.scite.ai/api_partner/search' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  --data-urlencode 'term=CRISPR' \
  --data-urlencode 'limit=1'

Keep API keys and Enterprise credentials out of source control and client-side code. Store them in an environment variable or secret manager.

Authentication errors

401 Unauthorized means the credential is missing, invalid, expired, or revoked.
403 User not authorized means the credential is valid, but the account or key lacks access to that feature.

See Errors and rate limits for troubleshooting. For MCP clients, see Scite MCP authentication.

Get Started

Concepts

Guides

MCP

Reference

Choose an authentication option

API key

Enterprise credentials

API keys

Enterprise credentials

Authentication errors

​Choose an authentication option

API key

Enterprise credentials

​API keys

​Enterprise credentials

​Authentication errors

Choose an authentication option

API keys

Enterprise credentials

Authentication errors