REST API Authentication
Create and use a Screpy REST API key.
Screpy REST API requests use a bearer API key. Create a key in Settings → Connected Apps, then store it in your server-side environment.
Send the key
curl --request GET 'https://api.screpy.com/v1/account' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY'Keep keys server-side
Do not expose API keys in browser code, mobile apps, public repositories, or client-side configuration. Read the key from a server-side environment variable or secret manager, then add the authorization header as your server makes the request.
REST API and MCP use different credentials
REST API keys authenticate requests to https://api.screpy.com/v1. They do not connect an MCP client. MCP clients use separate Screpy OAuth authorization, and MCP OAuth tokens cannot authenticate REST API requests.
This page documents Screpy's current REST API key flow. See Screpy's editorial policy for how product-specific guidance is reviewed and corrected.
Check access before building
Call account to identify the authenticated account and check current feature availability and allowances. Start with projects to discover the project UIDs this key can access.