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

Velaris Entity Management V2 API

The Entity Management V2 API from Velaris — 11 operation(s) for entity management v2.

Velaris Entity Management V2 API is one of 14 APIs that Velaris publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 11 operations across 11 paths. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, https://api.euw1.velaris.io.

11 operations 11 paths 0 schemas 5 GET6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.euw1.velaris.io
Authentication
HTTP Bearer, HTTP Basic
Contact
Resource Areas
1

Authentication & Security 2

Velaris Entity Management V2 API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • bearerAuth — User-scoped access token. Header: Authorization: Bearer {accesstoken}. Create under Profile Security Access token.
  • basicAuth — Legacy. Base64(username:password). Not available for SSO/MFA tenants.

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 5 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Entity Management V2 11
GET
/v2/organizations
Get All Organizations
getAllOrganizations → 200
POST
/v2/organizations/search
Search Organization
searchOrganization body → 200
GET
/v2/accounts
Get All Accounts
getAllAccounts → 200
POST
/v2/accounts/search
Search Accounts
searchAccounts body → 200
GET
/v2/contacts
Get All Contacts
getAllContacts → 200
POST
/v2/contacts/batch/read
Get Contacts by Emails
getContactsByEmails body → 200
POST
/v2/contacts/search
Search Contacts
searchContacts body → 200
GET
/v2/opportunities
Get All Opportunities
getAllOpportunities → 200
POST
/v2/opportunities/search
Search Opportunities
searchOpportunities body → 200
GET
/v2/risks
Get All Risks
getAllRisks → 200
POST
/v2/risks/search
Search Risks
searchRisks body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

velaris-entity-management-v2-api-openapi.yml Raw ↑

Other APIs Velaris publishes across the network.

Velaris Activity API
Velaris Attribute Change Log API
Velaris Currencies API
Velaris Custom Objects API
Velaris Entity Management V1 API
Velaris Field Definitions API
Velaris Integrations API
Velaris Lifecycles API
Velaris Notes API
Velaris Surveys API
Velaris Tasks API
Velaris Ticketing API
Where this information came from

This is an independent, third-party profile of Velaris Entity Management V2 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.