For the complete documentation index, see llms.txt. This page is also available as Markdown.

Get counterparty list

Retrieves a paginated list of counterparties (business partners, clients, or related entities) with comprehensive filtering options and detailed profile information.

Endpoint

GET /v2/counterparty

Link

Request

Query Parameters

All parameters are optional. Use them to filter the counterparty list.

Parameter

Type

Description

Example

counterpartyId

string

Filter by counterparty ID.

"cp_12345"

counterpartyName

string

Filter by counterparty name.

"Tech Supplies"

customerId

string

Filter by customer ID.

"cust_67890"

customerName

string

Filter by customer name.

"John Doe"

fromCreatedAt

string

Filter from creation date (ISO 8601).

"2024-01-01T00:00:00Z"

toCreatedAt

string

Filter to creation date (ISO 8601).

"2024-12-31T23:59:59Z"

meta.page

integer

Page number (starts from 0).

0

meta.pageSize

integer

Items per page.

20

Headers

Key

Value

Required

Authorization

123

Yes

Accept

application/json

Yes


Response (200 OK)

Returns a paginated list of counterparties with complete details.

Response Fields

1. Meta (Pagination)

Field

Type

Description

Example

pageSize

integer

Items per page.

20

page

integer

Current page (0-indexed).

0

total

string

Total items count.

"150"

2. Items (Counterparty Array)

Field

Type

Description

Example

id

string

Counterparty unique ID.

"cp_12345"

description

string

Counterparty description.

"Primary electronics supplier"

createdAt

string

Creation timestamp.

"2024-01-15T10:30:00Z"

updatedAt

string

Last update timestamp.

"2024-05-20T14:45:00Z"

3. Customer Object

Field

Type

Description

Example

id

string

Customer ID.

"cust_67890"

name

string

Customer name.

"John Doe"

phone

string

Customer phone.

"+1234567890"

email

string

Customer email.

"[email protected]"

status

string

Customer status: - NEW - READY_FOR_MODERATION - MODERATED - VERIFY - ACCEPT - REJECT - BANNED

"ACCEPT"

4. Profile Object

Field

Type

Description

Required

Example

name

string

Legal name.

Yes

"Tech Supplies Corp"

email

string

Contact email.

No

"[email protected]"

phoneNumber

string

Contact phone.

No

"+19876543210"

taxNumber

string

Tax ID number.

No

"TAX-US-12345"

dateOfBirth

string

Date of birth/incorporation.

No

"1985-05-15T00:00:00Z"

website

string

Company website.

No

"https://techsupplies.com"

lastname

string

Last name (individuals).

No

"Smith"

5. Address Object

Field

Type

Description

Required

Example

addressLine1

string

Primary address.

Yes

"123 Main Street"

addressLine2

string

Suite/floor.

No

"Suite 500"

addressLine3

string

Additional info.

No

"Building B"

city

string

City.

No

"New York"

stateIso

string

State code.

No

"NY"

countryIso

string

Country code.

No

"US"

postalCode

string

Postal code.

No

"10001"

unitNumber

string

Unit number.

No

"5A"

6. AdditionalInfo Object

Field

Type

Description

Allowed Values

Example

type

string

Legal structure.

INDIVIDUAL, CORPORATION

"CORPORATION"

businessLine

string

Industry type.

PLB_AUTOMOTIVE, PLB_RETAIL, PLB_HIGH_TECH_SOFTWARE_TELECOMS, etc.

"PLB_HIGH_TECH_SOFTWARE_TELECOMS"

relationship

string

Business relationship.

PRC_SUPPLIER, PRC_CUSTOMER, PRC_BUSINESS_PARTNER, etc.

"PRC_SUPPLIER"

Example Response:

json


Examples

Request

bash

Individual Counterparty Example

Response:

json


Error Responses

  1. Unauthorized:

    json

  2. Invalid Parameters:

    json


Notes

  • Pagination: Use meta.page and meta.pageSize for large datasets

  • Filtering: Combine multiple filters for precise searches

  • Address Validation: addressLine1 is required for KYC compliance

  • Business Lines: Extensive industry classification available

  • Relationships: Defines the business context of the counterparty

Common Use Cases:

  • Supplier/vendor management

  • Client portfolio review

  • Compliance auditing

  • Relationship mapping

Request sample

Response sample

Last updated