HomeFor ITPickit API
Pickit API

Build with your
Pickit content.

Connect your own applications and services to Pickit. Find files, work with collections, upload content and update metadata through the Pickit Public API.

Your application or service
Pickit Public APIGET POST
Files · Collections · Metadata
REST endpoints with account and library context
What you can build

Make the library part of your workflow.

Use the API for a custom content experience, an import process or a connection to another business system. Choose the operations your workflow needs.

Find and retrieve files

Search, filter and list files, or retrieve a file by ID. Use the returned metadata, file URLs and previews in your application.

Work with collections

Retrieve collections and use collection filters to find the files for a particular audience or content experience.

Upload content from a URL

Import a file from a reachable URL into the configured Pickit account and library, with its metadata. Uploads require administrator permissions on the API account.

Update file metadata

Update names, descriptions, tags, attributes and collection membership. Metadata writes require administrator permissions on the API account.

Explore the endpoint reference
Authentication & scope

Credentials plus the right content context.

The Public API uses an API key and secret. Requests also identify the Pickit account and library they operate on. Configure access with Pickit before building the integration.

Read access follows the API user’s permissions in the configured account. Upload and update operations require account administrator access.

Read the authentication documentation
Pickit-Api-Key
Identifies your API credentials.
Pickit-Api-Secret
Authenticates the API key.
Pickit-Api-Account
Identifies the configured Pickit account.
Pickit-Api-Library
Selects the library for the operation.

Keep the API secret in your server-side application or service. It should never be exposed in browser code or a public repository.

Getting started

Start with one useful operation.

The documentation is the reference for base URLs, request parameters and response formats. Validate the account and permission model before expanding the workflow.

  1. Agree access

    Define the content, account, library and read or write operations your application needs. Arrange the API credentials with Pickit.

  2. Check the connection

    Use the documented credential-check endpoint, then list or retrieve a file from the intended library.

  3. Build and validate

    Test with representative files and user permissions. Handle pagination and error responses, and validate any writes in a controlled library.

Open the developer documentation
Two ways to connect

An API for your application. MCP for AI clients.

Pickit Public API

Your application calls REST endpoints with an API key and secret. You define the interface, data handling and workflow.

Pickit MCP

An AI client connects through MCP with user authorization. It can use the tools available to that client within the authorized user’s Pickit access.

Explore MCP & AI integrations

What would you like to connect?

Tell us about your application, content and intended workflow. We’ll help you define the API access it needs.