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/hipay-merchant-group-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:
version: '0.3'
title: HiPay Marketplace Merchant Group API
description: "\nThe implementation of HiPay Marketplace involves establishing connections between your marketplace platform and HiPay based on a simple integration through a set of APIs.\n\n## Account creation:\n\n 1) The agent checks the e-mail availability with the [Is-available API](#/user-account/post_user-account_is-available).\n\n 2) The agent creates a HiPay account for merchants using the [User-account API](#/user-account/post_user-account).\n\n 3) The agent sends us the account number and the identification/KYC information using the [Identification API](#/identification/post_Identification). HiPay validates the identification/KYC information within three days and sends the agent a notification confirming that the merchant is fully operational.\n\n## Bank account information submission:\n\nPlease note that it is possible to submit bank account information any time between account creation and withdrawal requests.\nTo register a HiPay account bank information, use the [Bank-info API.](#/bank-info/post_user-account)\n\n## Fund allocation:\n\nFund allocation is only possible if the merchant's account is validated by HiPay.\n\nAll the funds are held in escrow before being deposited on the technical account.\n\nThe [Transfer API](#/transfer/post_transfer]) is then used to allocate funds from the technical account to the merchant's account.\nThe [Transfer API](#/transfer/post_transfer]) allows transfer requests to be made on the agent’s behalf or on the behalf of a third party.\n\nThe technical account is therefore a monitoring tool that provides a clear view of fund allocation (fund remittance, refunds, chargebacks).\n\n## Withdrawal requests:\n\nWithdrawal is only possible if the merchant's account AND banking informations are validated by HiPay.\n\nOnce funds are allocated, there are two withdrawal possibilities:\n\n - Whenever a transaction is made – please note that this option is not recommended by HiPay,\n - Whenever a withdrawal request is made by the merchant – for example, every ten days, depending on the agent.\n\nWhen agents want to do a withdrawal, they need to check the merchant’s account balance with the [Balance API.](#/balance/get_user-account)\n\n - In case of a zero balance, funds must be allocated with the [Transfer API](#/transfer/post_transfer]).\n - If the balance equals the amount of the allocated funds, a fund withdrawal request can be made with the [Withdrawal API](#/withdrawal/post_withdrawal). (The Withdrawal API allows for a withdrawal request to transfer money to the merchant’s bank account and also to the partner’s bank account.)\n - There must be a zero balance in the end.\n\n## Marketplace live testing:\n\nThis documentation describes the Marketplace API parameters and response fields and allows you to test the platform in real time.\n\n## Marketplace API base URLs:\n\n| Environment | Base URL |\n| --- | --- |\n| Test | https://test-professional.hipay.com/api/ |\n| Production | https://professional.hipay.com/api/ |\n\n## Authentication:\n\nAll requests to the HiPay Marketplace API require you to authenticate yourself using the HTTP *Basic Authentication* to convey your identity. Your API credentials can be found in [your Test HiPay Professional back office](https://test-merchant.hipaywallet.com/login). Most HTTP clients (including web browsers) have built-in support for HTTP Basic Authentication. If not, the following header must be included in all HTTP requests.\n\n`Authorization: Basic base64(\"<API login>:<API password>\")`\n"
servers:
- url: https://test-professional.hipay.com/api
tags:
- name: merchant-group
description: Manage merchant groups
paths:
/merchant-group/{merchant_group_code}.{_format}:
get:
summary: List merchant group member
description: '
### Information
List merchant group member.'
parameters:
- in: path
name: merchant_group_code
required: true
schema:
type: string
default: devportaltest
- in: path
name: _format
required: true
schema:
type: string
enum:
- json
- xml
default: json
- in: query
description: The date from which the member accounts were created
name: past_date
schema:
type: string
format: date
default: '2018-01-01'
- in: query
description: Account type
name: account_type[]
schema:
type: string
enum:
- merchant
- associator
- admin
default: merchant
- in: query
description: Number of results to display on each page. Default is 20
name: nb_result_per_page
schema:
type: integer
format: int32
default: 20
- in: query
description: Page number. First page has number 1. Default is 1
name: page
schema:
type: integer
format: int32
default: 1
- description: Account ID if operations must be made on an account other than yours (you must have specific rights on this account).
in: header
name: php-auth-subaccount-id
schema:
type: integer
- description: Account login (email address) if operations must be made on an account other than yours (you must have specific rights on this account).
in: header
name: php-auth-subaccount-login
schema:
type: string
responses:
'201':
description: Success response.
content:
application/json:
schema:
properties:
code:
type: integer
format: int32
description: Status code of the answer.
message:
type: string
description: Description of the answer.
merchant_group_name:
type: string
description: Merchant group name
account_type:
type: array
items:
type: string
description: List of account type
total_merchant:
type: integer
format: int32
description: Total merchant
past_date:
type: string
description: The date from which the member accounts were created
nb_result_per_page:
type: integer
format: int32
description: Number of result per page
page:
type: integer
format: int32
description: Page number
merchants_list:
type: array
items:
type: string
description: List of members
'400':
description: Validation failed.
'401':
description: Authentication failed.
tags:
- merchant-group
security:
- basicAuth: []
/merchant-group/{merchant_group_code}/count.{_format}:
get:
summary: Count merchant group member
description: '
### Information
Count merchant group member.'
parameters:
- in: path
name: merchant_group_code
required: true
schema:
type: string
default: devportaltest
- in: path
name: _format
required: true
schema:
type: string
enum:
- json
- xml
default: json
- in: query
description: The date from which the member accounts were created
name: past_date
schema:
type: string
format: date
default: '2018-01-01'
- in: query
description: Account type
name: account_type[]
schema:
type: string
enum:
- merchant
- associator
- admin
default: merchant
- description: Account ID if operations must be made on an account other than yours (you must have specific rights on this account).
in: header
name: php-auth-subaccount-id
schema:
type: integer
- description: Account login (email address) if operations must be made on an account other than yours (you must have specific rights on this account).
in: header
name: php-auth-subaccount-login
schema:
type: string
responses:
'201':
description: Success response.
content:
application/json:
schema:
properties:
code:
type: integer
format: int32
description: Status code of the answer.
message:
type: string
description: Description of the answer.
merchant_group_name:
type: string
description: Merchant group name
account_type:
type: array
items:
type: string
description: List of account type
total_merchant:
type: integer
format: int32
description: Total merchant
past_date:
type: string
description: The date from which the member accounts were created
'400':
description: Validation failed.
'401':
description: Authentication failed.
tags:
- merchant-group
security:
- basicAuth: []
components:
securitySchemes:
basicAuth:
type: http
scheme: basic