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

Alloy Entities API

Person and business entities, notes, merging, feedback, and groups.

Alloy Entities API is one of 19 APIs that Alloy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 13 operations across 10 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://sandbox.alloy.co/v1, https://alloy.co/v1, https://api.alloy.co/v1.

13 operations 10 paths 3 schemas 6 GET2 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.alloy.co/v1
Authentication
HTTP Basic, OAuth 2.0, HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 4

Alloy Entities API declares 4 security schemes for authenticating requests. It accepts HTTP basic authentication (basic). It supports OAuth 2.0 (oauth2) using the clientCredentials flow. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (bearerAuth).

  • basic — HTTP basic authorization using a workflow token and secret
  • oauth2 — OAuth2 using a workflow token and secret to generate a bearer token
  • basicAuth — HTTP Basic Authentication with workflow or account-level API key as username and secret as password.
  • bearerAuth — OAuth 2.0 bearer token obtained via the OAuth endpoints.

Paths & Operations 13

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

Entities 13

Entities are the center of the Alloy world. All evaluations, manual reviews, and documents are related to an entity whether or not you explicitly link them together in your API re…

GET
/entities/businesses/{entity_token}
Get a business entity
1 param → 200400
PATCH
/entities/businesses/{entity_token}
Update a business entity
1 param body → 200
GET
/entities/{entity_token}
Get Information Related to an Entity
1 param → 200
GET
/entities/persons/{entity_token}
Get a person entity
1 param → 200400
PATCH
/entities/persons/{entity_token}
Update a person entity
1 param body → 200
POST
/entities/businesses
Create a business entity
body → 201400
POST
/entities/{entity_token}/notes
Add a Note for an Entity
1 param body → 200
POST
/entities/merge
Merge two entities
body → 201
POST
/entities/persons
Create a person entity
body → 201400
GET
/entities/{entity_token}/evaluations/{evaluation_token}
Get an Entity Evaluation
getEntityEvaluation 2 params → 200
GET
/entity-feedback
List Entity Feedback
getEntityFeedback → 200
POST
/entity-feedback
Submit Entity Feedback
postEntityFeedback body → 201
GET
/entity-groups/{entity_token_or_external_id}
Get Entity Group by Token or External ID
getEntityGroup 1 param → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are EvaluationRequest (13 properties), Entity (7 properties), Note (3 properties). Each schema is shown below with its type and property counts.

Note
object
3 properties
EvaluationRequest
object
Payload submitted to evaluate an entity against an Alloy workflow.
13 properties
Entity
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alloy-com-entities-api-openapi.yml Raw ↑

Other APIs Alloy publishes across the network.

Alloy Bank Accounts API
Alloy Batches API
Alloy Cases API
Alloy Custom Lists API
Alloy Documents API
Alloy Evaluations API
Alloy Events API
Alloy Groups API
Alloy Investigations API
Alloy Journeys API
Alloy Lists API
Alloy OAuth API
Where this information came from

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