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

GetResponse Search Contacts API

Search Contacts API documentation API documentation The Search Contacts area of the GetResponse API v3 — 8 operation(s) across 5 path(s), split by tag from the provider-published OpenAPI at https://apireference.getresponse.com/open-api.json.

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

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

This API exposes 8 operations across 5 paths, and defines 19 schemas. It is described by OpenAPI 3.0.0, at version 3.2026-07-28T07:58:55+00:00.

Requests are made against 3 base URLs: https://api.getresponse.com/v3, https://api3.getresponse360.com/v3, https://api3.getresponse360.pl/v3.

8 operations 5 paths 19 schemas 1 DELETE3 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
3.2026-07-28T07:58:55+00:00
Base URL
https://api.getresponse.com/v3
Authentication
API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 2

GetResponse Search Contacts API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Auth-Token (api-key). It supports OAuth 2.0 (oauth2) using the implicit, authorizationCode and clientCredentials flows, exposing 1 scope.

  • api-key — Header value must be prefixed with api-key

Paths & Operations 8

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

Search Contacts 8

Search Contacts API documentation API documentation

GET
/search-contacts/{searchContactId}
Get search contacts by contact ID.
getSearchContactsById 2 params → 200404400401429
POST
/search-contacts/{searchContactId}
Update search contacts
updateSearchContacts 1 param body → 200404409400401429
DELETE
/search-contacts/{searchContactId}
Delete search contacts
deleteSearchContacts 1 param → 204404400401429
GET
/search-contacts/{searchContactId}/contacts
Get contacts by search contacts ID
getContactsByIdSearchContacts 7 params → 200404400401429
POST
/search-contacts/{searchContactId}/custom-fields
Upsert custom fields by search contacts
upsertCustomFieldsBySearchContactId 1 param body → 202404400401429
GET
/search-contacts
Get a saved search contact list
getSearchContactsList 8 params → 200400401429
POST
/search-contacts
Create search contacts
newSearchContacts body → 201409400401429
POST
/search-contacts/contacts
Search contacts using conditions
getContactsFromSearchContactsConditions 6 params body → 200400401429

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are SearchedContactDetails (10 properties), ErrorResponse (7 properties), SearchContactSection (5 properties), BaseSearchContacts (4 properties). Each schema is shown below with its type and property counts.

BaseSearchContacts
object
The short description of a saved search.
4 properties
BaseSearchContactsDetails
object
1 required
CampaignReference
object
3 properties 1 required
ConditionType
object
1 property 1 required
DateOrDateTime
ErrorResponse
object
7 properties 7 required
NewContactCustomFieldValue
object
2 properties 2 required
NewContactCustomFieldValues
object
1 property
NewSearchContacts
object
New search contacts.
3 required
SearchContactSection
object
5 properties 4 required
SearchContactsBySearchForm
object
3 required
SearchContactsConditionsDetails
object
2 properties 2 required
SearchContactsDetails
object
Search contact details.
4 required
SearchedContactDetails
object
10 properties
SortOrderEnum
string
SubscribersTypeEnumForSearching
object
1 property
SubscribersTypeEnumForSegments
object
1 property
UpdateSearchContacts
object
New search contacts.
3 required
UpsertContactCustomFields
object
1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

getresponse-search-contacts-openapi.yml Raw ↑

Other APIs GetResponse publishes across the network.

GetResponse API v3
GetResponse A/B tests API
GetResponse A/B tests - subject API
GetResponse Accounts API
GetResponse Addresses API
GetResponse Autoresponders API
GetResponse Campaigns (Lists) API
GetResponse Carts API
GetResponse Categories API
GetResponse Click Tracks API
GetResponse Contacts API
GetResponse Custom Events API
Where this information came from

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