Lytho's API enables developers to build applications with access to Lytho's Asset Management and statistics dashboard. This enables users to fully integrate Lytho in their workflow and processes. Use the documentation below to get started:
TABLE OF CONTENTS
Using Lytho API
Lytho API allows developers to request information from Lytho including Assets, Collections, Tags, Tag groups and Permissions.
Every HTTP request made to Lytho API must be authenticated by Lytho. Lytho supports API keys to be able to authenticate and use the Lytho API.
An API key is bound to a specific Lytho tenant. Multiple API keys can be created and setup by a Lytho Admin this API key always needs to be send in the header of the API call and will be checked within Lytho API on validity. An API key can always be revoked by the Lytho tenant admin.
API Requests
All API requests must be made over HTTPS. The URL for the request varies depending on the region your account is located in and the resources being accessed. See our detailed API documentation for exact URLs.
Pagination of Lytho API is the process of organizing the response results of an API call into multiple pages. When you do GET calls especially bulk requests using the GET API methods there is a high possibility of a large number of records being returned. To make handling large payloads easier, we provide you with a way to control the maximum number of responses through pagination.
Every call that is capable of using pagination can be given the following two request parameters:
• Page, the page parameter contains the page you want to retrieve
• Size, the size parameter contains the number of records a single page will contain its defaulted to 20 and has a maximum of 50
Currently all API calls expect a complete object to be send back to update, if a field in the object is not present in the json the field will be removed and become an empty field within Lytho. At this moment partial updates are not possible.
Technical Documentation
You can find the technical documentation for Lytho DAM's API here.
Use Cases Examples
File Storage & Sharing Tools (Google Drive, Dropbox, OneDrive, Box)
Sync or migrate files to/from DAM, manage versioning, apply metadata automatically.
Project & Work Management Platforms (Jira, Asana, Smartsheet, Monday.com)
Link assets to tasks/projects, auto-upload final deliverables to DAM, trigger updates based on task status.
Communication & Collaboration Tools (Slack, Microsoft Teams)
Push notifications when assets are uploaded or updated, share asset links automatically in team channels.
Creative & Design Tools (Adobe Creative Cloud, Figma, Canva)
Pull approved assets into design tools, push final creatives back into DAM with correct metadata.
Sales & CRM Platforms (Salesforce, HubSpot, Zoho CRM)
Attach approved assets to deals, campaigns, or contacts; track usage by sales teams.
Web Content & CMS Tools (WordPress, Drupal, Sitecore, Kentico)
Publish DAM-hosted assets to websites, update imagery dynamically from DAM.
Calendaring & Scheduling Tools (Google Calendar, Outlook Calendar)
Use custom metadata to schedule asset lifecycle events (e.g., publish dates, expiration).
BI & Analytics Platforms (Domo, Tableau, Power BI)
Pull asset usage data and metadata for performance reporting and ROI analysis.
Customer Support & Knowledge Management (Zendesk, ServiceNow, Confluence)
Embed latest brand-approved visuals into help articles or ticket replies.
Error Handling
The Lytho API uses HTTP status codes to reflect a successful or unsuccessful request. 2XX status codes are successful requests 4XX/5XX status codes represent an error took place. If you receive an error status code, check the body for an error code and message.
| Status code |
Description | Most likely cause |
| 2XX | Successful request | |
| 400 | Bad request | Invalid / missing data |
| 401 | Unauthorized | Invalid / missing API key |
| 403 | Forbidden | Performing an action that's not permitted |
| 404 | Not found |
The resource doesn’t exist / wrong endpoint |
| 409 | Conflict |
Trying to overwrite a resource that already exists |
| 429 | Too many requests | Hit an API rate limit |
| 500 | Internal server error | An error occurred on Lytho side |
Rate Limits define the maximum number of requests that can be made by apps to the Lytho API in a given period of time. Lytho employs rate limits to ensure stability of the API service for all users and to prevent many types of abuse or inadvertent
usage. Cache responses whenever possible instead of frequently making the same request.
• 20 requests / minute
• and a daily rate limit of 30000 request / day
(this are the base rate limits, if needed we can look into specific requests for rate limit settings)