How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Unified.to list API

The list API from Unified.to — 2 operation(s) for list.

Unified.to list API is one of 140 APIs that Unified.to publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 13 JSON Schema definitions.

Tagged areas include List. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 13 JSON Schemas.

This API exposes 6 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against 3 base URLs: https://api.unified.to, https://api-eu.unified.to, https://api-au.unified.to.

6 operations 2 paths 3 schemas 1 DELETE2 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Servers
https://api.unified.to
https://api-eu.unified.to
https://api-au.unified.to
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Unified.to list API declares 1 security scheme for authenticating requests. An API key is passed in the header as authorization (jwt). By default, every request must be authenticated.

Paths & Operations 6

Across 2 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

list 6
GET
/martech/{connection_id}/list
List All Lists
listMartechLists 9 params → 200
POST
/martech/{connection_id}/list
Create a List
createMartechList 3 params body → 200
DELETE
/martech/{connection_id}/list/{id}
Remove a List
removeMartechList 2 params → 200default
GET
/martech/{connection_id}/list/{id}
Retrieve a List
getMartechList 4 params → 200
PATCH
/martech/{connection_id}/list/{id}
Update a List
patchMartechList 4 params body → 200
PUT
/martech/{connection_id}/list/{id}
Update a List
updateMartechList 4 params body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are MarketingList (17 properties), property_MarketingList_address (8 properties). Each schema is shown below with its type and property counts.

MarketingList
object
Mailing List
17 properties
property_MarketingList_address
object
8 properties
MarketingLists
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unified-to-list-api-openapi.yml Raw ↑

Other APIs Unified.to publishes across the network.

Unified.to
Unified.to Authentication API
Unified.to account API
Unified.to accounting API
Unified.to activity API
Unified.to ad API
Unified.to ads API
Unified.to apicall API
Unified.to application API
Unified.to applicationstatus API
Unified.to assessment API
Unified.to ats API
Where this information came from

This is an independent, third-party profile of Unified.to list API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.