Extract Assets and Metadata
External systems can query iBase through HTTP requests, use a range of search criteria and retrieve approved assets and metadata in structured documents.
Developer API and integrations
Connect iBaseTo Sites and External Systems
Let approved websites, applications, CMS platforms and search services query iBase and retrieve structured assets and metadata without bypassing repository permissions.
API access
Secure Asset and Metadata APIs
iBase includes API access for external systems that need to search repositories, retrieve metadata and publish selected assets into websites or applications.
Support Configurable Data Models
The API supports structured subjects, categories, keyword hierarchies, item relationships and item-type-specific fields from configurable iBase schemas.
Control What Applications Can Reach
API access can be shaped around authorised systems, repository permissions and the specific assets or metadata each integration should expose.
Integration patterns
Web, Search and CMS Workflows
Integration routes can be designed around publishing, discovery, synchronisation or downstream application needs.
Search
Federated Searching
Expose selected data so federated search engines can query iBase alongside other online databases, return results from each source and link users back to source records.
CMS
Integrate with Content Management Systems
Connect with external content management systems and poll for content at regular intervals to reduce manual transfer effort.
Read/write
Structured API Routes
Use API routes to retrieve approved records or support controlled submission workflows where external systems need to send content back.
Governance
Permission-Aware Integration
Combine API access with folder-level controls so external systems only reach the content they are authorised to use.
Connected DAM
Connect iBase to Your Estate
API use cases, search exposure and integration patterns can be scoped around public sites, CMS platforms and downstream applications.
Public Publishing
Power public portals and specialist collection sites from approved iBase records.
Internal Integration
Connect DAM content with CMS, collection, CRM or operational systems where workflows require it.
Controlled Exposure
Keep integration access explicit, permission-aware and aligned with repository governance.