API Integration Guidelines
Welcome to the Screendragon API Portal! This page outlines the essential guidelines and best practices for integrating with our APIs. Please read carefully to ensure a smooth and efficient integration experience.
Authentication & Access
To access our APIs, clients must first obtain authentication credentials.
How to Get Started:
- Request Access: To enable API access for your organization, please contact your Screendragon Account Manager.
- Receive Credentials:
- You will receive a
Client IDandClient Secretfor OAuth 2.0 authentication along with relevant URLs depending uponGranttype. - You will receive API Key for Basic Authentication.
- You will receive a
Sandbox Environment
We provide a sandbox environment for testing and development, available as the Screendragon staging site.
Best Practices
To ensure optimal performance and avoid service disruptions, please follow these guidelines:
Efficient API Usage
- Avoid Unnecessary Calls: Only call endpoints when needed. Avoid polling or excessive retries.
- Use Webhooks: Where available, use webhooks instead of polling for updates.
- Batch Requests: Use batch endpoints when available to reduce the number of API calls.
Rate Limiting
- Standard Limit: 1,000 requests per hour per client.
- Throttling: Exceeding limits will result in
429 Too Many Requestsresponses.
Data Updates
- Avoid Frequent Updates: Do not send frequent updates for the same resource unless necessary.
Prohibited Activities
To maintain system integrity, the following are strictly prohibited:
- Sending automated or scripted traffic without prior approval.
- Attempting to bypass authentication or rate limits.
- Using production credentials in the sandbox environment.
- Posting sensitive or personal data in test environments.
Support & Contact
If you have questions or need help, Please contact your Screendragon Account Manager.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article