Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/trimble:trimble-claims-cache-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Org Service Claims Cache API
description: '# Overview
The Organizer Service allows managing hierarchical breakdown structures. Each breakdown structure is represented as a tree. Trees are organized in forests, a group of trees. Typically forests would be mapped to projects. Each tree consists of nodes. Nodes are managed as a flat list but clients are expected to organize them into the tree kind of structure based on common name prefixes. Each node has a set of links associated with it. Links are opaque strings that are expected to be interpreted by clients. Documentation for this service is available on the Trimble Developer site. # Getting started
**You must agree to the Terms of Service to use Connect services.**
You need to complete the steps in the Getting started guide to be able to call the API. # Concepts
Please see Common Concepts in the Connect Platform documentation. ## Change notifications
The Subscribe API allows getting url for creating a WebSocket connection to the service. A standard WebSocket API may be used, no additional library is needed.A webSocket connection
may be used to receive notification messages of changes on any resource the user has access to. Notifications are delivered at best effort, in some rare cases, notifications can be lost. A periodic full refresh of the local cache is recommended. A Notification WebSocket is opened using the credentials of the subscribing user. Change notifications will be published
for every change in each resource managed by the service if and only if the user has read access
(org:GetXXX action) to the changed resource. After opening the WebSocket connection, the client needs to send a subscription message to start receiving change notification messages. Before that, the subscription service will send only keepalive messages. ```json
{
"type": "Subscribe"
}
```
The notification message has type "Data". The Notification message payload has the same syntax as BatchGetRequest, in other words, it contains objects with arrays of resource identifiers. The resource version is always included in the identifier. ```json
{
"type": "Data",
"payload": { "trees":
[
{
"forestId" : "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"treeId" : "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy",
"v" : 2
}
]
}
}
```
```json
{
"type": "Data",
"payload": { "nodes":
[
{
"forestId" : "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"treeId" : "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy",
"nodeId" : "zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
"v" : 9
}
]
}
}
```
The service sends periodic keepalive messages to all connected clients (type "Ka", no payload). No reply from the client is expected. In other words, the client can silently ignore these messages. Also, the client can send keepalive messages. The service will not reply to them. ```json
{
"type": "Ka"
}
```
## Deprecated Change notifications
The set of `Subscribe` APIs allows subscribing to the change notifications in different scopes (forest, tree, node). The notifications are delivered with MQTT protocol over HTTP. To consume notifications in browser-based apps you can use https://www.npmjs.com/package/cdm-notify-client as a convenient wrapper for the AWS IoT Device class. The payload of each change notification is a JSON object with a `location` property that identifies the changed resource as a relative URL
and the `v` property that informs the new version of the changed resource. Note that notification topic names should not be parsed to get the resource identity as they might be scrambled. ## Eventual Read Consistency
The service internally stores data in several Availability Zones within a Region. Each Availability Zone is isolated from failures in other Availability Zones and provides inexpensive, low-latency network connectivity to other Availability Zones in the same Region. This allows rapid replication of your data among multiple Availability Zones in a Region. When your application writes data to the service and receives an HTTP 200 response (OK), the write has occurred and is durable.'
version: v1
contact:
name: Trimble Connect Support
url: https://connect.trimble.com
email: connect-support@trimble.com
license:
name: Trimble Connect SDK Internal Use License
url: https://developer.trimble.com/docs/connect/terms/SDK-IU-license-agreement
termsOfService: https://developer.trimble.com/docs/connect/terms
servers:
- url: https://org-api.eu-west-1.connect.trimble.com/v1
description: Production EU (Ireland)
- url: https://org-api.eu-west-2.connect.trimble.com/v1
description: Production UK (London)
- url: https://org-api.us-east-1.connect.trimble.com/v1
description: Production US East (N. Virginia)
- url: https://org-api.ap-southeast-1.connect.trimble.com/v1
description: Production Asia Pacific (Singapore)
- url: https://org-api.ap-southeast-2.connect.trimble.com/v1
description: Production Asia Pacific (Sydney)
tags:
- name: Claims Cache
description: Operations to control user claims cache used for making access control decisions.
paths:
/me:
get:
summary: Me
operationId: Me
description: Get information about the user bearer token belongs to.
tags:
- Claims Cache
parameters:
- name: refresh
in: query
description: If specified the claims refresh is enforced out of normal refresh cycle before the set of claims returned. Usually claims refresh is happening periodically (every 15 minutes) in the background.
schema:
type: boolean
- name: all
in: query
description: If specified the all known information about the user is returned, otherwise only basic identity claims returned. WARN - this information is for debugging purposes only, client applications should not rely on the structure and content of the response, it could change in the future without notification.
schema:
type: boolean
- name: wait
in: query
description: If specified the service will wait for the asynchronous claims gathering process to complete, otherwise service immediately return claims gathered so far even if the gathering is not complete yet. Makes a difference only if 'all' parameter is specified.
schema:
type: boolean
responses:
'200':
description: User info
content:
application/json:
schema:
$ref: '#/components/schemas/UserClaims'
'401':
description: Authorization information is missing or invalid.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
security:
- Bearer: []
components:
schemas:
ErrorResponse:
title: The error response.
required:
- code
- message
type: object
properties:
code:
type: string
description: The error code.
message:
type: string
description: The human readable error message.
UserClaims:
title: Claims about the user.
required:
- iss
- sub
type: object
properties:
sub:
type: string
description: The identifier (Trimble ID UUID) of the user.
email:
type: string
description: The email of the user.
iss:
type: string
description: The issuer claim identifies the principal that issued the token.
uat:
type: integer
description: The timestamp when the user claims cache has been updated last time. The cache is updated automatically periodically. To force the immediate update the `/me` API can be called with the `refresh` query parameter.
securitySchemes:
Bearer:
type: http
description: The Trimble ID access token.
scheme: bearer
bearerFormat: JWT
x-amazon-apigateway-binary-media-types:
- application/vnd.trimbim
x-amazon-apigateway-minimum-compression-size: 1024
x-amazon-apigateway-gateway-responses:
ACCESS_DENIED:
statusCode: '401'
responseParameters:
gatewayresponse.header.Access-Control-Allow-Origin: '''*'''
gatewayresponse.header.Access-Control-Allow-Headers: '''Origin,X-Requested-With,Content-Type,Accept,Authorization,If-Match'''
gatewayresponse.header.Access-Control-Allow-Methods: '''GET,HEAD,OPTIONS,POST,PUT,DELETE,PATCH'''
gatewayresponse.header.Access-Control-Max-Age: '''1728000'''
responseTemplates:
application/json: '{"code":"$context.authorizer.code","message":"$context.authorizer.message"}'
UNAUTHORIZED:
statusCode: '401'
responseParameters:
gatewayresponse.header.Access-Control-Allow-Origin: '''*'''
gatewayresponse.header.Access-Control-Allow-Headers: '''Origin,X-Requested-With,Content-Type,Accept,Authorization,If-Match'''
gatewayresponse.header.Access-Control-Allow-Methods: '''GET,HEAD,OPTIONS,POST,PUT,DELETE,PATCH'''
gatewayresponse.header.Access-Control-Max-Age: '''1728000'''
responseTemplates:
application/json: '{"code":$context.error.messageString,"message":"Bearer token is expected in Authorization header."}'
MISSING_AUTHENTICATION_TOKEN:
statusCode: '404'
responseParameters:
gatewayresponse.header.Access-Control-Allow-Origin: '''*'''
gatewayresponse.header.Access-Control-Allow-Headers: '''Origin,X-Requested-With,Content-Type,Accept,Authorization,If-Match'''
gatewayresponse.header.Access-Control-Allow-Methods: '''GET,HEAD,OPTIONS,POST,PUT,DELETE,PATCH'''
gatewayresponse.header.Access-Control-Max-Age: '''1728000'''
responseTemplates:
application/json: '{"code":"RESOURCE_NOT_FOUND","message":"The requested resource is not found."}'