Trelica API

You can use the Trelica API to connect Trelica to third-party apps - such as business productivity tools, finance systems or HR systems - use an existing integration.


The API is documented in Postman with links to the formal endpoint documentation.

Who is the API for?

The Trelica API is designed for technical users at Trelica customers, and also for developers wanting to integrate their products with Trelica.

What can I do with the API?

The API covers many core areas of Trelica including applications, people, contracts, workflows, the audit log, and users.

For IT teams running in AWS, the MCP Server for Trelica by 1Password provides a centralized, read-only control plane for SaaS visibility and access control intelligence. Backed by 350+ direct integrations with the most widely-used enterprise SaaS apps, the MCP Server helps you monitor app usage, user access, and policy drift across your environment. See usage instructions under “Additional details” on the AWS listing for the MCP Server for Trelica by 1Password.

The API is under incremental development, so if there are features that you need that aren't currently supported please reach out to us.

How do I use the API?

A good starting point is our Postman documentation. You can open the collection directly here:

Run In Postman

For authentication you can use both the Client Credentials Flow or Authorization Code Flow with Postman. We recommend getting started with the Client Credentials OAuth flow.

We've also published a PowerShell module which will help get you started if you're using the API from scripts:

How is the API designed?

The Trelica API is a modern, RESTful API. It is built on secure, widely adopted standards.

Authentication and authorization use OAuth 2.0, either using Client Credentials or Authorization Code flows. Client Credentials is appropriate if you are connecting to access your own data; Authorization Code flow is best if you are a software developer wanting to let your users access their Trelica data in your application.

If you're configuring OAuth then your tool or library might support the "well-known" OpenID configuration standard. The Trelica URL for this is:

https://app.trelica.com/.well-known/openid-configuration

Regardless of which OAuth flow you choose, all access is governed by Scopes which determine what you are allowed to see and do with the API.

The flow and the scopes you want to use to connect are bundled together by an API App. You can define an App yourself in Trelica. Apps can either have local access, or if you are a software developer, you may want to publish the app so that mutual customers can access their Trelica data from your product.

This documentation uses https://app.trelica.com when referencing endpoints. If you are hosted on our EU environment, then please use https://eu.trelica.com instead of https://app.trelica.com when accessing the API.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.