Skip to main content
The Runpod REST API v2 provides programmatic access to your Runpod resources over standard HTTP. Use it to create and manage Pods, query Serverless endpoints, provision storage, and retrieve billing data — without using the console.
If you have an existing REST v1 or GraphQL integration, run /runpod:migrate with the Runpod skills plugin installed in your coding agent to migrate it to v2 automatically. See the migration guide for details.

​
Base URL

The Runpod REST API v2 provides programmatic access to all Runpod compute resources. Integrate GPU infrastructure into your applications, workflows, and automation systems.

​
Available resources

  • Pods: Create and manage persistent GPU instances for development, training, and long-running workloads.
  • Serverless: Deploy and scale containerized applications with autoscaling and job monitoring.
  • Templates: Save and reuse Pod and endpoint configurations.
  • Network volumes: Create persistent storage attachable to multiple resources.
  • Container registry auth: Connect to private Docker registries.
  • Catalog: Browse available GPU types, CPU types, and data centers.
  • Billing: Access usage metrics and billing information.

​
Authentication

All requests require a Runpod API key in the request headers. The API uses standard HTTP methods and returns JSON responses.

​
Rate limits

The API limits how many requests each user can send per minute, hour, and day. Responses include RateLimit headers that report your remaining quota, and requests over the limit return 429 Too Many Requests. To learn how to read these headers and build a client that handles them, see Rate limits.

​
OpenAPI schema

Retrieve the complete OpenAPI specification for client generation, request validation, or tooling integration.
Last modified on October 13, 2026