Reachdesk website screenshot

Reachdesk

Reachdesk is a global B2B corporate gifting and direct mail platform that enables sales, marketing, and customer success teams to send physical gifts, branded merchandise, and digital rewards at scale. The Reachdesk REST API allows programmatic triggering of gift campaigns, integration with CRM and marketing automation tools, and management of sending workflows across 180+ countries. API tokens are generated via the platform settings and used to authenticate requests for campaign triggering and gift delivery operations.

Reachdesk publishes 8 APIs on the APIs.io network, including Bulk Sends API, Campaigns API, Contacts API, and 5 more. Tagged areas include Corporate Gifting, Direct Mail, Swag, B2B, and Sales Enablement.

The Reachdesk catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 JSON-LD context.

Reachdesk’s developer surface includes authentication, documentation, support, engineering blog, pricing, API reference, getting-started guide, and 28 more developer resources.

56.2/100 strong ▬ flat Agent 35/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessPaid
2 APIs 1 MCP Servers
Corporate GiftingDirect MailSwagB2BSales EnablementCustomer SuccessMarketing AutomationGifting PlatformRewardsMCPAI AgentsOpenAPI

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/reachdesk: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Reachdesk MCP Server

Reachdesk operates a first-party remote Model Context Protocol server at https://app.reachdesk.com/mcp, on the same host as its REST API. It is a hosted HTTP endpoint an MCP cli...

Reachdesk Bulk Sends API

The Bulk Sends API from Reachdesk — 1 operation(s) for bulk sends.

Reachdesk Campaigns API

The Campaigns API from Reachdesk — 1 operation(s) for campaigns.

Reachdesk Contacts API

The Contacts API from Reachdesk — 1 operation(s) for contacts.

Reachdesk Gdpr API

The Gdpr API from Reachdesk — 2 operation(s) for gdpr.

Reachdesk Organization API

The Organization API from Reachdesk — 1 operation(s) for organization.

Reachdesk Sends API

The Sends API from Reachdesk — 1 operation(s) for sends.

Reachdesk Sends?start Date={start Date}&end Date={end Date} API

The Sends?start Date={start Date}&end Date={end Date} API from Reachdesk — 1 operation(s) for sends?start date={start date}&end date={end date}.

Reachdesk Transactions API

The Transactions API from Reachdesk — 1 operation(s) for transactions.

Scroll for all 9

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Reachdesk API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Reachdesk MCP Server

Reachdesk operates a first-party remote MCP server on its own API host. It is a hosted HTTP endpoint an MCP client POSTs to directly — there is no npx/stdio package to install. ...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Reachdesk Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Reachdesk Context

10 classes · 24 properties

JSON-LD

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Reachdesk Authentication

apiKey/oauth2 · 2 schemes

SECURITY

Reachdesk Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Reachdesk Trust Center

verified, claimed, note

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Reachdesk Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 5

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: reachdesk
name: Reachdesk
description: Reachdesk is a global B2B corporate gifting and direct mail platform that enables sales, marketing, and customer
  success teams to send physical gifts, branded merchandise, and digital rewards at scale. The Reachdesk REST API allows programmatic
  triggering of gift campaigns, integration with CRM and marketing automation tools, and management of sending workflows across
  180+ countries. API tokens are generated via the platform settings and used to authenticate requests for campaign triggering
  and gift delivery operations.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/reachdesk.png
url: https://raw.githubusercontent.com/api-evangelist/reachdesk/refs/heads/main/apis.yml
created: '2026-06-13'
modified: '2026-08-13'
specificationVersion: '0.23'
tags:
- Corporate Gifting
- Direct Mail
- Swag
- B2B
- Sales Enablement
- Customer Success
- Marketing Automation
- Gifting Platform
- Rewards
- MCP
- AI Agents
- OpenAPI
apis:
- aid: reachdesk:reachdesk-mcp
  name: Reachdesk MCP Server
  description: Reachdesk operates a first-party remote Model Context Protocol server at https://app.reachdesk.com/mcp, on
    the same host as its REST API. It is a hosted HTTP endpoint an MCP client POSTs to directly — there is no stdio package
    to install. Access is OAuth 2.1 with dynamic client registration (RFC 7591), PKCE S256, and two published scopes, mcp:tools.user.read
    and mcp:tools.user.write, which scope tools to the authenticated Reachdesk user. The server is undocumented in Reachdesk's
    knowledge base and API reference; it was found by probing the API host, and the tool list is auth-gated.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://reachdesk.readme.io/
  baseURL: https://app.reachdesk.com/mcp
  tags:
  - MCP
  - AI Agents
  - Gifting
  - Authentication
  tags_raw:
  - MCP
  - AI Agents
  - Gifting
  - OAuth
  properties:
  - type: MCPServer
    url: mcp/reachdesk-mcp.yml
  - type: ToolCrosswalk
    url: mcp/reachdesk-tool-crosswalk.yml
  - type: OAuthScopes
    url: scopes/reachdesk-scopes.yml
  - type: WellKnown
    url: well-known/reachdesk-well-known.yml
- aid: reachdesk:reachdesk-bulk-sends-api
  name: Reachdesk Bulk Sends API
  description: The Bulk Sends API from Reachdesk — 1 operation(s) for bulk sends.
  humanURL: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  baseURL: https://app.reachdesk.com/api/v2
  tags:
  - Bulk Sends
  properties:
  - type: OpenAPI
    url: openapi/reachdesk-bulk-sends-api-openapi.yml
  - type: Documentation
    url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  - type: APIReference
    url: https://reachdesk.readme.io/reference/authentication
  - type: APISection
    url: https://support.reachdesk.com/hc/en-gb/sections/29669389953297-Reachdesk-API
  - type: Authentication
    url: authentication/reachdesk-authentication.yml
  - type: ErrorCatalog
    url: errors/reachdesk-problem-types.yml
  - type: Conventions
    url: conventions/reachdesk-conventions.yml
  - type: DataModel
    url: data-model/reachdesk-data-model.yml
- aid: reachdesk:reachdesk-campaigns-api
  name: Reachdesk Campaigns API
  description: The Campaigns API from Reachdesk — 1 operation(s) for campaigns.
  humanURL: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  baseURL: https://app.reachdesk.com/api/v2
  tags:
  - Campaigns
  properties:
  - type: OpenAPI
    url: openapi/reachdesk-campaigns-api-openapi.yml
  - type: Documentation
    url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  - type: APIReference
    url: https://reachdesk.readme.io/reference/authentication
  - type: APISection
    url: https://support.reachdesk.com/hc/en-gb/sections/29669389953297-Reachdesk-API
  - type: Authentication
    url: authentication/reachdesk-authentication.yml
  - type: ErrorCatalog
    url: errors/reachdesk-problem-types.yml
  - type: Conventions
    url: conventions/reachdesk-conventions.yml
  - type: DataModel
    url: data-model/reachdesk-data-model.yml
- aid: reachdesk:reachdesk-contacts-api
  name: Reachdesk Contacts API
  description: The Contacts API from Reachdesk — 1 operation(s) for contacts.
  humanURL: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  baseURL: https://app.reachdesk.com/api/v2
  tags:
  - Contacts
  properties:
  - type: OpenAPI
    url: openapi/reachdesk-contacts-api-openapi.yml
  - type: Documentation
    url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  - type: APIReference
    url: https://reachdesk.readme.io/reference/authentication
  - type: APISection
    url: https://support.reachdesk.com/hc/en-gb/sections/29669389953297-Reachdesk-API
  - type: Authentication
    url: authentication/reachdesk-authentication.yml
  - type: ErrorCatalog
    url: errors/reachdesk-problem-types.yml
  - type: Conventions
    url: conventions/reachdesk-conventions.yml
  - type: DataModel
    url: data-model/reachdesk-data-model.yml
- aid: reachdesk:reachdesk-gdpr-api
  name: Reachdesk Gdpr API
  description: The Gdpr API from Reachdesk — 2 operation(s) for gdpr.
  humanURL: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  baseURL: https://app.reachdesk.com/api/v2
  tags:
  - GDPR
  tags_raw:
  - Gdpr
  properties:
  - type: OpenAPI
    url: openapi/reachdesk-gdpr-api-openapi.yml
  - type: Documentation
    url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  - type: APIReference
    url: https://reachdesk.readme.io/reference/authentication
  - type: APISection
    url: https://support.reachdesk.com/hc/en-gb/sections/29669389953297-Reachdesk-API
  - type: Authentication
    url: authentication/reachdesk-authentication.yml
  - type: ErrorCatalog
    url: errors/reachdesk-problem-types.yml
  - type: Conventions
    url: conventions/reachdesk-conventions.yml
  - type: DataModel
    url: data-model/reachdesk-data-model.yml
- aid: reachdesk:reachdesk-organization-api
  name: Reachdesk Organization API
  description: The Organization API from Reachdesk — 1 operation(s) for organization.
  humanURL: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  baseURL: https://app.reachdesk.com/api/v2
  tags:
  - Organization
  properties:
  - type: OpenAPI
    url: openapi/reachdesk-organization-api-openapi.yml
  - type: Documentation
    url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  - type: APIReference
    url: https://reachdesk.readme.io/reference/authentication
  - type: APISection
    url: https://support.reachdesk.com/hc/en-gb/sections/29669389953297-Reachdesk-API
  - type: Authentication
    url: authentication/reachdesk-authentication.yml
  - type: ErrorCatalog
    url: errors/reachdesk-problem-types.yml
  - type: Conventions
    url: conventions/reachdesk-conventions.yml
  - type: DataModel
    url: data-model/reachdesk-data-model.yml
- aid: reachdesk:reachdesk-sends-api
  name: Reachdesk Sends API
  description: The Sends API from Reachdesk — 1 operation(s) for sends.
  humanURL: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  baseURL: https://app.reachdesk.com/api/v2
  tags:
  - Sends
  properties:
  - type: OpenAPI
    url: openapi/reachdesk-sends-api-openapi.yml
  - type: Documentation
    url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  - type: APIReference
    url: https://reachdesk.readme.io/reference/authentication
  - type: APISection
    url: https://support.reachdesk.com/hc/en-gb/sections/29669389953297-Reachdesk-API
  - type: Authentication
    url: authentication/reachdesk-authentication.yml
  - type: ErrorCatalog
    url: errors/reachdesk-problem-types.yml
  - type: Conventions
    url: conventions/reachdesk-conventions.yml
  - type: DataModel
    url: data-model/reachdesk-data-model.yml
- aid: reachdesk:reachdesk-sends-start-date-start-date-end-date-end-date-api
  name: Reachdesk Sends?start Date={start Date}&end Date={end Date} API
  description: The Sends?start Date={start Date}&end Date={end Date} API from Reachdesk — 1 operation(s) for sends?start date={start
    date}&end date={end date}.
  humanURL: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  baseURL: https://app.reachdesk.com/api/v2
  tags: []
  tags_raw:
  - Sends?start Date={start Date}&end Date={end Date}
  properties:
  - type: OpenAPI
    url: openapi/reachdesk-sends-start-date-start-date-end-date-end-date-api-openapi.yml
  - type: Documentation
    url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  - type: APIReference
    url: https://reachdesk.readme.io/reference/authentication
  - type: APISection
    url: https://support.reachdesk.com/hc/en-gb/sections/29669389953297-Reachdesk-API
  - type: Authentication
    url: authentication/reachdesk-authentication.yml
  - type: ErrorCatalog
    url: errors/reachdesk-problem-types.yml
  - type: Conventions
    url: conventions/reachdesk-conventions.yml
  - type: DataModel
    url: data-model/reachdesk-data-model.yml
- aid: reachdesk:reachdesk-transactions-api
  name: Reachdesk Transactions API
  description: The Transactions API from Reachdesk — 1 operation(s) for transactions.
  humanURL: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  baseURL: https://app.reachdesk.com/api/v2
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/reachdesk-transactions-api-openapi.yml
  - type: Documentation
    url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
  - type: APIReference
    url: https://reachdesk.readme.io/reference/authentication
  - type: APISection
    url: https://support.reachdesk.com/hc/en-gb/sections/29669389953297-Reachdesk-API
  - type: Authentication
    url: authentication/reachdesk-authentication.yml
  - type: ErrorCatalog
    url: errors/reachdesk-problem-types.yml
  - type: Conventions
    url: conventions/reachdesk-conventions.yml
  - type: DataModel
    url: data-model/reachdesk-data-model.yml
common:
- type: Authentication
  url: authentication/reachdesk-authentication.yml
- type: DomainSecurity
  url: security/reachdesk-domain-security.yml
- type: Website
  url: https://www.reachdesk.com/
- type: Documentation
  url: https://support.reachdesk.com/hc/en-gb/categories/4404901379473-Integrations-API
- type: Support
  url: https://support.reachdesk.com/hc/en-gb
- type: Blog
  url: https://www.reachdesk.com/blog
- type: Pricing
  url: https://www.reachdesk.com/pricing
- type: LinkedIn
  url: https://www.linkedin.com/company/reachdesk
- type: X
  url: https://x.com/ReachdeskHQ
- type: GitHubOrg
  url: https://github.com/reachdesk
- type: Plans
  url: plans/reachdesk-plans-pricing.yml
- type: RateLimits
  url: rate-limits/reachdesk-rate-limits.yml
- type: FinOps
  url: finops/reachdesk-finops.yml
- type: DeveloperPortal
  url: https://reachdesk.readme.io/
- type: APIReference
  url: https://reachdesk.readme.io/reference/authentication
- type: GettingStarted
  url: https://support.reachdesk.com/hc/en-gb/articles/29669486204305-Send-gifts-with-the-Reachdesk-Trigger-Campaign-API
- type: TermsOfService
  url: https://www.reachdesk.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.reachdesk.com/privacy-policy
- type: Login
  url: https://app.reachdesk.com/users/sign_in
- type: WellKnown
  url: well-known/reachdesk-well-known.yml
- type: MCPServer
  url: mcp/reachdesk-mcp.yml
- type: ToolCrosswalk
  url: mcp/reachdesk-tool-crosswalk.yml
- type: OAuthScopes
  url: scopes/reachdesk-scopes.yml
- type: Conventions
  url: conventions/reachdesk-conventions.yml
- type: ErrorCatalog
  url: errors/reachdesk-problem-types.yml
- type: DataModel
  url: data-model/reachdesk-data-model.yml
- type: Lifecycle
  url: lifecycle/reachdesk-lifecycle.yml
- type: ChangeLog
  url: changelog/reachdesk-changelog.yml
- type: Conformance
  url: conformance/reachdesk-conformance.yml
- type: TrustCenter
  url: security/reachdesk-trust-center.yml
- type: Webhooks
  url: asyncapi/reachdesk-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Packages
  url: packages/reachdesk-packages.yml
- type: LLMsTxt
  url: llms/reachdesk-llms.txt
- type: Overlay
  url: overlays/reachdesk-api-overlay.yaml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-08-13'
  status: enriched
  artifacts_added: 26
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/reachdesk"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/reachdesk/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/reachdesk/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.