Kriya Scenario API
The Scenario API from Kriya — 1 operation(s) for scenario.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/kriya-scenario-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Kriya Onboarding Scenario API
description: '# Introduction
Welcome to Onboarding API, an extension to the existing KriyaPaymentsApi platform that allows partners to automate onboarding process, and to view results of these checks in a simple way.'
contact:
name: Support
url: https://kriya.co/
email: apisupport@kriya.co
version: ''
x-logo:
url: https://cdn.kriya.co/images/Kriya-Putty-Large.svg
backgroundColor: '#00283C'
altText: Kriya Logo
servers:
- url: https://api.kriya.dev/onboarding/
description: Test Environment
- url: https://api.kriya.co/onboarding/
description: Production Environment
tags:
- name: Scenario
paths:
/scenario/onboardingStatus:
put:
tags:
- Scenario
summary: Update onboarding status for testing purposes.
description: Update onboarding status for testing purposes. Only available in the staging environment.
operationId: UpdateOnboardingStatusScenario
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/updateOnboardingStatusScenarioCommand'
required: true
responses:
'404':
description: Payload of ProblemDetails
content:
application/json:
schema:
$ref: '#/components/schemas/problemDetails'
'401':
description: Payload of ProblemDetails
content:
application/json:
schema:
$ref: '#/components/schemas/problemDetails'
'400':
description: Payload of ProblemDetails
content:
application/json:
schema:
$ref: '#/components/schemas/problemDetails'
'200':
description: No description
components:
schemas:
problemDetailsError:
type: object
properties:
code:
type: string
message:
type: string
updateOnboardingStatusScenarioCommand:
type: object
properties:
merchantCompanyIdentifier:
type: string
onboardingStatus:
type: string
problemDetails:
type: object
properties:
title:
type: string
errors:
type: array
items:
$ref: '#/components/schemas/problemDetailsError'
date:
type: string
format: date-time
operationId:
type: string
message:
type: string
metadata:
type: object
additionalProperties:
type: object
reasons:
type: array
items:
$ref: '#/components/schemas/iError'
statusCode:
enum:
- 100
- 101
- 102
- 103
- 200
- 201
- 202
- 203
- 204
- 205
- 206
- 207
- 208
- 226
- 300
- 300
- 301
- 301
- 302
- 302
- 303
- 303
- 304
- 305
- 306
- 307
- 307
- 308
- 400
- 401
- 402
- 403
- 404
- 405
- 406
- 407
- 408
- 409
- 410
- 411
- 412
- 413
- 414
- 415
- 416
- 417
- 421
- 422
- 422
- 423
- 424
- 426
- 428
- 429
- 431
- 451
- 500
- 501
- 502
- 503
- 504
- 505
- 506
- 507
- 508
- 510
- 511
type: integer
format: int32
default: 100
iError:
type: object
properties:
reasons:
type: array
items:
$ref: '#/components/schemas/iError'