Uploading and Managing IDLs
Orquestra allows you to upload Anchor Interface Definition Language (IDL) files to automatically generate APIs for building Solana transactions. This guide covers uploading, versioning, and managing your IDLs.Prerequisites
- An Orquestra account (sign in via GitHub)
- An Anchor IDL JSON file for your Solana program
- Your program’s on-chain address (Program ID)
Uploading via Dashboard
Fill in Project Details
- Name: A descriptive name for your project
- Description: Optional description of your program
- Program ID: Your Solana program’s public key
- Visibility: Choose public or private
Upload Your IDL
Paste your Anchor IDL JSON or upload the file directly. The IDL will be validated automatically.
Public projects are discoverable by anyone and can be used via the API without authentication. Private projects are only accessible to you.
Uploading via API
You can programmatically upload IDLs using the REST API:Endpoint
Authentication
Requires a Bearer token (JWT) from GitHub OAuth login.Request Body
Response
IDL Validation
Orquestra automatically validates your IDL structure. Common validation checks include:- Required fields (
name,version,instructions) - Account metadata structure
- Type definitions and references
- PDA seed configurations
Size Limits
- Maximum IDL size: 10 MB
- Maximum CPI.md size: 5 MB
IDL Versioning
Orquestra maintains a complete version history of your IDL. Every time you update your IDL, a new version is created.Updating an IDL
Response
Listing All Versions
Response
Retrieving a Specific Version
By default, the API returns the latest version. To fetch a specific version:Rate Limits
IDL uploads are rate-limited to prevent abuse:- 10 requests per minute per IP address
Deleting a Project
Deleting a project removes all IDL versions, API keys, and cached data. This action is irreversible.You must provide the exact project name as confirmation to prevent accidental deletions.
Best Practices
- Use descriptive names: Make it easy to identify projects in your dashboard
- Keep IDLs in sync: Update your Orquestra IDL whenever you redeploy your program
- Version thoughtfully: Each update creates a new version, so group related changes
- Add CPI docs: If others will integrate with your program, provide clear CPI documentation
- Test with private projects: Use private visibility while developing, then make public when ready
Next Steps
Building Transactions
Learn how to use your uploaded IDL to build transactions
API Keys
Create API keys for programmatic access
AI Documentation
Explore auto-generated Markdown docs for AI agents