Skip to main content
The Salesforce replica implements REST API v67.0 for six standard objects, a subset of SOQL and composite requests. Its key is salesforce.

Connect

Node
This is what ancha connect salesforce --lang ts prints. There is no OAuth or SOAP login: use the token as given.

Endpoints

All endpoints are partial. GET /services/data/ needs no token and reports version 67.0. Unsupported objects, fields and syntax return Salesforce’s error shape with an ancha: not implemented: message and x-ancha-gap: 1.

Objects

External_Id__c is a unique external ID on every object, usable in /sobjects/:type/External_Id__c/:value. Unknown fields are rejected. Relationships must point at existing records of the right object.

SOQL

  • One object, explicit fields, predicates joined with AND, one ORDER BY field, LIMIT and OFFSET.
  • Operators =, !=, <, <=, >, >=, IN, LIKE. String comparisons ignore case.
  • Pages hold 2,000 records by default; nextRecordsUrl reads the next page from a snapshot taken when the query ran.
  • Relationship queries, subqueries, aggregates, COUNT, GROUP BY, OR, NOT, date functions and FIELDS() are coverage gaps.
POST /composite runs 1 to 25 subrequests in order, with references such as @{created.id} and optional allOrNone rollback.

Starter data

The salesforce-starter dataset is the org Acme (00D000000000001AAA). The Helix account is hidden from queries, and direct reads and writes to it or its related records fail.

Checks

Salesforce has no state checks. Use trace checks:

Limits

  • Six objects; no Apex, triggers, workflows, lead conversion or assignment rules.
  • No SOAP, Bulk API, OAuth flows or full Describe metadata.
  • A simple per-account permission rule, not Salesforce’s sharing model.