Bonjoro

Bonjoro is a personal-video customer engagement platform operated by Vimily Pty Ltd of Sydney, Australia. Sales, marketing, customer success and education teams use it to record short one-to-one videos — "Bonjoros" — and deliver them at the moments that decide a relationship: signup, onboarding, first purchase, renewal and churn risk. Alongside the messaging product it runs a video testimonial collection surface. Bonjoro publishes a REST API (API V2, 94 paths and 123 operations) covering greets, recipient profiles, campaigns and workspaces, recordings and media, message templates, engagement results and stats, transmissions and deliverability, replies, teams and users, custom sending domains and verified signatures, and the trigger/action automation engine that wires Bonjoro into CRMs and email platforms. REST API access is published as a Company-tier entitlement; the wider integration surface runs through 18+ native connectors and a first-party Zapier app.

Bonjoro publishes 1 API on the APIs.io network: API V2. Tagged areas include video-messaging, customer-engagement, customer-success, sales-engagement, and marketing-automation.

The Bonjoro catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Bonjoro’s developer surface includes documentation, API reference, support, engineering blog, pricing, signup flow, authentication, and 17 more developer resources.

50.5/100 developing ▬ flat Agent 49/100 agent ready Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs
video-messagingcustomer-engagementcustomer-successsales-engagementmarketing-automationvideocrm-integrationtestimonialssaasaustralia

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 50.5/100 · developing
Contract Quality 13.6 / 25
Developer Ergonomics 7.8 / 20
Commercial Clarity 15.3 / 20
Operational Transparency 3.8 / 13
Governance 2.5 / 12
Discoverability 7.6 / 10
Agent readiness — 49/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/bonjoro: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Bonjoro API V2

REST API for the Bonjoro personal-video platform. Create and assign greets (video tasks) for one or many recipients, manage recipient profiles and campaigns/workspaces, upload r...

Open Collections 1

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

Bonjoro API V2

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Bonjoro Plans Pricing

5 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Bonjoro Rate Limits

1 limits

RATE LIMITS

Event Specifications 1

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

Security Posture 2

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

Bonjoro Authentication

oauth2/http-bearer · 2 schemes

SECURITY

Bonjoro Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: bonjoro
name: Bonjoro
description: 'Bonjoro is a personal-video customer engagement platform operated by Vimily Pty Ltd of Sydney, Australia. Sales,
  marketing, customer success and education teams use it to record short one-to-one videos — "Bonjoros" — and deliver them
  at the moments that decide a relationship: signup, onboarding, first purchase, renewal and churn risk. Alongside the messaging
  product it runs a video testimonial collection surface. Bonjoro publishes a REST API (API V2, 94 paths and 123 operations)
  covering greets, recipient profiles, campaigns and workspaces, recordings and media, message templates, engagement results
  and stats, transmissions and deliverability, replies, teams and users, custom sending domains and verified signatures, and
  the trigger/action automation engine that wires Bonjoro into CRMs and email platforms. REST API access is published as a
  Company-tier entitlement; the wider integration surface runs through 18+ native connectors and a first-party Zapier app.'
image: https://www.bonjoro.com/apple-touch-icon-180x180.png
url: https://raw.githubusercontent.com/api-evangelist/bonjoro/refs/heads/main/apis.yml
x-type: company
x-source: harvest:marketing-integration-graph
x-tier: enriched
x-tier-reason: enrichment-pipeline
specificationVersion: '0.21'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- video-messaging
- customer-engagement
- customer-success
- sales-engagement
- marketing-automation
- video
- crm-integration
- testimonials
- saas
- australia
apis:
- name: Bonjoro API V2
  description: REST API for the Bonjoro personal-video platform. Create and assign greets (video tasks) for one or many recipients,
    manage recipient profiles and campaigns/workspaces, upload recordings to presigned S3 URLs, apply message templates and
    branding, read engagement results, event streams and transmission/deliverability records, manage teams, users, invites,
    custom sending domains and verified email signatures, and build trigger/action automations against connected CRM and email
    services. OAuth 2.0 bearer tokens issued from /api/v2/oauth/2/token.
  humanURL: https://vimily.github.io/bonjoro-api-docs/
  baseURL: https://www.bonjoro.com/api/v2
  tags:
  - video-messaging
  - customer-engagement
  - customer-success
  - sales-engagement
  - marketing-automation
  - crm-integration
  properties:
  - type: Documentation
    url: https://vimily.github.io/bonjoro-api-docs/
  - type: APIReference
    url: https://vimily.github.io/bonjoro-api-docs/
  - type: OpenAPI
    url: openapi/bonjoro-api-v2-openapi.yml
  - type: Overlay
    url: overlays/bonjoro-api-v2-overlay.yaml
  - type: Authentication
    url: authentication/bonjoro-authentication.yml
  - type: Conventions
    url: conventions/bonjoro-conventions.yml
  - type: ErrorCatalog
    url: errors/bonjoro-problem-types.yml
  - type: DataModel
    url: data-model/bonjoro-data-model.yml
  - type: RateLimits
    url: rate-limits/bonjoro-rate-limits.yml
  - type: Webhooks
    url: asyncapi/bonjoro-webhooks.yml
  - type: Conformance
    url: conformance/bonjoro-conformance.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://bonjoro.com/
- type: Documentation
  url: https://vimily.github.io/bonjoro-api-docs/
- type: APIReference
  url: https://vimily.github.io/bonjoro-api-docs/
- type: Support
  url: https://www.bonjoro.com/support-center
- type: HelpCenter
  url: https://help.bonjoro.com/
- type: Blog
  url: https://www.bonjoro.com/blog
- type: Pricing
  url: https://www.bonjoro.com/pricing
- type: SignUp
  url: https://www.bonjoro.com/auth/register
- type: Login
  url: https://www.bonjoro.com/auth/login
- type: TermsOfService
  url: https://www.bonjoro.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.bonjoro.com/privacy-policy
- type: Integrations
  url: https://www.bonjoro.com/integration
- type: Plans
  url: plans/bonjoro-plans-pricing.yml
- type: RateLimits
  url: rate-limits/bonjoro-rate-limits.yml
- type: Authentication
  url: authentication/bonjoro-authentication.yml
- type: Conventions
  url: conventions/bonjoro-conventions.yml
- type: ErrorCatalog
  url: errors/bonjoro-problem-types.yml
- type: Lifecycle
  url: lifecycle/bonjoro-lifecycle.yml
- type: DataModel
  url: data-model/bonjoro-data-model.yml
- type: Conformance
  url: conformance/bonjoro-conformance.yml
- type: Packages
  url: packages/bonjoro-packages.yml
- type: Webhooks
  url: asyncapi/bonjoro-webhooks.yml
- type: LLMsTxt
  url: llms/bonjoro-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/bonjoro-domain-security.yml
x-vouched-by:
- Drip
- MailerLite
x-vouch-count: 2
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 21
  pass: local-v1
x-enrichment-notes:
  contract_discovery: 'The API host api.bonjoro.com is a Cloudflare-challenged dead end (403 "Just a moment..." on every path)
    and no developers/docs/status subdomain resolves. The real machine-readable contract was found on the third pass: Bonjoro''s
    own API reference is a Redoc standalone bundle at https://vimily.github.io/bonjoro-api-docs/ (Vimily Pty Ltd is Bonjoro''s
    operating company), with a complete OpenAPI 3.0.0 document — 94 paths, 123 operations, 126 schemas, 42 tags — embedded
    in the page''s __redoc_state. It is saved verbatim in openapi/_original/.'
  pointers_deliberately_withheld: No WellKnown or SecurityTxt (every /.well-known/ path 404s), no AgentCard (probed, absent),
    no MCPServer (no server exists — mcp/ holds a derived candidate only), no ToolCrosswalk (no MCP or GraphQL surface), no
    SDKs (no first-party client library in any registry), no Idempotency (no idempotency contract anywhere in 123 operations),
    no StatusPage (status.bonjoro.com has no DNS; the statuspage.io and instatus.com hosts are vendor catch-alls), no Deprecation
    (no policy, no Sunset header, no deprecated operation), no ChangeLog (/changelog redirects to the product login), no Security
    or Compliance (no disclosure policy, bug bounty, trust centre or named certification), no AsyncAPI (webhooks documented,
    no spec), no OAuthScopes (every requirement is an empty scope array).