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

GetAccept Contacts API

Everything related to contacts

GetAccept Contacts API is one of 12 APIs that GetAccept publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contacts. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.0.0, at version 1.6.

Requests are made against a single base URL, https://api.getaccept.com/v1.

3 operations 2 paths 3 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.6
Base URL
https://api.getaccept.com/v1
Authentication
OAuth 2.0, HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 2

GetAccept Contacts API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (Oauth2) using the authorizationCode flow, exposing 1 scope. It accepts HTTP bearer tokens (JWT) (Token). By default, every request must be authenticated.

  • Oauth2 — For testing purpose, use clientid api and clientsecret app
  • Token — Enter your bearer token

Paths & Operations 3

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

Contacts 3

Everything related to contacts

GET
/contacts
List contacts
ListContacts 8 params → 200401
POST
/contacts
Create contact
CreateContact body → 200400401
DELETE
/contacts/{contactId}
Delete contact
DeleteContact 1 param → 204401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Contact (16 properties), Error (3 properties), Contacts (1 property). Each schema is shown below with its type and property counts.

Error
object
3 properties
Contacts
object
Contact list
1 property
Contact
object
Every unique e-mail address (or mobile number) is defined as a contact.
16 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

getaccept-contacts-api-openapi.yml Raw ↑

Other APIs GetAccept publishes across the network.

GetAccept Archive API
GetAccept Attachments API
GetAccept Authentication API
GetAccept Communication Templates API
GetAccept Custom Data API
GetAccept Documents API
GetAccept Others API
GetAccept Subscriptions API
GetAccept Templates API
GetAccept Users API
GetAccept Videos API
Where this information came from

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