Merge Subpackage Contacts API

The subpackage_contacts API from Merge — 14 operation(s) for subpackage_contacts.

GitHub OpenAPI

Operations 19

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /accounting/v1/contacts List customers and suppliers in the accounting system · List #
Ask an LLM
“How do I pull every customer and vendor contact from a linked accounting platform through Merge?”
“Can I filter accounting contacts to only suppliers, or only customers?”
Tell an agent
List the accounting contacts flagged as suppliers.
Find accounting contacts with email {email_address}.
POST /accounting/v1/contacts Create a customer or vendor in accounting · Create #
Ask an LLM
“Can I add a new vendor to my customer's accounting ledger through a unified API?”
“What happens if I ask for the new accounting contact to be written asynchronously?”
Tell an agent
Add a new accounting contact with these details: {contact}.
Create supplier {contact} in the linked accounting system asynchronously.
GET /accounting/v1/contacts/{id} Get one accounting contact · Retrieve #
Ask an LLM
“How can I look up a single vendor or customer record from the accounting integration?”
“Can I see the raw third-party payload behind one accounting contact?”
Tell an agent
Get accounting contact {id}.
Fetch accounting contact {id} with {relations} expanded.
PATCH /accounting/v1/contacts/{id} Update an accounting contact · Partial Update #
Ask an LLM
“Can I change a supplier's details in the accounting system after it was created?”
“How do I edit only some fields on an existing accounting contact?”
Tell an agent
Update accounting contact {id} with {changes}.
Change the email on accounting vendor {id} to the value in {changes}.
GET /accounting/v1/contacts/meta/patch/{id} See which accounting contact fields can be edited · Meta Patch Retrieve #
Ask an LLM
“Which fields on an accounting contact am I allowed to update for this integration?”
“Is there a way to check the edit schema before patching an accounting contact?”
Tell an agent
Show the editable fields for accounting contact {id}.
Get the update metadata for accounting contact {id} before I change it.
GET /accounting/v1/contacts/meta/post See which fields creating an accounting contact takes · Meta Post Retrieve #
Ask an LLM
“What fields does the linked accounting platform require when creating a new contact?”
“Can I check the create schema for accounting contacts before posting one?”
Tell an agent
Show the required fields for creating an accounting contact on linked account {account_token}.
Get the accounting contact creation metadata.
GET /accounting/v1/contacts/remote-field-classes List custom field definitions for accounting contacts · Remote Field Classes List #
Ask an LLM
“Which custom fields exist on contacts in my customer's accounting software?”
“Can I list only the custom remote fields for accounting contacts, not the common ones?”
Tell an agent
List the remote field classes for accounting contacts on linked account {account_token}.
Show only custom field classes defined on accounting contacts.
GET /crm/v1/contacts List CRM contacts · List #
Ask an LLM
“How do I pull all the people from a customer's CRM?”
“Can I find CRM contacts by phone number or by several email addresses at once?”
Tell an agent
List CRM contacts under account {account_id}.
Find CRM people matching emails {email_addresses}.
POST /crm/v1/contacts Create a contact in the CRM · Create #
Ask an LLM
“Can I push a new lead's person record into my customer's CRM?”
“What do I send to add a person to a linked CRM?”
Tell an agent
Create a CRM contact from {contact}.
Add person {contact} to the linked CRM in debug mode.
GET /crm/v1/contacts/{id} Get one CRM contact · Retrieve #
Ask an LLM
“How do I read one person's record from the linked CRM?”
“Can I include the CRM's custom fields when fetching a single contact?”
Tell an agent
Get CRM contact {id}.
Fetch CRM person {id} including remote custom fields.
PATCH /crm/v1/contacts/{id} Update a CRM contact · Partial Update #
Ask an LLM
“Can I edit a person's details in the CRM through Merge?”
“How do I change just the title or phone on an existing CRM contact?”
Tell an agent
Update CRM contact {id} with {changes}.
Patch the CRM person {id} so their details match {changes}.
POST /crm/v1/contacts/ignore/{model_id} Stop syncing a CRM contact · Ignore Create #
Ask an LLM
“How do I exclude a specific CRM contact from future syncs, say for a GDPR request?”
“What happens to a CRM contact's data once I mark it ignored?”
Tell an agent destructive · confirm first
Ignore CRM contact {model_id} for reason {reason}.
Stop syncing CRM contact {model_id} with the note {message}.
GET /crm/v1/contacts/meta/patch/{id} See which CRM contact fields can be edited · Meta Patch Retrieve #
Ask an LLM
“Which fields can I update on a person in the linked CRM?”
“Is there a schema for patching a CRM contact that I can read first?”
Tell an agent
Show the patchable fields for CRM contact {id}.
Get the CRM contact edit metadata for {id}.
GET /crm/v1/contacts/meta/post See which fields creating a CRM contact takes · Meta Post Retrieve #
Ask an LLM
“What does the linked CRM need before I can create a new person record?”
“Can I read the create-contact schema for a CRM integration?”
Tell an agent
Show the CRM contact creation fields for linked account {account_token}.
Get the create metadata for CRM people.
GET /crm/v1/contacts/remote-field-classes List custom field definitions for CRM contacts · Remote Field Classes List #
Ask an LLM
“What custom properties are defined on contacts in my customer's CRM?”
“Can I tell which CRM contact fields are common-model fields versus custom ones?”
Tell an agent
List CRM contact remote field classes for linked account {account_token}.
Show the custom property definitions on CRM people.
GET /ticketing/v1/contacts List ticketing contacts · List #
Ask an LLM
“How do I get the requesters and end customers stored in a help desk?”
“Can I find a ticketing contact by email?”
Tell an agent
List help desk contacts with email {email_address}.
Show ticketing contacts modified after {modified_after}.
POST /ticketing/v1/contacts Create a contact in the ticketing system · Create #
Ask an LLM
“Can I add a new requester to my customer's help desk?”
“What do I send to create a ticketing contact?”
Tell an agent
Create a help desk contact from {contact}.
Add requester {contact} to the ticketing platform.
GET /ticketing/v1/contacts/{id} Get one ticketing contact · Retrieve #
Ask an LLM
“How do I read a single requester record from the help desk?”
“Can I expand related records on a ticketing contact when I fetch it?”
Tell an agent
Get ticketing contact {id}.
Fetch help desk requester {id} and expand {relations}.
GET /ticketing/v1/contacts/meta/post See which fields creating a ticketing contact takes · Meta Post Retrieve #
Ask an LLM
“Which fields does the help desk accept when I create a requester?”
“Can I check the ticketing contact create schema first?”
Tell an agent
Show the ticketing contact creation fields for linked account {account_token}.
Get the help desk requester create metadata.

Documentation

Specifications

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/hris-api-employee-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/hris-api-employee-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/ats-api-candidate-schema.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/ats-api-application-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/ats-api-candidate-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/accounting-api-invoice-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/accounting-api-invoice-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/ticketing-api-ticket-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/ticketing-api-ticket-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/crm-api-opportunity-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/crm-api-opportunity-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/file-storage-api-file-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/file-storage-api-file-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/knowledge-base-api-article-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/knowledge-base-api-article-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/chat-api-message-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/chat-api-message-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/agent-handler-tool-pack-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/agent-handler-tool-pack-structure.json
📊
JSONSchema
https://artifacts.apis.io/merge/json-schema/gateway-response-schema.json
📊
JSONStructure
https://artifacts.apis.io/merge/json-structure/gateway-response-structure.json

Other Resources

🔗
Website
https://www.merge.dev/categories/hr-payroll-api
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-hris-api-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/hris-api-employee-example.json
🔗
Website
https://www.merge.dev/categories/ats-recruiting-api
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-ats-api-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/ats-api-candidate-example.json
🔗
Examples
https://artifacts.apis.io/merge/examples/ats-api-application-example.json
🔗
Website
https://www.merge.dev/categories/accounting-api
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-accounting-api-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/accounting-api-invoice-example.json
🔗
Website
https://www.merge.dev/categories/ticketing-api
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-ticketing-api-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/ticketing-api-ticket-example.json
🔗
Website
https://www.merge.dev/categories/crm-api
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-crm-api-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/crm-api-opportunity-example.json
🔗
Website
https://www.merge.dev/categories/file-storage-api
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-file-storage-api-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/file-storage-api-file-example.json
🔗
Website
https://www.merge.dev/categories/knowledge-base
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-knowledge-base-api-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/knowledge-base-api-article-example.json
🔗
Website
https://www.merge.dev/categories/chat
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-chat-api-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/chat-api-message-example.json
🔗
Website
https://www.merge.dev/merge-agent-handler
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-agent-handler-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/agent-handler-tool-pack-example.json
🔗
Support
https://help.ah.merge.dev/
🔗
Website
https://www.merge.dev/gateway
🔗
JSONLD
https://artifacts.apis.io/merge/json-ld/merge-gateway-context.jsonld
🔗
Examples
https://artifacts.apis.io/merge/examples/gateway-response-example.json

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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/merge:merge-subpackage-contacts-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

merge-subpackage-contacts-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Merge Subpackage Contacts API
  version: 1.0.0
  description: 'Operations tagged subpackage_contacts across 3 of this provider''s published API definitions: merge-accounting-api-openapi.yaml, merge-crm-api-openapi.yaml, merge-ticketing-api-openapi.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.merge.dev/api
- url: https://api-eu.merge.dev/api
- url: https://api-ap.merge.dev/api
tags:


# --- truncated at 32 KB (86 KB total) ---
# Full source: https://artifacts.apis.io/merge/openapi/merge-subpackage-contacts-api-openapi.yml