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-psets-syncing-beta-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: PSet Service PSets Syncing BETA API
description: '# Overview
The Property Set Service allows managing libraries of property set definitions and attaching property sets to external objects. * Property sets are a collection of properties. * Definitions allow validating the properties against a schema. 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 Monitoring
The service supports change monitoring through the polling APIs (with ability to fetch the changed resources) as well as change push notifications via Subscribe API. ### Polling for Changes
The polling style change detection and synchronization is supported only for property sets (not library descriptors and definitions) in the scope of psets that belong to specific library (ListPSetChangesByLib) or to specific definition (GetPSetChangesByDef). A `changeToken` is used to represent a cursor to the current state of the respources in the synchronization scope at specific point in time. The `changeToken` is an opaque string and should not be interpreted by the client. The client should store the `changeToken` and use it in the next request to fetch the changes since the last request. An initial value of the `changeToken` is typically received from the corresponding listing API (ListPSetsByLib or ListPSetsByDef) that return the `changeToken` representing the current state in the corresponding scope. So after fetching the current state with the `ListPSetsByXXX` API, the client can use the `changeToken` with the `ListPSetChangesByXXX` APIs to fetch the changes over the time. To detect if there are any changes avalable call a `ListPSetChangesByXXX` API with the known `changeToken`. It allows both detect if there is a change available as well as to fetch the actual changes in a single request. While paginating responses, the `changeToken` is updated on each page response and can be used to fetch the next page of changes instead of the `next` url. Using `changeToken` for paginating `ListPSetChangesByXXX` API is a preferred method to iterate through changes instead of using the `next` url because it allows to tolerate potential failures on the client side while iterating over the long collection of changes. As a most robust solution the client could fetch the page of changes, process the items on the page and store the `changeToken` before proceeding to the next page request. The presence of the `next` could be used as an indication that there are more changes to fetch available immediately. If there is no `next` url in the response, the client should store the `changeToken` and have a delay before using it to request further changes. ### Change Push 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".'
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://pset-api.eu-west-1.connect.trimble.com/v1
description: Production EU (Ireland)
- url: https://pset-api.eu-west-2.connect.trimble.com/v1
description: Production UK (London)
- url: https://pset-api.us-east-1.connect.trimble.com/v1
description: Production US East (N. Virginia)
- url: https://pset-api.ap-southeast-1.connect.trimble.com/v1
description: Production Asia Pacific (Singapore)
- url: https://pset-api.ap-southeast-2.connect.trimble.com/v1
description: Production Asia Pacific (Sydney)
tags:
- name: PSets Syncing BETA
description: '**BETA** APIs related to PSets synchronization'
paths:
/libs/{libId}/defs/{defId}/psetsSync:
get:
deprecated: true
tags:
- PSets Syncing BETA
summary: PsetsSync - lists PSets and returns changeToken for getting later changes fast
description: 'PsetsSync is similar to ListPSetsByDef as PsetsSync also returns a paginated list of PSets. PsetsSync is meant to be used for initial state synchronization to support other syncing methods. There are two changes compared to ListPSetsByDef:
1.Only non-deleted psets can be fetched.
2.Each page of responses also contains cursor (known as *changeToken*) of the latest information returned so that later fetch of changes can return changed pSets only.
If the multi-page response is interrupted the changeToken in the last page received can be used for later fetch of changes without having to complete the initial fetch successfully.'
operationId: psetsSync
parameters:
- name: libId
in: path
description: The library identifier.
required: true
schema:
type: string
- name: defId
in: path
description: The pset definition identifier.
required: true
schema:
type: string
- name: top
in: query
description: The maximum number of items to return on a single page (max is 500, default is 100). Note that this parameter does not guarantee that the exact requested number of items is returned. A single list operation can retrieve a maximum of 2 MB of data. This limit applies before the access control filtering is applied to the results. If the `next` link is present in the response and is non-null, you must paginate the result set.
schema:
maximum: 500
minimum: 0
type: integer
- name: skiptoken
in: query
description: The token used for the pagination. Typically returned with the response in the previous page and should be used as is without interpretation.
schema:
type: string
responses:
'200':
description: List of resources
content:
application/json:
schema:
$ref: '#/components/schemas/SyncPSetsPage'
'400':
description: Required parameters are missing (e.g. libId, defId) or request is not valid in some other way.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
'401':
description: Authorization information is missing or invalid.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
'403':
description: User is not authorized to access this resource.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
security:
- Bearer: []
components:
schemas:
SyncPSetsPage:
title: The page with a list of psets and a link to the next page and changeToken in the last page.
required:
- items
type: object
properties:
items:
type: array
items:
$ref: '#/components/schemas/PSetResponse'
next:
type: string
description: The link to the next page if there are more items available.
changeToken:
type: string
example: eus3hfy5kh
description: The token/cursor value for subsequent fetches of changes. The value might be the same 'changeToken' as was passed as input to the API, if there are no changes found. The property might be missing from the response, if there were no input 'changeToken' and there are no any psets in the scope.
PSetResponse:
title: The pset instance.
required:
- createdAt
- createdBy
- defId
- libId
- link
- modifiedAt
- modifiedBy
- props
- schemaV
- v
type: object
properties:
link:
type: string
description: The link to external resource (FRN notation).
libId:
type: string
description: The library id.
defId:
type: string
description: The pset definition id.
createdAt:
type: string
description: The creation timestamp.
format: date-time
createdBy:
type: string
description: The identifier of the user created the pset.
modifiedAt:
type: string
description: The last update timestamp.
format: date-time
modifiedBy:
type: string
description: The identifier of the user updated the pset last time.
deleted:
type: boolean
description: The deletion flag.
v:
type: integer
description: The version number.
schemaV:
type: integer
description: The pset schema version used for this pset.
props:
type: object
properties: {}
description: The property values.
_actions:
type: array
description: Metadata. The list of context actions caller is allowed to perform on the resource. Please see explanation with warning about use of this information in the introduction section.
items:
type: string
description: The action.
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.
securitySchemes:
Bearer:
type: http
description: The Trimble ID access token.
scheme: bearer
bearerFormat: JWT
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,If-None-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,If-None-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,If-None-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."}'