Sync a CRM object

curl --request POST \
  --url https://api.introw.io/api/v1/crm/objects/{objectType}/sync/{objectId} \
  --header 'x-api-key: <api-key>'

const options = {method: 'POST', headers: {'x-api-key': '<api-key>'}};

fetch('https://api.introw.io/api/v1/crm/objects/{objectType}/sync/{objectId}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

import requests

url = "https://api.introw.io/api/v1/crm/objects/{objectType}/sync/{objectId}"

headers = {"x-api-key": "<api-key>"}

response = requests.post(url, headers=headers)

print(response.text)

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

Sync a CRM object

You usually do not need this. Introw already syncs every connected CRM object automatically about every 15 minutes, so any change made in your CRM is reflected in Introw within the next sync window without any action on your part.

Use this endpoint only when a change must be reflected in Introw immediately rather than waiting for the next automatic sync. The typical case is a workflow that computes or mutates a value on the record and whose result must be persisted in Introw right away to keep data integrity. For example, an automation recalculates a field on a deal and that value has to be consistent in Introw at once for partner-facing views, commission calculations, or downstream logic, instead of up to ~15 minutes later.

It forces Introw to re-fetch the single object from your connected CRM (HubSpot or Salesforce) and re-ingest it on demand. objectId is that record’s id in the CRM. The object is ingested in the context of your linked partners, so partner associations are resolved as part of the sync.

objectType takes your CRM’s own name for the object, case-insensitively. Introw translates it, so there is nothing to look up or map on your side:

Deal: Salesforce Opportunity, HubSpot Deal
Company: Salesforce Account, HubSpot Company
Ticket: Salesforce Case, HubSpot Ticket
Contact: Contact in both
Lead: Lead in both

Introw’s own type names (DEAL, COMPANY, TICKET, CONTACT, LEAD) and HubSpot object type ids (0-3, 0-2, 0-5, 0-1, 0-136) resolve to the same objects. Custom objects are the one case where the exact name matters: pass the object’s API name as your CRM shows it, for example Partner_Program__c in Salesforce or p_partner_application / 2-12345 in HubSpot. Custom types are used verbatim, not translated.

Authenticated by API key only: no specific scope is required. On success the endpoint returns 204 No Content and does not return the synced object; read it back from the relevant resource if you need the ingested state.

POST

api

crm

objects

{objectType}

sync

{objectId}

Sync a CRM object

curl --request POST \
  --url https://api.introw.io/api/v1/crm/objects/{objectType}/sync/{objectId} \
  --header 'x-api-key: <api-key>'

const options = {method: 'POST', headers: {'x-api-key': '<api-key>'}};

fetch('https://api.introw.io/api/v1/crm/objects/{objectType}/sync/{objectId}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

import requests

url = "https://api.introw.io/api/v1/crm/objects/{objectType}/sync/{objectId}"

headers = {"x-api-key": "<api-key>"}

response = requests.post(url, headers=headers)

print(response.text)

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

{
  "error": {
    "code": "<string>",
    "message": "<string>",
    "details": "<unknown>"
  }
}

Authorizations

x-api-key

string

header

required

Introw API key shown once when the credential is created.

Path Parameters

objectType

string

required

Type of CRM object to sync, in your CRM's own wording (Opportunity, Deal, Account, Company, …) or a custom object's API name. See the description above. Type of CRM object to sync, in your own CRM's wording. Introw translates it: Salesforce Opportunity, Account, Case and HubSpot Deal, Company, Ticket are all accepted (case-insensitive), as are Introw's own DEAL, COMPANY, TICKET, CONTACT, LEAD. For a custom object, pass its API name exactly as your CRM shows it (for example Partner_Program__c or p_partner_application).

Required string length: 1 - 255

objectId

string

required

Identifier of the CRM object to sync, as it appears in your CRM. Identifier of the CRM object to sync.

Required string length: 1 - 255

Response

CRM object was fetched and ingested successfully. No content is returned.

⌘I

INTROW API

Use cases

Partner API

Forms API

CRM API

Commission payouts API

Commission lines API

Collaboration API

Embed API

Affiliate API

Sync a CRM object

Authorizations

Path Parameters

Response