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

Zepto Contacts (Receivable) API

The Contacts (Receivable) API from Zepto — 4 operation(s) for contacts (receivable).

Zepto Contacts (Receivable) API is one of 22 APIs that Zepto publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 2 base URLs: https://api.sandbox.zeptopayments.com, https://api.zeptopayments.com.

4 operations 4 paths 4 schemas 1 PATCH3 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.zeptopayments.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Zepto Contacts (Receivable) API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (bearerAuth) using the authorizationCode flow, exposing 9 scopes. By default, every request must be authenticated.

Paths & Operations 4

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

Contacts (Receivable) 4
POST
/contacts/receivable
Add a Receivable Contact
AddAReceivableContact 1 param body → 201404
POST
/contacts/{contact_id}/receivable/disable
Disable a Receivable Contact
DisableAReceivableContact 2 params → 204400404
POST
/contacts/{contact_id}/receivable/activate
Reactivate a Receivable Contact
ActivateAReceivableContact 2 params → 204400404
PATCH
/contacts/{contact_id}/receivable
Update a Receivable Contact
UpdateAReceivableContact 2 params body → 202400404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are AddAReceivableContactRequest (5 properties), AddAReceivableContactResponse (1 property), UpdateAReceivableContactRequest (1 property). Each schema is shown below with its type and property counts.

UpdateAReceivableContactRequest
object
1 property 1 required
AddAReceivableContactRequest
object
5 properties 2 required
Metadata
object
Use for your custom data and certain Zepto customisations.
AddAReceivableContactResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zepto-payments-contacts-receivable-api-openapi.yml Raw ↑

Other APIs Zepto publishes across the network.

Zepto Agreement modification API
Zepto Agreements API
Zepto Alias Resolution API
Zepto Bank Accounts API
Zepto Clients API
Zepto Contacts API
Zepto CoP Account Validations API
Zepto Disputes (Beta) API
Zepto Float Accounts API
Zepto Payment Requests API
Zepto Payments API
Zepto Payouts API
Where this information came from

This is an independent, third-party profile of Zepto Contacts (Receivable) 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.