Send chat requests with OAuth

Choose this path when a customer has authorized your application to use their selected ShareAI account. First complete authorization code with PKCE and obtain a grant that includes surcharge.

curl --fail-with-body https://api.shareai.now/api/v1/chat/completions \
  -H "Authorization: Bearer $SHAREAI_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"model":"MODEL_IDENTIFIER","messages":[{"role":"user","content":"Hello!"}],"stream":false}'

The access token goes in the Bearer header#

The chat endpoint and request body are the same as the API-key flow. The difference is the credential and its authorization lifecycle. A refresh token is sent only to the token endpoint; an ID token is used only for validated application sign-in.

Who pays and which plan applies?#

The accepted grant identifies the selected personal or organization account, application and usage plan. The service determines those values from the authorization. Do not send a payer ID, builder fee or another client’s subject in the chat body to change billing.

Renew access without losing consent#

When the access token expires, use the refresh flow on your backend and store the replacement refresh token. When the grant is revoked or new consent is required, reconnect the customer through the browser flow.

Failure handling#