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

HitPay Beneficiaries API

The Beneficiaries API from HitPay — 3 operation(s) for beneficiaries.

HitPay Beneficiaries API is one of 24 APIs that HitPay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 2 base URLs: https://api.hit-pay.com, https://api.sandbox.hit-pay.com.

6 operations 3 paths 6 schemas 1 DELETE2 GET1 PATCH2 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.hit-pay.com/v1
Resource Areas
1

Paths & Operations 6

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

Beneficiaries 6
POST
/v1/beneficiaries/schema
Get the API schema
get-schema 1 param body → 200422
POST
/v1/beneficiaries
Create a new beneficiary
create-beneficiary 1 param body → 201422
GET
/v1/beneficiaries
Get list of beneficiaries
get-all-beneficiary 3 params → 200
PATCH
/v1/beneficiaries/{beneficiary_id}
Update existing beneficiary
update-beneficiary 2 params body → 200422
DELETE
/v1/beneficiaries/{beneficiary_id}
Delete existing beneficiary
delete-beneficiary 2 params → 204
GET
/v1/beneficiaries/{beneficiary_id}
Get a beneficiary by ID
get-beneficiary-detail 2 params → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are beneficiary-bd-local (13 properties), beneficiary-php-local (13 properties), beneficiary-sqd-fast (12 properties), beneficiary-bd-upay (11 properties). Each schema is shown below with its type and property counts.

beneficiary-php-local
object
13 properties 8 required
beneficiary-bd-bkash
object
11 properties 7 required
beneficiary-bd-tap
object
11 properties 7 required
beneficiary-bd-local
object
13 properties 9 required
beneficiary-bd-upay
object
11 properties 7 required
beneficiary-sqd-fast
object
12 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hitpay-beneficiaries-api-openapi.yml Raw ↑

Other APIs HitPay publishes across the network.

HitPay Account Status API
HitPay Balances API
HitPay Charge API
HitPay Charges API
HitPay Customers API
HitPay Invoices API
HitPay Notifications API
HitPay Orders API
HitPay Payment Requests API
HitPay Product Category API
HitPay Products API
HitPay Readers API
Where this information came from

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