SendSafely REST API

Name: SendSafely REST API
Brand: SendSafely REST API
Availability: InStock

✓ Official Vendor SpecStorageObject StorageapiKey36 EndpointsREST

For Agents

Programmatically verify api credentials, verify api version. Covers 36 operations with apiKey authentication.

Install Jentic One Beta

Connect the SendSafely REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SendSafely REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with SendSafely REST API.

Verify API credentials

Get user information

Add dropzone recipient

Query and filter SendSafely REST API records by parameters

GET STARTED

Start building with SendSafely REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SendSafely REST API for, with concrete tasks.

★ Storage and Databases Operations

Use the SendSafely REST API to perform storage operations programmatically. The API provides 36 endpoints covering core functionality including verify api credentials, verify api version, get user information.

Call GET /config/verify-credentials/ to verify api credentials

Automated config Management

Automate config operations by combining multiple SendSafely REST API endpoints. Agents can verify api version and then get user information in a single workflow.

Call GET /config/version/{platform}/{versionNo}/ to verify api version, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SendSafely REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'verify api credentials', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

36 endpoints — the sendsafely rest api provides programmatic access to sendsafely for sending and receiving encrypted files.

METHOD

PATH

DESCRIPTION

GET

/config/verify-credentials/

Verify API credentials

GET

/config/version/{platform}/{versionNo}/

Verify API version

GET

/user/

Get user information

GET

/user/dropzone-recipients/

Get dropzone recipients

PUT

/user/dropzone-recipients/

Add dropzone recipient

GET

/user/groups/

Get contact groups

GET

/enterprise/

Get enterprise information

GET

/package/

List active packages

GET

/config/verify-credentials/

Verify API credentials

GET

/config/version/{platform}/{versionNo}/

Verify API version

GET

/user/

Get user information

GET

/user/dropzone-recipients/

Get dropzone recipients

PUT

/user/dropzone-recipients/

Add dropzone recipient

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

SendSafely REST API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'verify api credentials') and Jentic returns the matching SendSafely REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct SendSafely REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using SendSafely REST API through Jentic.

What authentication does the SendSafely REST API use?

The SendSafely REST API uses an API key passed in the `ss-api-key` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I verify api credentials with the SendSafely REST API?

Yes. Use the GET /config/verify-credentials/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the SendSafely REST API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I verify api credentials through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'verify api credentials'. Jentic returns the matching SendSafely REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the SendSafely REST API have?

The SendSafely REST API exposes 36 endpoints covering config, user, enterprise operations.

SendSafely REST API

Connect the SendSafely REST API to your agent

Capabilities

Start building with SendSafely REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs