- Automate Network Operations: Provision and manage network resources without manual intervention
- Build Custom Integrations: Connect DynamicLink with your existing tools, workflows, and systems
- Create Third-Party Applications: Develop applications that leverage DynamicLink’s network capabilities
- Implement Infrastructure as Code: Manage your network infrastructure through code and version control
- Enable CI/CD Pipelines: Integrate network provisioning into your deployment workflows
API reference documentation
For detailed information about specific endpoints, request/response formats, and examples, see the API Reference documentation.Key capabilities
- Tenant and user management
- Network infrastructure
- Cloud connections
- Routing and BGP
- Security services
- Network insights
- Monitoring and diagnostics
Authentication
All API requests require authentication using Bearer tokens. The API uses theHTTPBearerFromCookie security scheme, which supports tokens obtained through the authentication flow.
To get a Bearer token, you must request one from Zayo here: Zayo Developer Portal
API structure
The DynamicLink API follows RESTful conventions:- GET - Retrieve resources and query information
- POST - Create new resources
- PUT - Update existing resources
- DELETE - Remove resources
Examples
The DynamicLink API is designed to make integration straightforward. Here are common integration patterns:Automation workflows
Automate repetitive network management tasks:Infrastructure as code
Use the API with tools like Terraform, Ansible, or custom scripts to manage your network as code:Event-driven integrations
Build integrations that respond to network events and changes:Best practices
When building integrations with the DynamicLink API:- Use Idempotent Operations: Design your integration to handle retries safely
- Implement Proper Error Handling: Check HTTP status codes and handle errors gracefully
- Respect Rate Limits: Implement exponential backoff and respect API rate limits
- Secure Your Credentials: Never expose API tokens in logs, code repositories, or client-side applications
- Version Your Integrations: Be prepared for API changes and version your integration code
- Monitor API Usage: Track your API usage to optimize performance and costs
- Test in Non-Production: Always test integrations in a non-production environment first