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

Kriya Buyers API

The Buyers API from Kriya — 6 operation(s) for buyers.

Kriya Buyers API is one of 6 APIs that Kriya publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 6 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0.

Requests are made against 3 base URLs: http://localhost:7071/api, https://api.kriya.dev/payments/, https://api.kriya.co/payments/.

6 operations 6 paths 13 schemas 4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.kriya.co/payments/
Contact
Resource Areas
1

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 4 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Buyers 6
PUT
/scenario/buyers/risk-decision
Updates buyer risk decision status for testing
BuyerRiskDecisionScenario body → 401400200
POST
/companies/search
Searches for companies
CompaniesSearch body → 401400200
POST
/buyers
Registers a new buyer company
CreateBuyer body → 201401400
POST
/buyers/pricing-scheme/single
Retrieves buyer payment options and fees
FindBuyerPricingScheme body → 200401404500
POST
/buyers/single
Fetches buyer company information
GetSingleBuyer body → 200401404500
PUT
/buyers/contact-details
Modifies buyer's contact information
UpdateBuyerContactDetails body → 401400201

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are getBuyerResponse (14 properties), updateBuyerContactDetailsRequest (9 properties), updateBuyerScenarioRequest (7 properties), createBuyerRequest (6 properties). Each schema is shown below with its type and property counts.

getSingleBuyerPricingSchemeRequest
object
5 properties
getSingleBuyerRequest
object
5 properties
companySearchRequest
object
6 properties
createBuyerRequest
object
6 properties
getBuyerResponse
object
14 properties
buyerPricingScheme
object
6 properties
problemDetails
object
5 properties
address
object
Director residential address.
6 properties
updateBuyerContactDetailsRequest
object
9 properties
directorDetails
objectnull
Company director details.
6 properties
buyerContactDetails
objectnull
Primary contact details of the company.
3 properties
updateBuyerScenarioRequest
object
7 properties
createBuyerResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kriya-buyers-api-openapi.yml Raw ↑

Other APIs Kriya publishes across the network.

Kriya Onboarding API API
Kriya OnboardingJourney API
Kriya Orders API
Kriya Payments API
Kriya Scenario API
Where this information came from

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