The field a module’s records are named by

GET

/orgs/{org}/connectors/{id}/records/{module}/naming-field

curl --request GET \
  --url https://api.sloose.com/orgs/org_9f3c/connectors/cnn_9f2a/records/Accounts/naming-field \
  --header 'Authorization: Bearer <token>'

• Production
• Staging

Which field names a module’s records — Zoho’s display_field: Account_Name, Full_Name, Vendor_Name — which is what a lookup’s values are searched by when the page asks the CRM about a file’s own values (#1133), rather than reading a list of the module’s records. Read from the module’s own metadata the first time it is asked and kept on the connection’s module, as every read here keeps it, so the CRM is asked once per module. field is null when the CRM names none. Only a module of the connection, as its discovery read it (MODULE_NOT_FOUND).

Authorizations

• sessionAuth
• apiTokenAuth

Parameters

Path Parameters

org

required

The org id the session was issued for. A token for one org can never read another.

string

Example

org_9f3c

The org id the session was issued for. A token for one org can never read another.

id

required

The connector id, from GET /orgs/{org}/connectors.

string

Example

cnn_9f2a

The connector id, from GET /orgs/{org}/connectors.

module

required

The module’s API name in the destination.

string

Example

Accounts

The module’s API name in the destination.

Responses

200

The field the module’s records are named by.

Media typeapplication/json

object

field

required

The field’s API name, or null when the CRM names none.

string | null

Example^generated

{
  "field": "example"
}

401

No bearer, or one that is expired, revoked or no longer resolves to a member.

Media typeapplication/json

The error envelope every non-2xx answer uses.

object

error

required

Human-readable explanation.

string

code

Machine-readable reason. Absent on a few legacy 400s.

string

key

additional properties

Example^generated

{
  "error": "example",
  "code": "example"
}

403

The bearer’s role is too low, or it was issued for a different org.

Media typeapplication/json

The error envelope every non-2xx answer uses.

object

error

required

Human-readable explanation.

string

code

Machine-readable reason. Absent on a few legacy 400s.

string

key

additional properties

Example^generated

{
  "error": "example",
  "code": "example"
}

404

No such connector, or it is not visible to this session (NOT_FOUND); or the connection has no module of that name — only its modules, as its discovery read them, are asked of the CRM (MODULE_NOT_FOUND).

Media typeapplication/json

The error envelope every non-2xx answer uses.

object

error

required

Human-readable explanation.

string

code

Machine-readable reason. Absent on a few legacy 400s.

string

key

additional properties

Example^generated

{
  "error": "example",
  "code": "example"
}

422

Zoho rejected the request.

Media typeapplication/json

object

error

required

string

zoho

required

object

code

required

string | null

status

required

number | null

details

retryable

required

boolean

response

unanswered

required

True when Zoho gave no answer that says what was done — the connection dropped or timed out, Zoho failed on its side (a 5xx, or the same for the one record inside a 2xx), the answer was lost after its status or was not JSON, or Zoho said it made the record without saying which — so what was asked may have been done all the same: a create sent again after one may make a second record. A write that went unanswered stays counted, and its row may be written again for nothing. False when Zoho answered by declining (a 4xx, or a per-record refusal inside a 2xx), which made nothing.

boolean

Example^generated

{
  "error": "example",
  "zoho": {
    "code": "example",
    "status": 1,
    "details": "example",
    "retryable": true,
    "response": "example",
    "unanswered": true
  }
}

502

Zoho is rate-limiting (zoho.unanswered false: nothing was done), or did not answer — it could not be reached, failed on its side, or answered without saying what it did (zoho.unanswered true: what was asked may have been done). Or this API could not use the connection before anything was sent — a Zoho token that will not refresh (code: CONNECTION_UNAVAILABLE) — and says so on a write with written: false: nothing was written.

Media typeapplication/json

Any of:

object

object

error

required

string

zoho

required

object

code

required

string | null

status

required

number | null

details

retryable

required

boolean

response

unanswered

required

True when Zoho gave no answer that says what was done — the connection dropped or timed out, Zoho failed on its side (a 5xx, or the same for the one record inside a 2xx), the answer was lost after its status or was not JSON, or Zoho said it made the record without saying which — so what was asked may have been done all the same: a create sent again after one may make a second record. A write that went unanswered stays counted, and its row may be written again for nothing. False when Zoho answered by declining (a 4xx, or a per-record refusal inside a 2xx), which made nothing.

boolean

object

object

error

required

string

code

required

Why: CONNECTION_UNAVAILABLE when a Zoho token for the connection will not refresh.

string

written

On a write: refused before the record was sent to the CRM, so nothing was written and a retry makes no second record. Absent from a read.

boolean

key

additional properties

Example

{
  "written": false
}