Skip to main content

Overview

The Giza API provides direct HTTP access to all agent services. This is the underlying API that powers the SDK.
For most use cases, we recommend using the TypeScript SDK which provides type safety, automatic authentication, and better error handling. Use the HTTP API directly when:
  • Building in a language without SDK support
  • Needing lower-level control
  • Integrating with existing HTTP infrastructure

Base URL

https://partners-backend-1038109371738.europe-west1.run.app

API Groups

Common Parameters

Chain ID

Most endpoints require a chain_id path parameter:
ChainID
Base8453
Ethereum1
Arbitrum42161
Polygon137
Base Sepolia84532
Sepolia11155111

Wallet Address

Wallet addresses must be valid Ethereum addresses:
  • Start with 0x
  • 42 characters total (0x + 40 hex characters)
  • Case-insensitive

Response Format

All successful responses return JSON with the following structure:
{
  "data": { ... }
}
Error responses follow this format:
{
  "detail": [
    {
      "loc": ["path", "wallet"],
      "msg": "Invalid wallet address",
      "type": "value_error"
    }
  ]
}

HTTP Status Codes

CodeDescription
200Success
201Created
204No Content (success with no response body)
400Bad Request - Invalid parameters
401Unauthorized - Invalid API key
403Forbidden - Access denied
404Not Found - Resource doesn’t exist
422Validation Error - Invalid input
500Internal Server Error
503Service Unavailable

Rate Limits

API requests are rate-limited per partner. If you exceed limits, you’ll receive a 429 Too Many Requests response.
Contact Giza to discuss rate limit increases for production use cases.

OpenAPI Specification

The complete API specification is available in OpenAPI 3.1 format:
https://partners-backend-1038109371738.europe-west1.run.app/api/v1/openapi.json
You can use this to:
  • Generate client libraries
  • Import into Postman
  • Validate requests

Interactive API Explorer

Swagger UI

Try API endpoints directly in the interactive Swagger documentation

Next Steps