Overview
The superglue API provides GraphQL endpoints for creating integrations, building workflows, and executing schema tests. This allows you to automate schema validation and integrate testing into your CI/CD pipeline.Authentication
All API requests require a bearer token in the Authorization header:Base Endpoint
Core Schema Testing Workflow
1. Create Test Integrations
First, set up integrations pointing to different versions of your API using theupsertIntegration
mutation:
2. Build and Test Workflows
Use thebuildAndRunWorkflow
mutation to create workflows that test your schemas:
3. Compare Schema Performance
Execute the same test against different schema versions:4. Save Successful Workflows
Save workflows that pass testing for future use:Complete Schema Testing Example
Hereβs a complete Node.js example that tests two schema versions and compares their performance:Testing Breaking Changes
Test existing workflows against new API versions to detect breaking changes:Advanced Testing Patterns
Batch Testing Multiple Use Cases
Performance Benchmarking
CI/CD Integration
GitHub Actions Example
Error Handling
Always include proper error handling in your schema tests:Best Practices
- Test Early and Often: Run schema tests on every API change
- Use Realistic Data: Test with production-like data volumes and structures
- Automate in CI/CD: Include schema testing in your deployment pipeline
- Monitor Performance: Track how schema changes affect integration complexity
- Document Results: Keep a record of schema decisions and their test outcomes
Rate Limits and Quotas
Be aware of API rate limits when running automated tests:- Maximum 100 requests per minute per API key
- Consider adding delays between batch operations
- Use exponential backoff for retries
Next Steps
- Explore the full GraphQL schema
- Learn about workflow building
- Use superglue via MCP
- Join our community for support and examples