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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
VBOUT

VBOUT Contact API

The Contact API from VBOUT — 18 operation(s) for contact.

Documentation Provider Profile APIs.io OpenAPI GitHub

VBOUT Contact API is one of 15 APIs that VBOUT publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contact. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 18 operations across 18 paths. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, https://api.vbout.com/1.

18 operations 18 paths 0 schemas 2 DELETE9 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://api.vbout.com/1
Resource Areas
1

Paths & Operations 18

Across 18 paths, the API surfaces 18 operations — 2 DELETE, 9 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Contact 18
GET
EmailMarketing/GetContacts
Contacts
get-EmailMarketing-GetContacts 1 param → 200
GET
EmailMarketing/GetContactsByPhoneNumber
Contacts By Phone Number
get-EmailMarketing-GetContactsByPhoneNumber 1 param → 200
GET
EmailMarketing/GetContactByEmail
Contact By Email
get-EmailMarketing-GetContactByEmail 2 params → 200
GET
EmailMarketing/GetContact
Contact
get-EmailMarketing-GetContact 1 param → 200
POST
EmailMarketing/AddContact
Add Contact
post-EmailMarketing-AddContact 5 params
POST
EmailMarketing/EditContact
Edit Contact
post-EmailMarketing-EditContact 5 params
POST
EmailMarketing/SyncContact
Sync Contact
post-EmailMarketing-SyncContact 5 params
DELETE
EmailMarketing/DeleteContact
Delete Contact
delete-EmailMarketing-DeleteContact 2 params
POST
EmailMarketing/MoveContact
Move Contact
post-EmailMarketing-MoveContact 3 params
GET
EmailMarketing/GetContactTimeline
Contact Timeline
get-EmailMarketing-GetContactTimeline 2 params → 200
GET
EmailMarketing/GetContactTimelineByEmailAddress
Contact Timeline By Email Address
get-GetContactTimelineByEmailAddress 2 params → 200
GET
EmailMarketing/GetAudiences
Audiences
get-EmailMarketing-GetAudiences → 200
GET
EmailMarketing/GetLists
Lists
get-EmailMarketing-GetLists → 200
GET
EmailMarketing/GetList
List
get-EmailMarketing-GetList 1 param → 200
POST
EmailMarketing/AddList
Add List
post-EmailMarketing-AddList 14 params
POST
EmailMarketing/Editlist
Edit List
post-EmailMarketing-Editlist 15 params
DELETE
EmailMarketing/DeleteList
Delete List
delete-EmailMarketing-DeleteList 1 param
POST
EmailMarketing/AddActivity
Add Activity
post-EmailMarketing-AddActivity 3 params

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vbout-contact-api-openapi.yml Raw ↑

Other APIs VBOUT publishes across the network.

VBOUT Account API
AE Profile APIs.io
VBOUT AIchatbot API
AE Profile APIs.io
VBOUT Application API
AE Profile APIs.io
VBOUT Automation API
AE Profile APIs.io
VBOUT Email Marketing API
AE Profile APIs.io
VBOUT EmailMarketing API
AE Profile APIs.io
VBOUT Goals API
AE Profile APIs.io
VBOUT Help API
AE Profile APIs.io
VBOUT Pipeline API
AE Profile APIs.io
VBOUT Popups API
AE Profile APIs.io
VBOUT Settings API
AE Profile APIs.io
VBOUT Social Media API
AE Profile APIs.io
#Contact
← Back to V APIs
API Details
ID
vbout:vbout-contact-api
Base URL
https://api.vbout.com/1
Docs
https://developers.vbout.com
Provider
VBOUT
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=vbout-contact-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/vbout-contact-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of VBOUT Contact 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.