Rename, or unlist
const url = 'https://api.sloose.com/orgs/org_9f3c/connectors/cnn_9f2a';const options = { method: 'PATCH', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"label":"example","listed":true}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PATCH \ --url https://api.sloose.com/orgs/org_9f3c/connectors/cnn_9f2a \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "label": "example", "listed": true }'Renames a connection, or changes whether it is listed to verified users of the CRM. Administrators only. Nothing here touches the credential: Disconnect does that. There is no default to make: the work names its connection (design §14.8).
Session only: managing connections takes a person, never an org’s API token (D5); a token still lists and uses them.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The org id the session was issued for. A token for one org can never read another.
Example
org_9f3cThe org id the session was issued for. A token for one org can never read another.
The connector id, from the list.
Example
cnn_9f2aThe connector id, from the list.
Request Bodyrequired
Section titled “Request Bodyrequired”object
What the connection is called: “Production”, “Client A”, “Sandbox” — anything.
Whether a verified user of the CRM may be told this org holds it.
Examplegenerated
{ "label": "example", "listed": true}Responses
Section titled “Responses”The connection as it now stands.
object
object
Source | destination | both
What people call it — the CRM’s company name until an administrator renames it.
Whether a verified user of the CRM may be told this org holds it and ask it for access. An administrator turns it off for an org that would rather not be listed.
The system’s own id — the Zoho org id.
The Zoho data centre.
A person’s own connection (design §14.6): theirs alone, never an API token’s, managed by nobody else — and never named to the CRM’s users, whatever listed says.
Whether it holds a usable credential, so the server can read the system with nobody present.
Ok | revoked | error, from the credential’s last use.
Whether the grant covers the records themselves, which an import searches and writes. A connection made before connecting asked for them holds sign-in’s scopes alone: it is connected, can be read, and needs reconnecting before an import can run through it.
The modules whose field annotations a push from a configuration repository (POST /orgs/{org}/config/bundle, what sloose push sends) has written, each with when it last did; empty when none has. A push writes each of those modules’ annotations whole — and only those modules’ — so an alias added in the app on one of them is taken away by the next push that does not carry it, and one on any other module stays (a push still sets every module’s curation and excluded fields from its modules.json). Written with those annotations, never read from the audit.
object
The module’s CRM API name.
When a push last wrote its fields.
Whether the caller may change this connection’s field annotations, its aliases among them: true when the caller’s role, as this request settles it, is administrator. An API token acts at the lower of its own role and its creator’s (#239), and a read-only staff view writes nothing. False in the backoffice, which changes none.
Example
{ "connector": { "kind": "zoho_crm", "status": "active" }}The request — its body or its query — did not match the schema. issues carries the Zod issue list.
The error envelope every non-2xx answer uses.
object
Human-readable explanation.
Machine-readable reason. Absent on a few legacy 400s.
Examplegenerated
{ "error": "example", "code": "example"}No bearer, or one that is expired, revoked or no longer resolves to a member.
The error envelope every non-2xx answer uses.
object
Human-readable explanation.
Machine-readable reason. Absent on a few legacy 400s.
Examplegenerated
{ "error": "example", "code": "example"}The bearer’s role is too low, it was issued for a different org, or it is an API token (SESSION_REQUIRED).
The error envelope every non-2xx answer uses.
object
Human-readable explanation.
Machine-readable reason. Absent on a few legacy 400s.
Examplegenerated
{ "error": "example", "code": "example"}No such connector, or it is not visible to this session.
The error envelope every non-2xx answer uses.
object
Human-readable explanation.
Machine-readable reason. Absent on a few legacy 400s.
Examplegenerated
{ "error": "example", "code": "example"}