Skip to main content
All functions on Outerscope are accessible via POST requests, unless marked private by prefixing the function name with an underscore (e.g. _private_function()). Authenticate using the JWT token from the API Keys section of the dashboard. Endpoints require this token only when Outerscope.toml sets disable_auth = false. Authentication is disabled by default.

​
Request format

The POST request follows the structure below, where {function} is the name of the function to invoke. This example calls predict() from main.py.
Regioned hostnames such as https://api.aws.us-east-1.Outerscope continue to work. Requests to these hostnames are proxied to the global router, which can add latency. Use https://api.Outerscope for the lowest-latency path.

​
Response format

Responses follow this format:

​
Status codes

  • 200 → the function completed successfully
  • 401 / 403 → authentication or authorization failed
  • 404 → the app or function path could not be found
  • 5xx → either your app raised an exception or the platform could not complete the request
To return a custom status code such as 422 or 404, include a status_code field in the JSON response from main.py.
When debugging a failed request, check the HTTP status code and the app logs in the Outerscope dashboard. Inspecting the request payload, logs, and run_id together speeds up diagnosis.