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 Journeys API

Multi-step decisioning journeys, applications, batches, and reviews.

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

Tagged areas include Journeys. 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 17 operations across 14 paths, and defines 2 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.

17 operations 14 paths 2 schemas 7 GET1 PATCH6 POST3 PUT

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 Journeys 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 17

Across 14 paths, the API surfaces 17 operations — 7 GET, 1 PATCH, 6 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Journeys 17

A Journey is a decision configuration that allows you to run multiple workflows.

GET
/journeys/{journey_token}/applications/{journey_application_token}
Get Journey Application
5 params → 200401404429500503
PUT
/journeys/{journey_token}/applications/{journey_application_token}
Update Journey Application
4 params body → 200400401404409429500503
POST
/journeys/{journey_token}/applications
Create Journey Application
9 params body → 201400401404409429500503
GET
/journeys/{journey_token}/applications/{journey_application_token}/notes
List Journey Application Notes
getJourneyApplicationNotes 2 params → 200
POST
/journeys/{journey_token}/applications/{journey_application_token}/notes
Add a Note to a Journey Application
postJourneyApplicationNote 2 params body → 201
POST
/journeys/{journey_token}/applications/{journey_application_token}/rerun
Rerun a Journey Application
postJourneyApplicationRerun 2 params → 201
POST
/journeys/{journey_token}/applications/{journey_application_token}/review
Submit a Journey Application Review
postJourneyApplicationReview 2 params body → 201
PATCH
/journeys/{journey_token}/applications/{journey_application_token}/auditaccess
Audit Access to a Journey Application
patchJourneyApplicationAuditAccess 2 params → 200
PUT
/journeys/{journey_token}/applications/{journey_application_token}/nodes/{node_id}
Update a Journey Application Node
putJourneyApplicationNode 3 params body → 200
GET
/journeys/{journey_token}/applications/{journey_application_token}/review/{manual_review_token}
Get a Manual Review for a Journey Application
getJourneyApplicationManualReview 3 params → 200
POST
/journeys/{journey_token}/applications/{journey_application_token}/cases/{case_token}/review
Submit a Case Review for a Journey Application
postJourneyApplicationCaseReview 3 params body → 201
GET
/journeys/applications/ext/{external_application_id}/latest
Get the Latest Application by External ID
getJourneyApplicationByExternalId 1 param → 200
PUT
/journeys/applications/ext/{external_application_id}/latest
Update the Latest Application by External ID
putJourneyApplicationByExternalId 1 param body → 200
POST
/journeys/applications/ext/{external_application_id}/latest/rerun
Rerun the Latest Application by External ID
postJourneyApplicationRerunByExternalId 1 param → 201
GET
/journeys/entities/{external_entity_id}/applications
List Applications for an External Entity
getJourneyApplicationsByExternalEntity 1 param → 200
GET
/journeys/{journey_token}/parameters
Get Journey Parameters
getJourneyParameters 1 param → 200
GET
/journeys/{journey_token}/schema
Get Journey Schema
getJourneySchema 1 param → 200

Schemas 2

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

Note
object
3 properties
JourneyApplication
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

alloy-com-journeys-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 Entities API
Alloy Evaluations API
Alloy Events API
Alloy Groups API
Alloy Investigations API
Alloy Lists API
Alloy OAuth API
Where this information came from

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