How to Retrieve Salesforce Metadata Without the CLI

Retrieve Salesforce metadata - objects, fields, layouts, profiles - using the Metadata API, the CLI, or an in-browser viewer, and when each is worth the setup.

Updated 2026-09-09

Metadata answers the questions data cannot: which fields exist, how they are defined, what they are called in the API, and what depends on them.

There are three routes, and the fastest one depends on whether you need an artifact you can diff or an answer you need right now.

Option 1 - Salesforce CLI

Retrieve one object's metadata
sf project retrieve start --metadata CustomObject:Account --target-org my-org
  • sf project retrieve start pulls metadata into a local project you can diff and commit.
  • Best for deployments, code review, and anything that must move between orgs.
  • Requires an authenticated org and a local project - overkill for a single lookup.

Option 2 - the Metadata and Tooling APIs

The Tooling API answers field- and object-level questions directly, and it is queryable with SOQL-like syntax. This is the route to script when you want a report of every field on every object.

Tooling API: fields on an object
SELECT QualifiedApiName, DataType, Label
FROM EntityParticle
WHERE EntityDefinition.QualifiedApiName = 'Account'

Option 3 - read it in the browser

For the common case - what is this field's API name, type, and help text - TurboKit's metadata retriever shows field-level details inline on the record page, without a project, a CLI, or a second tab.

What to check metadata for

  • API names before writing SOQL or an integration mapping.
  • Field types and lengths before an import.
  • Dependencies before deleting a field - formulas, layouts, and validation rules that reference it.

Frequently asked questions

What is the difference between the Metadata API and the Tooling API?
The Metadata API deploys and retrieves configuration as files, and it is built for migrations. The Tooling API queries and modifies individual metadata records, which suits inspection and lightweight edits.
Do I need a developer setup to read metadata?
Not for reading. Setup and browser tools cover inspection. The CLI matters when you need version-controlled artifacts or a repeatable deployment.
Why does a field exist in the API but not in Setup search?
Setup search matches labels, and the API name can differ from the label entirely. Search by the label, and confirm the API name from the field definition.

More from the Admin How-To

Related reading