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

Veritus Customers API

The Customers API from Veritus — 12 operation(s) for customers.

Veritus Customers API is one of 4 APIs that Veritus publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 12 operations across 12 paths, and defines 28 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://sandbox.veritus.com/api/v1.

12 operations 12 paths 28 schemas 1 DELETE1 PATCH10 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://app.veritus.com/api/v1
Authentication
HTTP Bearer
License
MIT
Resource Areas
1

Authentication & Security 1

Veritus Customers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 12

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

Customers 12
POST
/customers
Create a new customer. Once created, you can use the customer ID to enroll them into drip campaigns or make outbound calls.
body → 200401400409500
POST
/customers/bulk
Create multiple customers in a single request. Returns partial success - some customers may be created while others fail validation or already exist.
body → 200401400500
PATCH
/customers/{customerId}
Update an existing customer's information. All fields are optional - only provide the fields you want to update.
1 param body → 200400401404500
POST
/customers/{customerId}/drip-campaigns
Enrolls a customer into a drip campaign. The customer is run through a compliance engine first. If compliance checks pass, the drip campaign is started immediately or scheduled for the next compliant…
body
POST
/customers/{customerId}/calls
Creates an outbound voice call to a customer. The customer is run through a compliance engine first. If compliance checks pass, the call is initiated. If the checks fail, the request will return an e…
body → 200400422500
DELETE
/customers/{customerId}/drip-campaigns/{dripCampaignId}
Cancel a drip campaign.
body → 200
POST
/customers/{customerId}/interactions/sms/import
Import a single SMS interaction for a customer. Use this to sync historical SMS messages or record SMS conversations from external systems.
1 param body → 200400401404500
POST
/customers/{customerId}/interactions/sms/import/bulk
Import multiple SMS interactions for a customer in a single request. Returns partial success - some messages may be imported while others fail validation.
1 param body → 200400401404500
POST
/customers/{customerId}/interactions/sms/generate
Generate an AI-powered SMS response for a customer. The generated message can optionally be persisted as an outbound interaction.
1 param body → 200400401404422500
POST
/customers/{customerId}/interactions/email/generate
Generate an AI-powered email response for a customer. The generated email can optionally be persisted as an outbound interaction.
1 param body → 200400401404500
POST
/customers/{customerId}/interactions/email/import
Import a single email interaction for a customer. Use this to sync historical emails or record email conversations from external systems.
1 param body → 200400401404500
POST
/customers/{customerId}/interactions/email/import/bulk
Import multiple email interactions for a customer in a single request. Returns partial success - some emails may be imported while others fail validation.
1 param body → 200400401404500

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are Customer (12 properties), CreateCustomerRequest (12 properties), EmailImportRequest (11 properties), UpdateCustomerRequest (10 properties). Each schema is shown below with its type and property counts.

EmailImportRequest
object
11 properties 5 required
UpdateCustomerRequest
object
10 properties
SmsGenerateRequest
object
4 properties 1 required
SmsImportBulkResponse
object
3 properties 3 required
CreateCallResponse
object
3 properties 3 required
Customer
object
12 properties 7 required
CustomersDripCampaignsPostRequest
object
2 properties 1 required
SmsImportRequest
object
7 properties 5 required
UpdateCustomerResponse
object
3 properties 3 required
BulkCreateCustomersRequest
object
1 property 1 required
EmailGenerateResponse
object
3 properties 3 required
EmailImportBulkResponse
object
3 properties 3 required
EmailImportResponse
object
3 properties 3 required
BulkCustomerSuccess
object
2 properties 2 required
CreateCustomerRequest
object
12 properties 6 required
BulkCustomerFailure
object
3 properties 3 required
ComplianceCheck
object
4 properties 4 required
Compliance
object
3 properties 3 required
BulkCustomerResult
EmailGenerateRequest
object
2 properties
CreateCallRequest
object
2 properties 1 required
SmsInteractionData
object
7 properties 7 required
EmailInteractionData
object
8 properties 7 required
SmsGenerateResponse
object
3 properties 3 required
SmsImportBulkRequest
object
1 property 1 required
BulkCreateCustomersResponse
object
3 properties 3 required
SmsImportResponse
object
3 properties 3 required
EmailImportBulkRequest
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

veritus-customers-api-openapi.yml Raw ↑

Other APIs Veritus publishes across the network.

Veritus Calls API
Veritus Clients API
Veritus Interactions API
Where this information came from

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